Open topic with navigation

Bulk Update Wizard

The Bulk Update wizard guides a user through the bulk update process, and ensures all necessary settings and data is provided to run the bulk update.

Step 1 - Configuration

In step 1, specify whether an existing configuration should be run for the bulk update, or if a new configuration should be created.

If a user has a saved bulk update configuration they can click the ellipsis button (…) to select the relevant configuration. Otherwise, select Create New Configuration, and click Next.

Step 2 - Operations

In step 2, specify the operations needed for the bulk update to perform. If an existing configuration was selected, all operations are listed in the order they are carried out.

If an operation is not already present, select from the dropdown menu the operations that should be applied to the set of objects.

The selected operation dictates what elements need to be filled out. The required elements vary from operation to operation. For a detailed description of the operations, see the Bulk Update Operations topic within the Bulk Update documentation here.

More than one operation can be applied to a bulk update by selecting 'Add Operation'. To change the order of the operations applied to the update, use the up and down arrows . An operation can be deleted by clicking the .

Important: Ensure that the operations are listed in the order that they are needed to perform. Operations are performed from the top down. This means that operations further down the list overwrite operations further up. This includes when more than one operation is specified. The operations still are applied in the listed order. If one operation fails for an object (ex: due to validation base type mismatch), all changes to the object will be rolled back and the object will be left as if was prior to applying the Bulk Update.

Step 3 - Preview

This screen shows examples of the results of the update. It displays a maximum of 10 objects. For each object the existing data and how the data will look after the update is applied displays.

The preview also displays warnings and errors if an operation that a user has chosen is not applicable. If a user hovers the cursor over the icons, they can see the error or warning text.

Click the Back button to change an operation or parameter. When satisfied with the preview, click Next to continue.

Step 4 - Advanced

In the final step, select one or more options, some of which can be selected simultaneously.

• Selecting Do not run now allows the user to run the bulk update later, and not immediately when the wizard is finished. When selecting this option, a user can still save the configuration, but Auto Approve and Pre-flight are disabled.
• Selecting Auto Approve approves the objects automatically after the update, and then places the objects in the approved workspace.
• Selecting Pre-flight allows a user to perform a test run of the update. When the user clicks 'Finish', the test runs in the background. This will apply the operations selected, and then roll them back. Additionally an execution report and an Impact Report will be generated. Temporary collections will also be created for the objects where the operations were successfully applied, and for the ones were errors were generated. The availability of this option depends on the user's system setup.

Note: It is recommended to always run a Pre-flight test or to try applying operations to a small set of objects before large quantities of objects are updated, as there is no 'undo' functionality for bulk updates.

• Selecting Save configuration allows a user to save the configuration so that it can be used again.

• In the Process Description field a user can write in a name that displays for the background process.
• The Available for object types limits the object types and nodes affected by the bulk update operations. First select an object type from the dropdown, then click the ellipsis button (…) to select the nodes to update.

• Click Finish to complete the bulk update configuration and start the operation(s) in a background process.

For more on monitoring bulk updates through a background process, see the Monitoring Bulk Updates topic in this documentation here.

2018, Stibo Systems