Selecting Supported Rule Hooks

Key Takeaways

  • Choose a supported rule type for the precise lifecycle phase and connector.

  • Cloud rules have restricted capabilities and a SailPoint review path for new rules.

  • Connector rules rely on supplied context and authorized managed connections.

  • Create Account field generation and adjustment of an assembled provisioning plan are separate hooks.

Last updated: November 2026

Name the phase and required result

A rule can implement logic beyond the available declarative operations, but it runs as a particular supported hook. Start with the phase: ingest data, link records, calculate a single value, adjust an assembled provisioning plan, or extend a supported connector operation. Each has its own permitted objects and intended side effects. The presence of a similarly named hook in a different SailPoint product does not establish its availability or behavior in Identity Security Cloud.

NeedSupported rule type to evaluateDocumented boundary
Derive a mapped identity value from supported contextIdentity AttributeReturns a value for an identity attribute and executes in the cloud
Resolve a complex account-to-identity linkCorrelationEvaluate after using declarative criteria where the data supports them
Compute which identity represents a managerManager CorrelationRelationship resolution distinct from storing a calculated text field
Generate a value needed for a new target accountAccount Profile Attribute GeneratorReturns the value for a configured provisioning policy field
Adjust supported details of an existing provisioning planBefore ProvisioningCloud hook mutates the plan and has no return output
Reuse supported rule logic inside a transformTransform ruleCloud type called through the documented rule transform
Adapt a response from a supported VA-based Web Services operationWeb Services After OperationOperates after the remote HTTP operation, with its supplied response and context
Run a script at a specified supported Active Directory account stepCorresponding connector before/after operation hookUses the documented IQService execution path for that specific action

Respect the runtime

SailPoint cloud rules execute in the shared cloud with a restricted context. Relevant rule types can read supported platform objects and helpers where the rule provides them. Code cannot use general context transactions, arbitrary external connections, or direct object persistence. Distinguish a direct call from a documented utility whose internal implementation may perform a supported check. For example, the rule utility describes a managed LDAP uniqueness check for an applicable field-generation case. Verify that the utility and its inputs are supported in the exact hook. Its existence does not permit opening an independent network connection.

Connector-executed rules in the documented VA path operate on what the connector passes. They cannot use that setting to query the SailPoint cloud data model. Some supported connector rules have an approved connection supplied by the runtime for work with the target, such as a JDBC aggregation rule operating on a result from a database query. Inspect the row and output contract for the connector. A hook for one Web Services integration cannot be assumed for a generic or differently implemented source. Check the specific connector's documentation and attach the rule for the intended operation as well as creating the rule object.

For a supported Web Services aggregation, use Before Operation if the target needs a computed request header. The hook has the current request endpoint and can return an updated endpoint. If the target returns account status codes that need normalization after parsing, use After Operation. It receives the processed account rows and can return revised rows under the data key. Test the outgoing header and returned status separately, preserving the account identifier that links the result to the correct record.

Work two provisioning requests

A new payroll account needs a site code derived from the identity and a field that is required on creation. Configure the field in Create Account and choose a supported transform or the appropriate field generator if code is warranted. Before Provisioning has a different role: it can adjust an already assembled plan within its supported scope before delivery to the connector, but SailPoint directs field creation to the provisioning policy. It cannot be substituted for the generator of a new field. A connector step that edits data after an HTTP response occurs at a later, target-specific boundary.

For a separate Active Directory case, the organization needs a specific supported script after account creation on its IQService path. Verify the connector family and exact after-create hook and the arguments supplied by IQService. Keep script concerns, the provisioning plan and the identity-side metadata distinct. Use test evidence to verify that the native operation and the hook both ran as intended.

SailPoint requires a review path for new cloud rules. Connector rules follow the supported rule APIs without the cloud review process. Either path still requires a validated, narrowly scoped sandbox test. See cloud rule types, connector rules, Before Provisioning, Web Services Before Operation, Web Services After Operation, and the rule utility.

Test Your Knowledge

An aggregation needs a supported custom algorithm to decide which identity should be attached to a source account. Simple declarative matches are insufficient. Which rule type fits this requirement?

A

Manager Correlation to choose an identity’s manager.

B

Correlation to associate the account with the selected identity.

C

Before Provisioning to change outgoing instructions.

D

Account Profile Attribute Generator to fill a create policy field.

Test Your Knowledge

A supported VA-based Web Services operation has already received a response, and the account rows need connector-specific normalization. Which rule fits that phase?

A

Identity Attribute, used as an identity profile mapping.

B

Before Provisioning, which runs in the cloud before a plan is sent.

C

Manager Correlation, to select a manager identity.

D

Web Services After Operation, with the supplied connector response context.

Sections you finish are checked off in the contents.