Bulk Actions (Classic)

Important: This topic is for the Classic Record experience. To view the content for the Next Generation Record experience see Records. For information on Classic experiences, see Archer Classic Experiences.

Bulk actions enable to you take an action on multiple records in a single application simultaneously.

For more information about packaging an application in which you have bulk actions, see Packaging Rules.

On this page

Bulk Action Permissions

You must enable fields in the application for bulk actions. You must also update access roles to allow users to perform on-demand bulk actions. See Bulk Action Permissions.

Bulk Action Configuration Settings

You can configure settings for how the system processes bulk actions. For information, see "Configuring Bulk Action Settings" in the Archer Control Panel Help.

Bulk Action Types

Here are the types of bulk actions available:

  • Bulk update. Enables users to update a large selection of records with the same values for various fields, instead of updating records individually. (Bulk update is not supported for sub-forms.) You can perform bulk updates on the following field types:
    • Text
    • Date / Time
    • User / Group
    • Values List
    • Numeric
    • Record Permissions
    • Cross-Reference / Related Record

      Note: If both Bulk Action and Dynamic Filters are enabled in a cross-reference field, you cannot use Bulk Update to update the cross-reference field. The Bulk Update cross-reference lookup displays the message "No Records Found."

  • Bulk create reference. Enables users to create reference records (cross-reference or related records) in a different application. The created records are associated to the original records through the designated cross-reference or related records fields. (Bulk create reference is not supported for sub-forms.)
  • Bulk enroll content. Enables users to enroll many records into an advanced workflow at once.
  • Bulk delete. Enables users to delete multiple records from a Search results page.
  • Bulk inline edit from a cross-reference grid. Enables users to select values for fields in a cross-reference display grid and have them applied to all the cross-referenced records. For more information, see Inline Editing.

Bulk Action Methods

There are also 2 methods for performing actions in bulk.

  • On-demand. Enables you to bulk update, bulk create reference, or bulk delete multiple records simultaneously from the Search results page, or to bulk inline edit from a cross-reference grid in a record.
  • Scheduled. Enables you to automate a bulk update or bulk create reference action by scheduling them to occur at a frequency of your choice. You can schedule bulk actions on all of the same field types supported for on-demand bulk actions. However, you do not need to enable individual fields in advance.

Bulk Action Notification Types

The system includes 2 admin notifications types for bulk action job status notifications: 1 for on-demand actions, and 1 for scheduled actions. For instructions on configuring admin notifications, see Adding Admin Notifications.

Bulk Action Permissions

A user without the System Administrator role can view the following:

  • Status of the jobs they created (they cannot view the status of jobs created by others).

  • Bulk Action History report for the jobs they started.

A user with Read permission selected for Set Up/Maintain Workflow Job Status Access Right can view the following:

  • Status of all jobs through the API call: http://localhost/Archer/api/V2/internal/JobStatus(X). (They cannot view all Jobs status on the Bulk Action History page.)

  • Jobs they created.

Users with the System Administrator role can view the following:

  • Status of all jobs in the system in the Bulk Action Bulk Action History page

  • Status of all jobs through the API call: http://localhost/Archer/api/V2/internal/JobStatus(X)

Schedule Owner, Configuration Administrator, and Sysadmin Administrator permissions

  • Schedule Owners (assigned in the schedule) have the ability to edit their schedules and actions.
  • Configuration administrators can update or delete any schedule that targets their application and can assign another user in the Schedule Owner and Run As fields.
  • System administrators can update and delete any schedule in the system and can assign another user in the Schedule Owner and Run As fields.