Saviynt SCIP SAVIGA-C01 Question # 18 Topic 2 Discussion

The correct sequence of workflow events for an application where the Manager's approval should be followed by the Application Owner's approval is D. Start > Manager's Approval > Resource Owner's Approval > Approve/Reject > End. Here's a breakdown:

Saviynt's Workflow Structure: Saviynt workflows follow a sequential structure, starting with a "Start" event and ending with an "End" event.

Workflow Activities: Each step in the workflow is represented by an activity, such as an approval task.

Manager's Approval: In this scenario, the first required approval is from the Manager. This would be represented by a "TASK Access Approve" activity (or similar, depending on the specific configuration) assigned to the user's manager.

Application Owner's Approval: After the Manager's approval, the workflow needs to proceed to the Application Owner for their approval. This would be another "TASK Access Approve" activity assigned to the Application Owner. In Saviynt terms, Application Owner is a type of Resource Owner.

Approve/Reject: This activity represents the decision point where the final approver (in this case, the Application Owner) either approves or rejects the request.

End: The workflow concludes with the "End" event, signifying the completion of the process.

Other Options:

A. Start > Resource Owner's Approval > Manager's Approval > Approve/Reject > End: Incorrect order; the manager's approval should come before the application owner's.

B. Start > Manager's Approval > Custom Assignment > Approve/Reject > End: "Custom Assignment" is not the most appropriate activity for a standard approval step. "TASK Access Approve" would be more suitable.

C. Start > Manager's Approval > Access Approval > Approve/Reject > End: "Access Approval" is a bit redundant; "TASK Access Approve" assigned to the appropriate role is clearer.

In essence: The correct workflow sequence accurately reflects the required approval hierarchy: first the Manager, then the Application Owner, followed by the final decision (Approve/Reject) and the end of the workflow.