ServiceNow Workflow Basics: Two Common Mistakes Why Creating an Approval Workflow Does Not Work

[BillMartin]

I want to help you not to fall and get stuck in these two common mistakes why the approval workflow is not behaving as expected.

You may have already established a good workflow that meets your business requirement and now you would like to put it into action using the different platform features of ServiceNow like the employee center, service operations workspace, and flow designer.

However, you are still failing to proceed. Here is why: the two common mistakes that you have not considered.

1. The Defined Table Declared From The Trigger Does Not Extended From The Task Table.

The out of the box tables of ServiceNow commonly extends from the task table. A good example is the ITSM module. Incident, Problem and Change all extends from the task table. It enables these modules to have the ability to trigger an approval at any stage of the business process.

2. The Role of the Approver Does Not Inherit From The Out of The Box ServiceNow Approver Roles.

ServiceNow Widgets that are readily available for approval task and notification should inherit from the correct roles. The approvers extends all througout modules of ServiceNow, so inheriting from the approvers role is a prerequisite that cannot be ignored.

I have demonstrated for better visibility.

Here is How: ServiceNow Approval Workflow: How to Create an Approval Workflow Using Flow Designer