In part 1 of this series on conditional statements, I demonstrated the use of IF-THEN logic for filtering records. In this blogpost, I will discuss using conditional statements in Approval Map.
The basic premise for approval map is if specific conditions on a document (or entity type) are satisfied, then Acumatica will route it to a user or workgroup for approval. Approval maps may include steps, from a simple one-step approval (e.g. when an expense claim is submitted, route it to the supervisor for approval) to multi-step approvals that may be executed in a sequential, parallel, or sequential-parallel fashion.
There are typically 3 parts in an approval map:
1. The step in the approval process
2. The conditions for the step
3. The action for the step if all conditions are met
Let’s examine a sample AP Bill approval map and its settings.
In the Steps panel, we see 3 steps in this approval map. The first step is ‘Line Approvals by Department’, which consists of 5 scenarios. Each scenario has a set of conditions and actions.
Consider that each line on an AP bill is an expense by a department, the 5 scenarios are mutually exclusive and can be read like this:
IF the expense is for Consulting, THEN route the AP bill to Martin Bernia from the Consulting department for approval
IF the expense is for Finance, THEN…
IF the expense is for Warehouse, THEN…
IF the expense is for Operations, THEN…
IF the expense is for Sales/Marketing, THEN…
Once we break down the list, we see the familiar conditional statements. For good measure, the screenshots below illustrate that the third step ‘Large Bill Approval’ uses the same concept.
I hope this helps to clarify how you can create an If…Then… scenario when setting up your approval maps. If you have any questions or need any help get in touch with us here at Central Nervous Systems.
Eric.