Has anyone else run into an issue when promoting Workflows from one environment to another? Records Management Activities almost always break, for example, in a current workflow, we assign a file date, cutoff instruction, event date, and finally a retention schedule. Each of these is set based on a conditional which evaluates which set of these variables each document should receive. For example a document may go down a branch that has the event based cutoff instructions set as the expiration date of the document. 

When transferring these Retention objects from one admin console to another and importing the workflow, all of the cutoff instructions are switched to another cutoff instruction. So, Termination date event activity may now be in the Expiration date path and vice versa. The fix is of course to go through each cutoff instruction activity and set it back to the correct instruction.

In my most recent migration to a production environment, I now am running into an issue where workflow is attempting to set the termination event date and it is terminating the workflow and telling me "One or more of the selected events are not valid for this records management object. [9116]" The fix for this is to delete the event from the workflow activity and re-add it. 

Obviously there are some bugs when it comes to migrating workflows with RME activities. I am wondering if anyone else has experienced these issues and if Laserfiche knows about this.

- Justin