Previous Topic: Parent and Child Processes in a WorkflowNext Topic: Parent Processes for Aggregated Tasks


Waiting for Child Processes

CA Identity Governance coordinates the execution of parent and child processes. For example, most certifications have distinct certification and change approval phases. CA Identity Governance pauses the high-level certification process until the child processes for certification actions complete. Then it advances the high-level certification process to the change approvals phase.

Parent and child processes pass a message flag between them through CA Identity Governance. However, CA Identity Governance monitors which jobs respond, and implements the logic that starts and stops parent and child jobs.

Process nodes that handle parent-child interaction use the following parameters:

waitKey

Causes CA Identity Governance to suspend a process at the current node. Any not null waitKey value causes CA Identity Governance to suspend the process.

This parameter value is passed to the workflow context in CA Identity Governancewhen the node runs the rcmInvoke agent script.

Note: This field can only be used in building blocks that pass the waitKey value to the CA Identity Governance workflow context.

In standard CA Identity Governance processes, the following values are used:

WAIT_PARENT

Causes CA Identity Governance to suspend a child process at the current node until the parent process sends the WAIT_PARENT string.

WAIT_CHILD

Causes CA Identity Governance to suspend a parent process at the current node until all child processes send the WAIT_CHILD string.

signalKey

Causes CA Identity Governance to resume a parent or child process. CA Identity Governance resumes a parent process only after all of its children return the correct signalKey value.

This parameter value is passed to the workflow context in CA Identity Governancewhen the node runs the rcmInvoke agent script.

Note: This field can only be used in building blocks that pass the signalKey value to the CA Identity Governance workflow context.

In standard CA Identity Governance processes, the following values are used:

WAIT_PARENT

Causes CA Identity Governance to resume child processes that were suspended with the waitKey value WAIT_PARENT.

WAIT_CHILD

Causes CA Identity Governance to resume a parent process that was suspended with the waitKey value WAIT_CHILD.

The waitKey and signalKey parameters are used together. The waitKey field defines the value of the signalKey field that causes CA Identity Governance to resume the suspended process. The two fields must specify the same text string.

More information:

Processes for Flow Control and Aggregation

Building Blocks for Parent-Child Process Handling