April 2026 Release: Bulk Action Framework Features & Enhancements

Bulk Action Framework

Feature: Bulk Action An action that is performed for a large volume of data (for example, an email sent after selecting a large number of Candidates) Framework
Level of Configuration: Low

This enhancement introduces the possibility of configuring Bulk Actions so that the fields that would normally be filled in by the Automated User In Salesforce terminology, this is anybody that has login access to an instance. In Bullhorn Recruitment Cloud instances, usually the staff of recruiting companies name (like ‘Created by’, ‘Last Modified by’, etc.) are instead populated with the Context User’s Name.

If the new setting is not selected, the current behaviour is retained: when users (or AI Agents) initiate a Bulk Action When used in ATS or Search and Match UI, one of multiple actions available after user has selected a sub-set of Candidates (e.g., Mass Email, Mass Placement The stage that occurs after a candidate accepts a job offer and facilitates their information being copied to the back office., Add to Call List in bulk, etc.), the system offloads the execution to a generic user ("Automated Process User”). Consequently, all downstream records created by this process (Tasks, Applications, Logs) are attributed to the generic user rather than the initiating user.

Please refer to this article for more details: Bulk Action Framework

Support for available actions will be added iteratively in the next few releases. In this release, we have added support for the following actions:

ATSv2 In Bullhorn Recruitment Cloud, the newest version of the ATS tool (Application Tracking System)> Apply To Other Job (bulk action that creates Applicationv2 records)
ATSv2> Internal Interview The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. (bulk action that creates SendOut A Client Submission (Sendouts, CV Sent) occurs when a recruiter sends a candidate to the hiring manager for approval to have an interview. Schedulev2 records)
ATSv2> Move To Stage (bulk action that creates Applicationv2 records)
ATSv2> Add To Call List (bulk action that creates Call List Member records)
ATSv2> Reject/Unreject (bulk action that updates Applicationv2 records)
USAM> Add To Job (bulk action that creates Applicationv2 records)
USAM>Add To Call List (bulk action that creates Call List Member records)
Call List> New Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) (bulk action that creates Applicationv2 records)

Configuration Steps

This is an opt-in feature. To enable it, set the Run Action As Invoking User field to True on the relevant Bulk Action Definition record. Once enabled, the User field on records created by the bulk action will show the name of the context user. This option is also available for Flow-based Actions that run as bulk actions.