Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
Examples · Lesson

XML examples

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.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. What do XML examples show?

    • A. How IdentityIQ objects look when exported for editing and version control.
    • B. To version and repeatably deploy configuration.
    • C. The Bundle object.
    Show answer

    A. How IdentityIQ objects look when exported for editing and version control.

    How IdentityIQ objects look when exported for editing and version control.

  2. What object backs a Role in XML?

    • A. To version and repeatably deploy configuration.
    • B. The Bundle object.
    • C. How IdentityIQ objects look when exported for editing and version control.
    Show answer

    B. The Bundle object.

    The Bundle object.

  3. Why keep XML in source control?

    • A. The Bundle object.
    • B. How IdentityIQ objects look when exported for editing and version control.
    • C. To version and repeatably deploy configuration.
    Show answer

    C. To version and repeatably deploy configuration.

    To version and repeatably deploy configuration.

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.
CallWhatsAppEnquire