Workflow configuration for the Identify Product custom step (Production Mapping)
The Identify Product step associates a product with a job by specifying the product library, solution, product class, series, and product. The Check Out and Check In steps use this association to perform their operations. The Launch ArcMap step may also be configured to use this association.
A series of parameters is available to customize the step execution behavior to align with the way you organize and manage products within the product library.
The table below outlines each step type argument and associated behavior:
Name | Description | Argument example | Behavior |
---|---|---|---|
Product Library (optional) | Identifies the product library of the product to be associated with the job. Three options are available:
| Define on Job is the default; no argument specified. | On step execution, you are prompted to choose a product library by selecting a Workflow Manager data workspace or browsing to a personal or file geodatabase. |
/ProductLibrary:MyProductLibrary | On step execution, the product library is set to a Workflow Manager data workspace. This property cannot be updated. Only products within this product library can be associated with the job. | ||
/ProductLibrary: ”C:\Data\My Product Library.gdb” | On step execution, the product library is set to a personal or file geodatabase. This property cannot be updated. Only products within this product library can be associated with the job. | ||
Solution (Optional) | Specifies the solution of the product to be associated with the job. Two options are available:
| Define on Job is the default; no argument specified. | On step execution, you are prompted to choose a solution from a list populated based on the selected product library. |
/Solution:MySolution | On step execution, the solution set on the step type is displayed but cannot be updated. Only products within this solution can be associated with the job. | ||
Class (Optional) | Specifies the product class of the product to be associated with the job. Two options are available:
| Define on Job is the default; no argument specified. | On step execution, you are prompted to choose a class from a list populated based on the selected solution. |
/Class:MyClass | On step execution, the class preset on the step type is displayed but cannot be updated. Only products within this class can be associated with the job. | ||
Series (Optional) | Identifies the series of the product to be associated with the job. Two options are available:
| Define on Job is the default; no argument specified. | On step execution, you are prompted to choose a series from a list populated based on the selected class. |
/Series:MySeries | On step execution, the series preset on the step type is displayed but cannot be updated. Only products within the series can be associated with the job. | ||
Product (Optional) | Identifies the product to be associated with the job. Two options are available:
| Define on Job is the default; no argument specified. | On step execution, you are prompted to choose a product from a list populated based on the selected series. |
/Product:MyProduct | On step execution, the product preset on the step type is displayed but cannot be updated. This product will be associated with the job. | ||
Map Document (Optional) | Specifies the map document to be checked out with the product. Three options are available:
| Use Existing Product MXD is the default; no argument specified. | Each product has a primary map document. With this option, the primary map document is associated with the job. On checkout, the product's primary map document is checked out. This is the appropriate setting for most workflows. |
/MXD:DefineOnJob | In some scenarios, multiple map documents are associated with a product. On step execution, you are prompted to choose which map document you want to work with from a list of map documents associated with the product. On checkout, the selected map document is set to be the primary MXD for the product and is checked out. | ||
/MXD:MyMapDocument2.mxd | In some scenarios, multiple map documents are associated with a product. On step execution, the map document preset on the step type is displayed but cannot be updated. This map document will be associated with the job. On checkout, this map document is set to be the primary MXD for the product and is checked out. | ||
Update AOI (Optional) | Specifies whether or not the job's area of interest is updated to match the product's area of interest. Two options are available:
| Update AOI is the default; no argument specified. | On step execution, the job's area of interest is set to the product's area of interest. |
/UpdateJobAOI:False | On step execution, no action is taken. The job's area of interest is not updated. |
The arguments outlined above must be input according to the product library structure. For example, to predefine the product class, the solution and product library must also be defined. Further, the product class must exist within that solution and product library. The argument editor enforces this behavior.