No. The key technical problem is the term Create Rule . IdentityIQ does not use an application “Create Rule” as the standard mechanism for defining how new target-system accounts are provisioned. New-account provisioning is principally defined through an application ' s Create Account Provisioning Policy . That policy identifies the fields required for account creation and determines how their values are obtained. Field values can themselves come from literals, scripts, rules, dependencies, or requester-entered information.
IdentityIQ does have a Creation Rule , but that is an aggregation rule with a different purpose. SailPoint documents the Creation Rule as executing when a new Identity is created during aggregation, commonly from an authoritative application. It can manipulate the identity being created—for example, its name or attributes—but it is not the mechanism that specifies how a new account is provisioned to a target application.
Provisioning rules such as BeforeProvisioning and AfterProvisioning can customize a ProvisioningPlan around connector execution, but that still does not make “Create Rule” the account-creation definition. Therefore, as worded, the proposed solution is false.
References/topics: IdentityIQ Engineer — Application Provisioning Policies, Create Account policy, Creation Rule, BeforeProvisioning Rule, Application Definition.
=======
