- Fri Feb 06, 2009 12:12 pm
#1499
I've had a number of issues when attempting to import a new version of a process ontop of an existing process. These are showstoppers for anything planned to be a production implementation. Worst case so far, is complete deletion of an existing process and all cases, meaning we have lost all case history which is not an acceptable risk, and all in-flight cases are lost as well.
There are 3 options available when importing a process to overwrite an existing process. The manual does not clearly define what happens with each of these options, and from experience, it greatly affects the inner workings of the processes if you select the wrong one, or in later updates, select a different option.
There are some absolute requirements that need to be met with any production tool that apply here, and I think need to be safegarded for ongoing use and changes to processes
There are 3 options available when importing a process to overwrite an existing process. The manual does not clearly define what happens with each of these options, and from experience, it greatly affects the inner workings of the processes if you select the wrong one, or in later updates, select a different option.
There are some absolute requirements that need to be met with any production tool that apply here, and I think need to be safegarded for ongoing use and changes to processes
-
[*]Case data needs to have a level of security that prevents wholesale deletion. All Cases must be maintained and available after a change to the process
[*]Case data should be available for export as a backup procedure, and available for import if an update fails to complete as expected. This should allow for a selection of the correct process when importing, to ensure that the cases are assigned to the correct process.
[*]The collective Process AND Cases should available for export to allow for modular backups, and potential recovery of a process with case data in the event of a failed update.
[*]In the scenario that a process update changes significantly enough to 'orphan' a case at a no-longer existant task, some form of administrative case-to-task reassignment needs to be available.