Reference · LessonBy Neelima, SailPoint Architect · Published · IdentityIQ 8.4 · all levels
XML object reference
How SailPoint IdentityIQ objects are represented in XML, and how to export, edit and import them safely.
Quick answer
How SailPoint IdentityIQ objects are represented in XML, and how to export, edit and import them safely.
Key takeaways
- All objects serialise to XML
- Export/import via debug pages or iiq console
- XML editing is powerful but unforgiving; back up
- Commit XML to Git for review and rollback
Everything is XML
IdentityIQ objects serialise to XML. Rules, workflows, applications and roles can all be exported, versioned, edited and re-imported as XML.
Export and import
Use the debug pages or the iiq console to export objects, and import to bring them into another environment or restore a version.
Editing XML
Direct XML editing gives full control for things the UI cannot express, but is unforgiving: validate structure and keep a backup.
Source control
Committing object XML to Git is what makes configuration reviewable, diffable and reversible across the lifecycle.
Practice challenge
+0 XPStreak ×0
Question 1 of 1
What makes IdentityIQ configuration reviewable and reversible?
Frequently asked questions
What does the term XML Object Reference refer to in SailPoint?
IdentityIQ objects serialise to XML. Rules, workflows, applications and roles can all be exported, versioned, edited and re-imported as XML.
What else is worth knowing about XML Object Reference?
Use the debug pages or the iiq console to export objects, and import to bring them into another environment or restore a version.
What is the practical takeaway on XML Object Reference?
Direct XML editing gives full control for things the UI cannot express, but is unforgiving: validate structure and keep a backup.
Want this with a live instructor and a lab tenant?