[senseq]

We have a workspace called 'sysT' and another one called 'sysP'.

It is ideal that all our BPM changes first happen in sysT and get tested there, and then we move the changes over to sysP, where live cases of customers are managed.

Are there any suggestions on how we should rollout the changes to sysP by making sure there are minimal impacts to existing cases on the system.

Any guidance on a robust rollout strategy would be appreciated.

Thank you!

[quipper8]

I haven't got enough processes yet to worry about automating much, but I have thought about it.

You can see the importer and exporter code here

https://github.com/colosa/processmaker/ ... porter.php

https://github.com/colosa/processmaker/ ... porter.php

The process files themselves are plain text, so I would put push them to git(I use gitlab for other stuff already) so you could preserve all versions and use the classes above in some custom php

so, process is done in sysT, run your script to:

-Export from workspace sysT whatever process ID
-push to a file named that processID in gitlab
-Import to workspace sysP using the overwrite options