Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Bulk actions

Creating bulk actions

Bulk actions allow users to perform actions on documents returned by the search queries of a Solr index. This allows for batches of documents to be processed from an index instead of manually needing to apply actions and affects those present through both HCP and S3 Compatible connectors.

The query will include any query settings or additional refinements and facet selections applied from within the Search App.

NoteThe addition of custom query parameters under the Custom Parameters section of Query Settings is not guaranteed to affect the results of the query acted upon by the bulk action.

To create a bulk action:

Procedure

  1. In the Search App, select your index from the All dropdown on the left-hand of the search bar.

    The Create Bulk Action button (GUID-C2D0EE96-BD8D-451F-A689-99AF016F03D5-low.png) appears on the right-hand of the search bar.
    NoteCreate Bulk Action only appears if:
    • Bulk actions are enabled in the query settings of an index.
    • An index is available and selected. If a user only has a single index, the All dropdown is not displayed and their index is chosen by default.
  2. Click Create Bulk Action.

    The Create Bulk Action menu appears.
  3. In the Description field, enter a brief description of the bulk action (optional).

  4. From the Bulk Action dropdown, select an action (required).

    • HCP Apply Hold: For each query result, this action applies hold to the corresponding HCP objects.
    • HCP Clear Hold: For each query result, this action clears hold to the corresponding HCP objects.
    • HCP Delete: For each query result, this action deletes the corresponding HCP objects.
    • HCP Privileged Purge: For each query result, this action completes a privileged purge of the corresponding HCP objects. An additional config property to log a reason for this privileged delete is required.
    • HCP Privileged Delete: For each query result, this action completes a privileged delete of the corresponding HCP object). An additional config property to log a reason for this privileged delete is required.
    • HCP Purge: For each query result, this action purges the corresponding HCP objects.
    • HCP Set Retention: For each query result, this action sets retention on the corresponding HCP objects. An additional config property to log a reason for this privileged delete is required.
    • S3 Compatible Apply Hold: For each query result, this action applies hold to the corresponding S3 objects.
    • S3 Compatible Clear Hold: For each query result, this action clears the hold on the corresponding S3 objects.
    • S3 Compatible Delete Objcet: For each query result, this action deletes the corresponding S3 objects.
    • S3 Compatible Set Retention: For each query result, this action sets retention on the corresponding S3 objects.
      • Retention Mode: Selecting GOVERNANCE protects an object from being overwritten or deleted by users without admin permissions. Selecting COMPLIANCE protects an object from being overwritten or deleted by any user, including the root user. A retention mode must be selected in order to use this bulk action.
      • Retention Period: The retain until date that protects the object version until the retention period expires.
    • S3 Compatible Set Tags: For each query result, this action sets the specified tag on the corresponding S3 objects.
      • Maintain Existing Unspecified Tags: If enabled (default), this setting maintains any existing tags that do not match the metadata prefix property. If disabled, the tags are deleted.
      • Use version id: If enabled, tags can be set on an object for a specific version ID. If disabled (default), the latest version ID will be used.
      • Tags to set: The name value pairs to be used as tags on the corresponding S3 objects.
  5. Click Create.

    The bulk action is created and a confirmation message appears.
  6. To view your bulk action, click your username at the top-right corner of the window and select Bulk Action Status. For more information on status, see Bulk action status.

    The Bulk Action List page appears and displays all of your bulk actions.

Next steps

After a bulk action has been completed, the results can either be stored or deleted. To delete a bulk action, see Deleting bulk actions.

Deleting bulk actions

After a bulk action has been created, it is stored in the Bulk Action Status menu until it is deleted.
ImportantDeleting a bulk action deletes all associated workflow components. Ensure a delete was intended before proceeding.

To delete a bulk action:

Procedure

  1. Click your username at the top-right corner of the window and select Bulk Action Status.

    The Bulk Action List page appears and displays all of your bulk actions.
  2. Navigate to your listed bulk action and then click Delete.

Bulk action status

Bulk action status can be viewed by clicking on your username at the top-right corner of the window and then selecting Bulk Action Status. The Bulk Action List page then appears and displays all of your bulk action information.

NoteTo return back to the home page of the Search App, click Back to Search in the top-left corner of the window.

The status of your bulk action is automatically updated as it is applied, from Pending to Running to Completed. To manually refresh the status to see the current number of processed documents, click the Bulk Action List refresh button.

The following status information is available for all bulk actions:

  • Dropped: The total number of documents that the bulk action dropped.
  • Failure: The total number of documents which the bulk action has failed.
  • Index: The index the query is being run against.
  • Input: The total number of documents which the bulk action has seen.
  • Status: The status of the underlying workflow.
  • Query: The query string used by the bulk action.

    NoteDocuments acted upon by the bulk action will be those returned from this query at the time the bulk action was created.

 

  • Was this article helpful?