Application Dependencies

Your business may have dependency requirements, where a user's access to one application is dependent on access to another application. For direct-connection applications, you can define Application Dependencies on the Provisioning tab, to specify that a user must have an account on one system before they can have an account on another system. When an Application Dependency has been defined, IdentityIQ's provisioning process will check to see if there is an account on the application(s) listed. If not, when IdentityIQ processes a provisioning request for a new account, a request for the an account on specified system(s) is added.

When Application Dependencies have been defined, you can use values from these applications as part of your Provisioning plans. When you select Value Settings in the provisioning form, you will see dependent as an option. You can choose the application and the attribute to retrieve from it in your form.

Using Rules in Applications

Rules in applications allow the addition of custom business logic to extend the functionality of IdentityIQ in aggregating from or provisioning to the application.

Some rules are applicable to and can be used in all applications. Other connector types support rules that are specific to the connector type. For more information on connector-specific rules, see Rules Tab(LINK IN DOC).

When implementing rules for applications, be aware of potential performance impacts. Complex rules that act on every record being processed by IdentityIQ can have a significant performance impact.

For general information about implementing rules, see Rules and Scripts in IdentityIQ(LINK IN DOC).