<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Digital processes that can think

Posted by FlowWright on Oct 18, 2019 7:56:00 AM

There are many ways to make digital processes make decisions.  Rules are used in almost any workflow process today to determine what path of steps and decisions within a process should be followed. 

The screenshot below is an example of a very basic invoice process workflow where a decision is made based on the size of the purchase order:

FlowWright purchase order workflow

Here is another example: a Change Notice process .  Here, a company has  32 types of Change Notices and the workflow uses rules to figure out who to route Change Notices to.  Even though the workflow design looks large, the concepts used to automate this process are intuitive and easily automated using FlowWright:

Change notice workflow

FlowWright provides multiple types of decision making options that are graphically represented to make design and execution and review intuitive for users.  Some of the decision workflow steps available to choose from are:

  • decision step
  • evaluate decisions
  • evaluate expression
  • decision table

Graphical decisions are rendered to show clearly what path a workflow followed based on decisions made during run-time.  But sometimes the complexity of decision-making,  especially when there are many rules involved, requires more power.  For this use case, FlowWright provides Decision Tables. Decision Tables are a powerful tool used to maintain a many rules that may involve a very large number of inputs and outputs.  Decision Tables can be used at run time to evaluate inputs and to determine outputs and outcomes.

Some processes make API calls or REST web-service calls to other systems to get data, and the data that is returned is then  evaluated to make decisions.  For example, a workflow process might call a business object to determine a patient's age, and then if the age is greater than 18, the process might go down one path, and if the patient is less than 18, it will go down another path.

Workflow processes can be smart, nimble, and include sophisticated decision-making that make the design appear to do the "thinking" for you!

Have questions about how to implement digital workflow processes that can think? Let's Talk! 

Make the workflow process think

Topics: Workflow Process Mapping, workflow processes