Which rules need to be followed when adding activities to a workflow? (Choose 3.)

When constructing a workflow within Micro Focus Identity Manager, several structural rules must be followed for the workflow to be valid. Firstly, any parallel processing paths initiated by a Branch activity must be synchronized and brought back into a single path using a corresponding Merge activity. Secondly, a provisioning workflow's purpose is to perform an action; therefore, it must contain at least one core provisioning activity, such as an Entitlement or Entity activity, to modify identity data or grant access. Lastly, every workflow must have a single, well-defined entry point (Start activity) and a single, well-defined exit point (Finish activity) to ensure predictable and manageable process flow.

A. A workflow cannot contain a condition activity.

This is incorrect. Condition activities are fundamental components used for creating logical branches (e.g., if/then/else) based on data or previous activity outcomes, such as an approval status.

B. Each Approval activity must have a Condition activity.

This is not a strict rule. While it is common to use a Condition activity to check the result of an Approval, the flow can be routed directly from the Approval's outcomes (e.g., 'approved' or 'denied' data flows) without an intermediate Condition activity.

1. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.2, "Building a Provisioning Request Definition."

This section explicitly states: "All workflows must have one Start activity and one Finish activity." This supports answer E.

It also states: "A workflow must contain at least one provisioning activity (Entitlement Grant, Entitlement Revoke, or Entity) to be a valid workflow." This supports answer D.

2. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.6.1, "Workflow Activity Reference," subsection on "Branch Activity."

The documentation for the Branch activity states: "The Branch activity allows you to create multiple parallel paths in a workflow... You must add a corresponding Merge activity to bring the paths back together." This supports answer C.

3. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.6.1, "Workflow Activity Reference," subsection on "Condition Activity."

This section describes the purpose and usage of the Condition activity for creating conditional paths, demonstrating that it is a valid and essential component, which invalidates option A. The examples show its use after an Approval activity but do not mandate it, which invalidates option B.