Reverse deployment (from production to development)

  • 26 November 2019
  • 1 reply
  • 7 views
H

Hi,

 

Due to the misconception during initial use of K2 designer, our Production and Development is different being the production having the latest and workable version. Only different on the designer part, the workflow are the same. 

 

Currently the intention is to made changes to the existing workflow. Minor changes, add a smart object event in 1 of the activities. Because the Prod & Dev are different, I couldn't do this. If I do packaging from Dev(working on workflow  K2 studio) and deploying it to Prod will revert the current working version to old version.

 

I'm considering to package everything from the Prod and deploy it to Dev. But I'm not certain of what to expect during and after the process, maybe you can give us a heads up.

 

Also, would it be an issue if I update the Prod workflow directly without going through packaging and deployment? Is it possible/safe to do so? 

 

Thanks

1 reply

Albarghouthy
Userlevel 5
Badge +16

Hi  @helmi 


 


Best practice is to align the environment, so I would recommend packaging your solution from Prod and deploy it to Dev.


If the change on the workflow side, yes you can make the changes to the workflow directly in production because it is easy to revert back workflow versions from the workspace/management, however this is not best practice.


 


Workspace


https://help.k2.com/onlinehelp/k2blackpearl/userguide/4.7/default.htm#6.Administer/Workspace_Legacy/Management_Console/Process-Versions.htm


Management


https://help.k2.com/onlinehelp/k2blackpearl/userguide/4.7/default.htm#K2_Management_Site/Workflow_Server/Versions.htm%3FTocPath%3DAdminister%7CK2%2520Management%2520Site%7CWorkflow%2520Server%7CWorkflows%7CProcess%2520Details%7C_____4

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings