Examples · LessonBy Neelima, SailPoint Architect · Published · IdentityIQ 8.4 · all levels
XML examples
Example IdentityIQ object XML for import/export.
Quick answer
These XML examples show how IdentityIQ objects (roles, applications, rules) look when exported, for editing and version control.
Key takeaways
- Object XML structure
- Editing exported XML
- Importing changes
- Keep XML in source control
IdentityIQ objects serialise to XML, which is how you export, version-control and deploy configuration. These examples show what common objects look like as XML.
A role (Bundle)
<Bundle name="Branch Teller" type="business">
<Description>Baseline access for a branch teller</Description>
<RequiredRoles>
<Reference class="Bundle" name="Teller-AD-Access"/>
</RequiredRoles>
</Bundle>A correlation rule
<Rule name="Correlate by EmployeeId" type="Correlation">
<Source>return "employeeId==" + account.getAttribute("employeeId");</Source>
</Rule>Guidance
- Keep exported XML in source control as the deployable source of truth.
- Understand references before editing; they link objects.
- Import into a lower environment first and verify.
Common pitfalls
- Breaking object references by careless editing.
- Editing generated IDs that must stay consistent.
- Deploying XML straight to production.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
What do XML examples show?
Frequently asked questions
What does the term XML examples refer to in SailPoint?
IdentityIQ objects serialise to XML, which is how you export, version-control and deploy configuration. These examples show what common objects look like as XML.
What else is worth knowing about XML examples?
Keep exported XML in source control as the deployable source of truth. Import into a lower environment first and verify.
What tends to go wrong with XML examples?
Breaking object references by careless editing. Editing generated IDs that must stay consistent. Deploying XML straight to production.
Want this with a live instructor and a lab tenant?