Skip to content
IT Canvass
Examples · Lesson

Examples hub

Quick answer

This module collects practical, adaptable examples, BeanShell rules, provisioning plan XML, workflow snippets and connector settings, so you can start from working code rather than a blank page. Each example is small, commented and tied to the concept it demonstrates.

Key takeaways

  • Working, commented examples to adapt
  • Covers rules, plans, workflows and connectors
  • Start from a sample, not a blank page
  • Each example links to its concept module
  • Keep adapted code in a rule library

The examples hub collects working, copy-ready code across every part of SailPoint you customise, rules, workflows, provisioning plans, connector configuration, REST calls, Java, XML and BeanShell, so you can learn by adapting real snippets rather than starting from a blank page.

What this module covers

Each example page shows genuine, commented code for one area, with the context it runs in and guidance on adapting it. Together they cover the practical customisation surface of IdentityIQ.

What you will find here

  • Rule examples, correlation, build-map, provisioning (BeanShell).
  • Workflow examples, approval steps, transitions, computed approvers.
  • Provisioning examples, building account and attribute requests.
  • Connector, REST, Java, XML and BeanShell examples.

How to use it

Start from the example closest to your need, understand what each line does, then adapt identifiers and logic to your environment. Always test customisations in a lower environment before production.

Common pitfalls

  • Copying without understanding the context a snippet needs.
  • Skipping null-safety when adapting rules.
  • Deploying examples 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.

Check your understanding

  1. The examples module is meant to be?

    • A. An identity attribute/value map. Correlation returns the attribute and value to match an identity.
    • B. Rule library. Rule libraries keep shared logic reusable.
    • C. Adapted to your environment. Examples are starting points to read and adapt, not paste blindly.
    Show answer

    C. Adapted to your environment. Examples are starting points to read and adapt, not paste blindly.

    Adapted to your environment. Examples are starting points to read and adapt, not paste blindly.

  2. Shared rule logic belongs in a?

    • A. Adapted to your environment. Examples are starting points to read and adapt, not paste blindly.
    • B. An identity attribute/value map. Correlation returns the attribute and value to match an identity.
    • C. Rule library. Rule libraries keep shared logic reusable.
    Show answer

    C. Rule library. Rule libraries keep shared logic reusable.

    Rule library. Rule libraries keep shared logic reusable.

  3. A correlation example returns?

    • A. Adapted to your environment. Examples are starting points to read and adapt, not paste blindly.
    • B. An identity attribute/value map. Correlation returns the attribute and value to match an identity.
    • C. Rule library. Rule libraries keep shared logic reusable.
    Show answer

    B. An identity attribute/value map. Correlation returns the attribute and value to match an identity.

    An identity attribute/value map. Correlation returns the attribute and value to match an identity.

Frequently asked questions

What does the term examples & code samples refer to in SailPoint?

The examples hub collects working, copy-ready code across every part of SailPoint you customise, rules, workflows, provisioning plans, connector configuration, REST calls, Java, XML and BeanShell, so you can learn by adapting real snippets rather than starting from a blank page.

What else is worth knowing about examples & code samples?

Together they cover the practical customisation surface of IdentityIQ.

What is the practical takeaway on examples & code samples?

Start from the example closest to your need, understand what each line does, then adapt identifiers and logic to your environment.

What tends to go wrong with examples & code samples?

Copying without understanding the context a snippet needs. Skipping null-safety when adapting rules. Deploying examples straight to production.
CallWhatsAppEnquire