Examples · LessonReviewed by Imran Q, SailPoint Trainer, 7 yrs · Updated · Published · IdentityIQ 8.4 · all levels
SailPoint BeanShell examples
Standalone BeanShell snippets used across IdentityIQ.
Quick answer
These BeanShell examples show common scripting patterns, logging, attribute access and helper calls, used inside rules and workflows.
Key takeaways
- Logging and debugging
- Attribute access
- Calling helper methods
- Keep snippets side-effect-light
BeanShell is the scripting language used throughout IdentityIQ rules and workflows. These snippets show everyday patterns that keep custom logic debuggable and robust.
Logging for debugging
import org.apache.log4j.Logger;
Logger log = Logger.getLogger("custom.myrule");
log.debug("Processing: " + (identity != null ? identity.getName() : "null"));Safe attribute access
String dept = identity != null ? identity.getStringAttribute("department") : null;
if (dept == null) { dept = "UNKNOWN"; }Guidance
- Log at debug with a named logger to trace values without production noise.
- Guard every dereference, BeanShell throws at runtime otherwise.
- Keep snippets side-effect-light, they often run per identity.
Common pitfalls
- No logging, leaving failures opaque.
- Null-pointer errors from unguarded access.
- Expensive work in per-identity snippets.
Want this with a live instructor and a lab tenant?