Skip to main content
Nintex Community Menu Bar
Solved

Development vs Production in 0365

  • Feb 9, 2018 8:11 PM UTC
  • 3 replies
  • 132 views
  • Translate All

Forum|alt.badge.img+5

So I developed a workflow and once it was what the customer wanted I made It a production workflow. And they are now using it. So what is best practices to make updates to that workflow without interrupting production?

 

Also when making changes to a workflow in production how do the workflows in progress react to it? Would they complete using the previous workflow?

Best answer by callum

Hi Joe,

Once a workflow instance starts, changes to the definition will not affect it, new instances will start using the latest published version.

Many users I've spoken with use this sort of approach:

  • Have a development/test & a production site
  • Often use scripts/migration tools/other tools to keep the lists/content types and other structure in sync from dev -> prod
  • Once a workflow change is tested, export from dev/test site and import into production, along with any structure changes.

Let me know if this helps

Callum

View original

3 replies

Forum|alt.badge.img+9
  • Nintex Employee
  • Answer
  • Feb 12, 2018 2:07 AM UTC

Hi Joe,

Once a workflow instance starts, changes to the definition will not affect it, new instances will start using the latest published version.

Many users I've spoken with use this sort of approach:

  • Have a development/test & a production site
  • Often use scripts/migration tools/other tools to keep the lists/content types and other structure in sync from dev -> prod
  • Once a workflow change is tested, export from dev/test site and import into production, along with any structure changes.

Let me know if this helps

Callum

Translate

Forum|alt.badge.img+5
  • Author
  • Feb 12, 2018 9:58 PM UTC

Yes that helps, thanks.

Translate

  • May 9, 2019 4:20 PM UTC

When publish a new workflow instance, will it affect old records with previous workflow version?

Translate