Is there a maximum number of conditions used on a rule in an approval map? Can you use just one subaccount segment for the approval condition?

Question

I am running into a scenario where I could really use the ability to segment approvals by a particular subaccount segment. 6 years ago Acumatica marked this idea as ‘unlikely’ to implement’. (see: “Approval maps: when subaccount is used as a condition, allow user to specify a segment value, not just the whole subaccount.”)

I tried masking the segments with question marks and blanks, but the bill wouldn’t read either one. ‘???-???-100’ and ‘ - -100’

To accomplish what I need to do, I would have to hardcode almost 75 different subaccounts into the conditions. (will import, but still - not very nice for long term maintenance).

Is there a limit to the number of conditions in a particular rule of an approval map?

Heather Jones · Answer

I think I have managed to achieve this for approval routing depending on Segment2 of the subaccount.

Where a segment2 value was ‘Quality’ for example try:

Field name: Subaccount

Condition: Contains

Value: %%%-Quality

Just watch if you have any other segments with part of the word, ie ‘IT’ for example as the rule that is the higher in the list will be used. I needed to hardcode IT to get round that, but for the most part this seems to work across all other values in our segment2 list. The %%% is the wildcard.

You also need to watch how you enter it, if you tab off to quickly/blink twice or lose concentration, you can select one of the existing subaccounts in the dropdown list that is being prompted, rather than taking the wildcard that you have keyed in.

In terms of number, i have around 35 defined rules in a level 1 step then a handful in L2 and L3 steps, and a catchall step.

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded