cancel
Showing results for 
Search instead for 
Did you mean: 
cespedesrl
Nintex Newbie

Implementing Business Processes: 1 control process vs. many separated proceses?

I have a question regarding the development of a business workflow in two different ways: one "orchestration" process vs. a "coreography" of many processes. (I am using BPM figures between quotes for ilustrative purposes only).

Taking in consideration the following paths for Development & Design:


•Create multiple (n) Nintex Workflows and create a chain of calls to workflows ("coreography" of separated, simple workflow units)
•Create one (big) Nintex Workflow (controller, complex workflow)

Which one is the recommended way to do workflows in Nintex, taking in consideration best practices in design and performance?

Reply
1 Reply
Not applicable

Re: Implementing Business Processes: 1 control process vs. many separated proceses?

Luis,

For complex workflows, making use of the 'Start Workflow' action to call on individual child workflows is the favored method.

Farm performance may vary, but we typically begin to see performance degradation in workflows exceeding 500 KB or containing more than 100 workflow actions.

Please refer to the following posts for more information:

Defensive Workflow Design Part 3 - Separation of Concerns

Start a Workflow using a Web Service

Regards,

Justin Tung

Reply