Defense Mapping custom steps
A series of custom steps are available to streamline and automate ESRI Defense Mapping TDS production workflows. However, these custom steps are generic in their construction so that Workflow Manager workflows can be constructed using these steps in production using any type of the Defense Mapping supported products.
The following custom steps and tokens are available to run with Workflow Manager:
Step name | Prog ID | Description | Return codes |
|---|---|---|---|
Add Job Hold Step | DefenseMappingSteps.AddJobHoldStep Arguments:
| Creates a hold on the job and halts progress through the rest of the workflow until the hold is removed |
|
Check AOI Step | DefenseMappingSteps.CheckAOIStep | Checks for the existence of the job AOI and provides a return value that allows the workflow to branch as appropriate |
|
Check Extended Property Step | DefenseMappingSteps.CheckExtendedProperty Step Arguments:
| Checks for a value in an extended property field and returns a specific value used for branching the workflow based on a comparison of the value in the extended property field and any match found in the JTX_AUX_PROPS_RET_CODES table | The value identified in the record for proper workflow branching |
Create Child Job Advanced Step | Arguments:
| Incorporates all the functionality from the Workflow Manager sample included with the 10.0 SP2 installation, and adds new functionality to allow you to define more than a single extended property to update the new jobs |
|
Enqueue Job Step | DefenseMappingSteps.EnqueueJobStep Arguments:
| Queues the job for synchronization or reconcile/post through the use of the ProcessEdits python script |
|
Execute GP Tool Step | DefenseMappingSteps.ExecuteGPTool Step Arguments:
| Executes a geoprocessing tool, script, or model as defined in an ArcGIS toolbox |
|
Get Edited Feature Count Step | DefenseMappingSteps.GetEditedFeatureCountStep Arguments:
| Updates an extended property of the WMX job with a total number of edited features by reviewing the archive tables of the associated feature classes and counting the changes made within the job and posted to the default version of the central database |
|
JTX Add Attachment Step |
DefenseMappingSteps.JTXAddAttachmentStep | Opens a dialog box that prompts you to add attachments to the job if necessary | N/A |
Resource MXD Step | DefenseMappingSteps.ResourceMxdStep Arguments:
| Resources the layers of an MXD from one data source to another, assuming that the feature classes are named the same in both data sources and that the original data source is known |
|
Select Data Workspace Step |
DefenseMappingSteps.SelectDataWorkspaceStep | Displays a list of data workspaces defined in the WMX Administrator in a dialog box; you can then make a selection of a single data workspace, which will then be assigned to the job |
|
Set Data Workspace Step | DefenseMappingSteps.SetDataWorkspaceStep | Copies the data workspace properties of one WMX job to another |
|
Set Production Properties Step | DefenseMappingSteps.SetProductionProperties Step Arguments:
| Configures the product library settings required for the job's database to connect to the correct product library so that when ArcMap is launched from the workflow, the product library settings are already configured |
|
Set Property Based On XML Step | DefenseMappingSteps.SetPropertyBasedOnXMLStep Argument:/xmlFilePath:<file location> Ex. /xmlFilePath:"c:\installdir\stepconfig.xml" | Generates a selection list based on the contents of an XML file stored on disk | Unique value |
Verify Status Step | DefenseMappingSteps.VerifyStatusStep Argument:/hideStatusDialog(optional) | Determines the status of an externally run process by checking the value of an attribute in a record associated with a job |
|