How to set up a new workflow

Hey ​@Adcirruserp 

From what you're describing, this sounds consistent with how Acumatica handles workflow changes across multiple customization projects. When two projects modify the workflow for the same screen, Acumatica applies the changes from the project with the highest level rather than merging them, which would explain why you're seeing different actions depending on the publishing levels.

If you want to maintain the customizations separately, the recommended approach is to use the Workflow API to extend the existing workflow. Otherwise, the workflow changes would need to be consolidated into a single customization project.

Since eBiz is a third-party customization, I'd lean toward exploring the Workflow API approach first so you can keep your changes separate from the vendor's package. I'd just verify how eBiz implements its workflow before proceeding, since that could affect how your extension needs to be structured.

Here's the Acumatica documentation: Workflow Creation: General Information.

Hope this helps!

Ebiz is frustrating because they should not be adding workflow actions. We complained to them in the past about this.

What we do is we add the workflow actions into THEIR package, but this requires you to add the actions every Ebiz update. Certainly not ideal, but it tends only be a 10-15 minute chore every 6 months or year.

Unfortunately, you can’t have two packages updating workflow on the same screen.

I’ll specify that they should be using code to add workflow actions.

A little birdy told me Acumatica is going to stop putting up with ISVs adding workflow actions via the GUI editor.

I still see the issue in 2026 R1 for Ebiz. Not sure about R2. Maybe by 2027 Ebiz will do it.

​@Adcirruserp Please add the workflow in the ebiz customization and publish it as a workaround. we cannot use same screen workflows in customization projects