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

How developer share tasks in a single Workflow Project

Jump to solution

Hi, Experts!

 

How can my team members managed to work collaboratively on one single Workflow Project? We using Nintex for a while now and seems it cannot be shared within team members not like doing a custom .NET application.

 

We need your help and advise as we need to strategize and speed up our development process.

 

Thanks,

Ryan

 

Labels: (1)
0 Kudos
Reply
2 Replies
jackgelo
Automation Master
Automation Master

Re: How developer share tasks in a single Workflow Project

Jump to solution

Hi,

unfortunately there is no co-authoring while building a workflow/form with Nintex, so you should organize externally in order to have only one people active in modifying the workflow and then saving it in order to have someone else pick where he has left..

 

Giacomo

Reply
graham
Nintex Newbie

Re: How developer share tasks in a single Workflow Project

Jump to solution

Well, as stated above, there is no way of collaboratively working on a single workflow

But - you can break it into multiple workflows on which you can work separately.

If you want the final product that consists of a single workflow, if each of the workflows are contained in an Action Set, you (the chief developer) can save each of these action sets as snippets and then import them into your master workflow.

You will of course need to be very careful with variable naming to ensure that any global veriables used across the workflows have the same names and types. You can ensure this by creating an action set in your master (it doesnt need to hold anything) and saving it as a snippet - then create a dummy workflow containing just the action set - this will hold just the variables you created.

The other devs can open the workflow and save the action set as a snippet and import them into their workflows.

However - if you need that many devs working on it - you may face one of the limits of Nintex (size of workflow or number of task steps) and keeping it as multiple workflows might be the answer.

Saving repeated processing as UDAs might avoid some of these limits and allow other devs to provide useful work.

View solution in original post

Reply