17.3 Viewing the Approval Status of a Workflow Process

The Approval Status column reflects the current approval status of a workflow process. At any given time, a workflow process will display one of the following statuses:

Processing

Indicates that one or more activities in the workflow process is waiting for an action from the approver. For example, if a workflow process has two approval activities defined, one is already approved, and the other is still waiting for approval. Technically, the workflow process is still running, so the workflow process displays the approval status as Processing.

Approved

Indicates that all approval activities in the workflow process have been completed.

Denied

Indicates that one or more approval activities in the workflow process was rejected by the approver.

Retracted

Indicates that the request for permission access was retracted by the requester. In this case, the workflow process is terminated before completion. Occasionally, when a user retracts a request with a pending workflow approval task, the approval task might continue to display on the application used to request access, such as Identity Governance, even though the status of the workflow changes to Terminated on the Workflow Administration Console. The delay occurs because the scheduler responsible for deleting the data runs as per the interval specified in the Pending Process Interval field on the Engine and Cluster configuration page. The default interval is 30 seconds for optimal performance. Optionally, reset the value to less than 30 seconds by accessing Configuration > Engine and Cluster. For more information, see Configuring Workflow Engine and Cluster settings. In SaaS environments, contact your SaaS Operations Administrator to reset the value.

Error

Indicates that one or more approval activities in the workflow process is faulty. In this case, the entire workflow process is terminated before completion. The errors can occur due to many reasons, some of them are listed below:

  • Error in calling the token end point.

  • Error while initializing the scripting engine or scripting context.

  • While forwarding a task, the Activity ID or Addressee details are missing or empty.