We recently did an upgrade from 10.0 to 10.2.2. To get to 10.2.2 we created a clone of our 10.0 database (called it ed6) and then upgraded both the SDE and WMX to 10.2.2. In this cloned database we then tested our existing workflows, created a number of new workflows, steps, etc. We then took our production 10.0 database offline, (ep4) upgraded it to SDE 10.2.2 and WMX 10.2.2. To get the tested changes we made into our production 10.2.2 database we exported the testing configuration from ed6 and merged into ep4, Overall this is working well but we have run into one issue.
We are finding that the behaviour of the auto execute is not the same as it was in 10.0. Because of this our users now find themselves in old jobs (created before the upgrade), in an endless loop. Here are the steps:
- Procedural step to start the job
- Create Version - not auto execute, proceed to next step
- Launch ArcMap - auto execute, proceed to next step
- Question step"more edits" - auto execute, proceed to next step
- If yes, return to step 3
- If no, reconcile and post changes
If the user selects yes in step 4, they are sent back to Launch ArcMap (step 3) which automatically executes. When they exit ArcMap, the more edits step automatically runs. If they say yes, ArcMap opens, and they are stuck in a loop. The only way the user can get out of the loop is to answer No to step four. This will move them to the reconcile and post. In order for them to return to continue editing, we need to set the step back to the Launch ArcMap for them. Generally we do not give our users the ability to set step.
As these are existing jobs, changing the steps in the workflow does not affect them. We have found a workaround which is to alter the autorun value in the JTX_JOB_STEP table for the existing jobs. For example:
set autorun = 0
where job_id = 27749 and step_id = 34803;
How much trouble can we get into with making changes directly in these tables?