Project Status check for User Error

This Flow helps to prevent User error when Users are updating Project Status. Companies may not want their Users to be able to revert the Project Status from Completed back to Active or go from a Status of Canceled to Completed. This Flow allows Admins to restrict their Users from going from one specific Project Status or another. Note: You can isolate this restriction to specific User Profiles, or make specific Profiles exempt from the restriction. 

The completed Flow will look something like this:

The Start Node is anytime a Project is updated.

Next create a Decision node

Here you will set the Conditions using the Prior Value of the Triggering record and the current Status value the User is trying to Save. In the example Conditions below, we do not want Users to be able to change the Status from Completed or Canceled to a value of Installed. 

In the below example, we do not want Users going from a Status of Pending straight to a Status of Completed. 

Note: Here you could also set Condition Requirements that only specific Profile IDs (the Production Manager Profile and Admin Profile) could circumvent the restrictions set in the rest of the Conditions in the Decision node. 

The Decision node will look different for every customer who implements this Flow, but here is an example: 

On the Positive Outcome path, we will create a Custom Error node:

Type the message you want to appear on the screen when the record meets the Condition Requirements.