Hello,
Not entirely sure why Acumatica did this, but I was curious about whether or not the identifier field for states could be expanded to two characters. 1 character gives you 26 alpha (less pre-defined) and then 10 int. I know you can use symbols as well but these don’t work well with API/middleware. Just wanted to gauge if this would be feasible or if anyone has done it in the past.
Best answer by Leonardo Justiniano
Hi
If a workflow has more than 36 different states, I can’t imagine the complexity of all possible combinations of conditions to transition from one to another. Having said that, I do no think there is a limitation into the state engine as the state field can be defined bigger in the source DAC and set in the workflow:
and then
CMMSWorkOrder.Status can be defined longer than 1 character.
There is an excellent guide (5 parts) for workflows written by Brian Stevens which explain the insights of Acumatica workflows: [Workflows Via Code]
+4Hi
If a workflow has more than 36 different states, I can’t imagine the complexity of all possible combinations of conditions to transition from one to another. Having said that, I do no think there is a limitation into the state engine as the state field can be defined bigger in the source DAC and set in the workflow:
and then
CMMSWorkOrder.Status can be defined longer than 1 character.
There is an excellent guide (5 parts) for workflows written by Brian Stevens which explain the insights of Acumatica workflows: [Workflows Via Code]
Thanks, Leonardo-
Yeah.. you are telling me about the complexity of the workflows. 21 workflows.. each having niche states. This is great information, I’ll dig into it.
+4Awesome!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
