Declined

change a process version on the fly

When a process is updated in development, the cases in progress follow the new process route smoothly. On the countrary, when a new process version is deployed into production, the cases in progress follow the version they picked up when started.

It's a bullet-proof option indeed but on the other hand it limits the agility considerably. As an illustration, it was so important for one of our customers that they opted to run productional processes on the development server! (Which has obvious negative effects indeed.)

Please make it possible to migrate cases in test/production to a new version after it's deployed. It may be done for all cases in progress and/or by a single case basis. If a case in progress has an active task which is missing in the new version then the migration isn't possible but with a minimal precautions taken by an analyst such migration should be safe enough.

I believe this feature would look nice from marketing/competition perspective too.

Best Answer
photo

Thank you for your interest in Bizagi

This suggestion has been declined because once a case is created in a version it will remain in it until the end. You cannot upgrade a case from version.

This is absolutely important to preserve the integrirty of cases.

Regards.

photo
0

It'd allow to build processes following its inherent logic, and apply smoothly the methods of continuous improvement not looking back at how to "optimize" those processes to make it possible.

photo
0

Thank you for your interest in Bizagi

This suggestion has been declined because once a case is created in a version it will remain in it until the end. You cannot upgrade a case from version.

This is absolutely important to preserve the integrirty of cases.

Regards.