Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Fix interference of Graph logic caused by Automation Steps

When you have logic in a PXGraph or PXGraphExtension written specifically to prevent Users from editing certain fields or pressing certain buttons in order to enforce a certain workflow, or prevent document progression based on specific rules, Automation Steps configured for that screen supersede all BLC logic and allow Users with no knowledge of the workflow to enable/disable buttons and fields thus allowing them to do things they were not meant to do.


Case #082149 was opened, and we were told to just throw Exceptions during processes if such a button were prematurely enabled and pressed. This greatly disrupts workflow, as the most common response to such an Exception is "Why was the button enabled in the first place?" and we've run into many people who have pressed these buttons just because they were enabled, even when they knew they should not press them. 

  • Angel Sanchez
  • Dec 17 2018
  • Attach files