Workflow Manager Custom Steps Doc

3355
1
11-08-2013 08:47 AM
TedCronin
MVP Honored Contributor
http://resources.arcgis.com/en/help/main/10.2/#/Workflow_Manager_custom_steps/00380000001w000000/

Per the Category Save MXDs:

The default behavior, when the /nosavemxd argument is not used, will save the job's map document in the Workflow Manager database. If your map documents are large, you may need to adjust the MAXBLOBSIZE SDE configuration setting.

Could you consider revising this text.  Very Confusing.


Also Per the Save MXD parameter, I am gathering that If I have the Save MXD checked then I should see the listing of the MXD in the
JTX_MAP_STORE table when the Step is triggered or finished.  I currently do not see the MXD in any of the tables.  Also if I set the Store MXDs in shared location parameter, what is the expected behavior?  I am expecting that when a MXD is Saved, then a copy is put here.  I assume these two parameters work in tandem.
1 Reply
by Anonymous User
Not applicable
Hi Ted,

We'll take a look at revising the text to make it more clear in the next release, as the double negative at the beginning is a bit confusing.

Using Launch Arcmap by default: When you make changes and save and close the step the mxd used for that session is saved with the job. This allows users to perform some of their work and return to the same mxd upon Launching Arcmap over and over again, when they come back the next day for example. This mxd can be deleted when the job is archived or deleted or as part of the CleanUp custom step as an option.

If you use the /nosavemxd, every time Launch Arcmap is executed for that job it will load the template map stored for the job type. It will preserve none of the configuration performed by the user.

JTX_MAP_STORE shows all the maps that have been added via the Administrator toolbar in Arcmap or through the Workflow Manager Administrator for use as template maps for Job Types. Or, they can also be used as the display maps for AOI or job results in the Workflow Manager client. They are not the individual job MXD versions, that is why they are not displaying.

Your statements with respect to Store MXD are correct. 🙂

Hope this answers your questions,
Michael
0 Kudos