Home Blog Tips & Tricks Using Acumatica’s Low-Code/No-Code

Tips & Tricks Using Acumatica’s Low-Code/No-Code

In this post, Naveen Boga compares our Low-code functionality, and how Acumatica has numerous ways to achieve the same results without the need for custom code. He compiles a number of tips to give you an idea of how to create and edit Acumatica fields within the GUI instead of having to write code.
Naveen Boga | August 23, 2022



As part of the Low code/No code concept, Acumatica ERP has introduced Workflow Engine in the 20 R2 version. Previously we used the Automation steps, which is tough to manage a transfer from one instance to another. The new Workflow Engine is maintained within a customization project and transfers easily between two instances.

We can define that a workflow does not require coding. To create/extend the workflow, we can use the editors in the Screens section of the Customization Project Editor.

In most cases, by using the default settings, writing code is not necessary. In addition, the settings can be configured in the Screen section

In this article, I would like to describe a few features where it’s not necessary to use code. These features are:

  • Enable/Disable a field
  • Make a field mandatory
  • Make a field Visible/Invisible
  • Change the Display Name of the field
  • Add Conditions
  • Enable fields when the document is Completed/Closed
  • Auto-Run Actions
  • Enable/Disable a field

Previously, to enable/disable the field, code was written in RowSelected event or using the PXUIEnabled attribute. However, by using the Screen Configuration setting we can enable/disable the field in the Screens section of the Customization Project Editor.

Enable or Disable a Field

To Enable/Disable a field:

  1. Navigate to the Customization Projects
  2. Open the Customization
  3. Click on the screen in the menu on the left-hand side.
  4. Use the Customize Existing Screen to create and add the Sales Orders
  5. Expand the SO301000 and click Fields.
  6. Select the field to Enable/Disable (For example, Customer Order Number)
  7. Add the value for the Enabled/Disabled column in the respective field.
  8. Publish the Customization Package to save the changes.

Make A Field Mandatory

Previously, we used the PXDefault attribute to make a field mandatory. But in the Customization Project Editor, we can use the settings to make the field mandatory.

  1. From the Customization Project Editor, select Fields in the left-hand menu.
  2. Set the Required section to True.
  3. Publish the Customization Package to save the change.

Make a Field Visible or Invisible

Using the same steps to Enable or Disable a field, we can make a field Visible or Invisible. This skips the need to write code in the RowSelected event at the graph and the PXUIVisible attribute at DAC level.

Change Display Name

In older versions, to change the Display Name we were writing the Cache_Attached event but using these settings we can easily modify/change the Display Name for the field.

Add Conditions

Adding Conditions is useful when performing Enable/Disable, Visible/Invisible, and Mandatory fields. In the Customization Project Editor, we can add new conditions or append conditions to the default Acumatica-provided conditions.

To add conditions:

  1. Select Conditions from the menu on the left-hand side.
  2. The Condition Properties screen displays.
  3. Enter a Condition Name and complete the required fields. In this example, we are adding a condition to Order Type that Equals a specific value.
  4. Publish the Customization Package to save the changes.

Enable the fields when the Document is Completed or Closed

The native Acumatica process will not allow you to edit or modify when a document is closed or completed. However, using the Workflow Mechanism a user can edit and save information even after the document is completed or closed.

To achieve this, we need to do changes at two levels.

  • Code Level changes are required.
  • Add steps in the workflow

I have written an article on this with a detailed explanation and here is the link for reference: https://asiablog.acumatica.com/2021/10/enable-customization-fields-when-document-is-completed.html

Auto-Run Actions

The Auto-Run Action feature allows us to automatically invoke another action when a condition is completed.

For example, you want to put the Order On-Hold when the Sales Order Total is less than $100.00. In this scenario, we can use the Auto-Run action feature that it will check the Order Total based on the condition and create the Put On-Hold button automatically. Please find the steps below.

To use Auto-Run to create the Put On-Hold button:

  1. Add a new condition to the Conditions
  2. Open the Extended Workflow and select the Open status workflow
  3. Next, go to the Actions
  4. Select the condition in the Auto-Run action
  5. Publish the package to save your changes.


When comparing low code functionality, Acumatica has numerous ways to achieve the same results without the need for custom code. These tips have been compiled to give you an idea of how to create and edit Acumatica fields within the GUI instead of having to write code.

Hopefully, after reading this article, you’ll be able to manage Acumatica a bit better and explore other areas of low code to save yourself a lot of time.

Happy Coding!

Blog Author

Naveen started his programming career with .NET technology and since 2016 has been solely focused on Acumatica ERP development. He is passionate about his career in technology and is continually learning and growing his skill set. However, Naveen believes in the adage “work smarter, not harder.” Currently, he creates custom solutions for Acumatica customers and primarily creates and maintains the shipping solutions products. A two-time Acumatica MVP and now Developer MVP, he is a frequent contributor to the Acumatica Community, providing useful insight and problem-solving to Acumatica users.

Receive blog updates in your Inbox.