nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow Manager ArcMap Launch not choosing job version

AllWeatherHeather

I am migrating a 9.3 system to 10.2.2 and part of that includes upgrading a number of JTX jobs to Workflow Manager. In my migrated workflows I create a job version of the data (successfully) then when ArcMap is launched it defaults to the parent version of the data. I can then manually change the version to the one I want but this will be an extra step that our users will often forget.

Has anyone else had this problem?

Trouver plus de publications taguées avec

Accepted answers

AllWeatherHeather

Tope,

I installed the patch but it didn't seem to make a difference... however what did work was a suggestion for ESRI Canada support staff to try repairing my Desktop and Workflow Manager installs. I'm happy regardless because everything is working again!

Thanks for your support.

All comments

AllWeatherHeather

Tope,

Thanks for your support.

TopeBello

Heather,

We found an issue with layers not getting repointing to the appropriate version right after releasing 10.2.2 and it sounds like this might be what you are seeing. Can you take a look at this link here? Install the patch and try to see if you the issue still exists.

http://support.esri.com/en/downloads/patches-servicepacks/view/productid/160/metaid/2097‌

Thanks,
Tope

AllWeatherHeather

Tope,

I migrated the job types and workflows using the export import functionality from JTX to Workflow Manager. I created empty feature classes with the same schema in a new 10.2.2 enterprise geodatabase (SQL 2012) and then produced fresh job mxds. When I try to create a brand new job (and job version of the data) ArcMap launches and defaults to the parent version of the date.

I am not trying to migrating existing jobs at this time, just move the job type over and test it in the new environment.

Thanks,

Heather

TopeBello

Hi Heather,

It is likely that during the upgrade, the Job Version didn't get migrated along when you performed the process. If you still have a copy of your JTX 9.3 database available, you can compare the version field/data in the JTX_JOBS table between the 2 databases (9.3 and 10.2.2). If the values are different, you can do a join and then calculate the values using standard ArcGIS/ArcMap tools.

Test out your workflow again to see if this resolves it.

Thanks,

Tope

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.