Associating batch jobs with product classes

To associate batch jobs with the current map data, a product library and production database must be specified. If you are not using a product library, you can upgrade a database to a product library and use the current data workspace as the production database. Once those two workspaces have been specified, a new data model is created based on all the feature classes in your production database.

However, if you are using an existing product library that contains data models, you can also choose to use an existing data model or create a new version of one.

The Associate Batch Jobs command allows you to associate three types of batch jobs with the product library. The batch job types are named based on the types of checks that should be included. For example, the Attribute batch jobs should only include attribute checks, and the Spatial batch jobs can include checks that validate spatial properties of the data such as the geometry, spatial relationships, and so forth.

Nota:

Spatial batch jobs should not include advanced checks or checks that run on the full database. These should only be included with the Reviewer batch job.

When you associate the batch jobs with the new data model, you are checking them into the product library. They are automatically associated with the product class created based on the current map data.

Learn more about associating batch jobs with product classes

Reviewer batch jobs are created with Data Reviewer and can be linked to the data currently loaded in your map with the Associate Batch Job tool. You can associate several batch jobs with the product library and associate them with any of the following categories:

• Attribute—This type of batch job contains checks that can be run through the Feature Manager, either in batch from context menu on the Create or Update tabs or once attributes are edited and applied to a single feature.
• Spatial—This type of batch job contains checks that can be run using the Validate Current Selection or Validate Current Extent tool.
• Reviewer—This type of batch job contains checks that can be run using various tools in a Reviewer session.

Pasos:

1. Start ArcMap.
   Sugerencia:

   If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.

2. On the main menu, click Customize > Toolbars > Production Editing.
3. On the Production Editing toolbar, click Production Editing > Associate Batch Jobs.

   If a product library has already been specified, the Update Workspace message appears. Proceed to step 6.

   The Set Product Library dialog box appears.

4. Click Browse.

   The Choose Product Library Location dialog box appears.

5. Navigate to the geodatabase that is going to be used as the product library.
6. Click Open.

   The Set Product Library dialog box appears with the path to the specified geodatabase.

7. Click OK.

   The Update Workspace message appears.

8. Click Yes to update the geodatabase.

   The geodatabase is updated to a product library, and an Update Workspace message prompts you to update the workspace for the data to a production database.

9. Click Yes to update the data workspace.

   The production database tables are copied to the current workspace, and a new data model is created based on the feature classes in the geodatabase.

   The Set Product Library dialog box appears.

10. Click OK.
11. Click the Product Library Batch Job Manager button.

    The Batch Job dialog box appears.

12. Click the Batch Job Type drop-down arrow and choose a category for the batch job.

    You can choose to add a batch job for the Attribute, Spatial, or Reviewer category.

13. Click the ellipsis (...) in the Batch Job cell.

    The Check in Batch job file dialog box appears.

14. Choose the batch job you want to associate with the product library.
15. Click Open.

    The Batch Jobs dialog box appears with the name of the batch job you added in the Batch Job Name cell.

16. To add another batch job, click the header for the next row in the table and repeat steps 12–15 for each batch job you want to associate with the product library.
17. Click and drag the slider in the Error Severity area to indicate which check results are going to be considered errors that need to be fixed before changes can be committed or posted to the database.
    • None—The severity assigned to each check is ignored.
    • 1—Only results from checks with a severity level of 1 are considered errors.
    • 1–2—Only results from checks with a severity level of 1 or 2 are considered errors.
    • 1–3—Only results from checks with a severity level or 1, 2, or 3 are considered errors.
    • 1–4—Only results from checks with a severity level of 1, 2, 3, or 4 are considered errors.
    • All—All the results of the checks are considered errors.
18. Click OK when you are finished associating batch jobs with the product library.