Related articles:

You can use the Batch Operations object to configure the Workspace DB based on comma-separated files (refer to Batch Operations File Formats).

Batch operations facilitate the data entry and deletion process for large system deployments. Batch operations also provide you with the ability to view in a readable format the binary Workspace DB data using the Export Database action (refer to To upload batch files onto system).

The batch operations are fully distributed over of the n-peers by the master. The PCE reads each line and creates or deletes the associated object and then validates the non-createable attributes for additions or replacements. If the creation or validation fails, the object is skipped accordingly. For deletion, each line is read to uniquely identify the object. If the object is found, it is deleted accordingly. When the object is valid, the master PCE forwards the resulting object to all peers.

Batch Operations Restrictions

During the batch operation process, the Workspace DB is locked and no UI modifications can take place until PCE has completed the batch operation.

 

 

  • No labels