Calling Sequence for the Participant Resolver API
When the workflow engine needs to find an activity’s participants, it passes the property information defined within the workflow engine’s user interface to idmgr. This information includes the type of participant resolver to use (as follows, by order of precedence), the name of the participant resolver (with custom types), and optional user-defined data.idmgr then does the following:
cim1265
When the workflow engine needs to find an activity’s participants, it passes the property information defined within the workflow engine’s user interface to
CA Identity Manager
. This information includes the type of participant resolver to use (as follows, by order of precedence), the name of the participant resolver (with custom types), and optional user-defined data.CA Identity Manager
then does the following:- Calls the appropriate participant resolver, based on the specified participant type.
- Retrieves the participant list and passes it back to the workflow engine.
If multiple participant resolver types have been specified,
CA Identity Manager
selects one based on the following order of precedence:- Custom type
- Role type
- Filter type
- Group type
CA Identity Manager
uses the first participant resolver it finds and ignores the rest.The workflow engine interacts with the Participant Resolver API indirectly, through a
CA Identity Manager
-supplied script named IM Approvers. This script passes CA Identity Manager
all the relevant property information defined within the workflow engine’s user interface, and CA Identity Manager
passes the information to the Participant Resolver API. This script name must be included in the Resources properties of any workflow activity that requires an approval of a CA Identity Manager
task. For more information, see the
Administration Guide
.