Manage Workday

Updated the Next Steps section to document the new background job processing for high volumes and exact time options for start and end dates.

Updated the User to Perform Orchestration Launches field description to specify the user context and added a note on required permissions. Updated the step sequence for selecting the Orchestrations tab, viewing the execution status, and using the Refresh Status button. Updated the Result section to describe execution behavior for single UI, default user context, mass actions, and condition rules.

In step 2, expanded the Recipients row to describe the Exclude Delegates in Notifications check box.

Clarified how Workday generates dynamic documents when configured as an action step on a business process.

Added a domain to the Security section, enabling you to access the View Audit Trail link.

Added a bullet in the Recommendations section that describes considerations for enabling automated background processing. Added configuration guidance for automated background processing in the Tenant Setup section.

Added an option to step 4 in the Steps section and clarified the Results section.

How to enable Engagement Builder background processing in a non-production tenant.

How to migrate legacy campaigns to Engagement Builder.

Added a new Calculated Fields section. Clarified the Data Source Filters section and removed the Prompts section.

Added a row on engagement insights.

Added a row on configuring email routing.

Answers frequently asked questions about legacy campaign migration.

Removed Example section.

Added new behavior in Step 3:

In the Sequence ID Format row: For sequence generators created before the custom sequence generator locale enhancement, Workday now evaluates any unspecified locale-dependent variables using the configured tenant locale.
In the Sequence Generator Locale row: This field now defaults to the configured tenant locale.

Added these details:

Workday uses the locale definition from the Sequence Generator Locale prompt to evaluate locale-dependent variables in the Sequence ID Format field.
For sequence generators created before the custom sequence generator locale enhancement, Workday now evaluates any unspecified locale-dependent variables using the configured tenant locale.

Renamed the topic from Concept: ID Definitions and Sequence Generators to ID Definition and Sequence Generator Information. Also added:

In the Defining Sequence Generators and Gapless Sequence Generators section that for sequence generators created before the custom sequence generator locale enhancement, Workday now evaluates any unspecified locale-dependent variables using the configured tenant locale.
In the Custom Sequence Generator Locales section that Workday now evaluates locale-dependent variables in sequence generators using the locale definition selected in the Sequence Generator Locale prompt.

Renamed the topic from Reference: Sequence Generator Variables to Sequence Generator Variables.

In the Projects section, renamed the Forecast options to Global Forecast, and added the Allow Multiple Resources for a Single Assignment option.

Added information about the:

Enable Tax Declaration Netting Transaction Grouping by Worktags check box in the Tax Options section.
Flatten Remittance Advice and Enable Tax Recovery on Invoice Write-Offs check boxes in the Customer Account Options section.

Added information about the Use Effective Dating for Service Dates feature.

Added a new Engagement Builder Settings section. Added new options and descriptions for enabling automated background processing.

Renamed the SMS Compliance section to WD Messaging Compliance and updated the section to include the WhatsApp channel.

In the Payroll Accounting section, added a row for the Allocate Net Pay Liability - Exclude Earnings option.

Added more information on how to enable passkeys and web authentication.

Updated details about the Career Hub.

In the Steps section, added Step 5 to set up WhatsApp notifications.

Updated this topic with the new WhatsApp channel for Workday Messaging.

Updated this topic with information and setup steps for the new WhatsApp channel for Workday Messaging.

How to create a WhatsApp conversational messaging configuration.

Updated with the new WhatsApp channel for Workday Messaging.

Added a Channel column to the table to identify the channels available for each country.

Added My Conversations support for Candidate Conversational Messaging for WhatsApp.

Added My Conversations support for Candidate Conversational Messaging for WhatsApp.

Added WhatsApp as a Notification Category to Message Builder Templates.

Provides information on WhatsApp Message template classifications, approval submittal, and formatting guidelines.

How to create segment-based security groups in WhatsApp Messaging for recruiting candidates.

Updated:

Use case section by adding a line about the new sections
Updated the special consideration section by adding a line after 4th bullet list.
Updated the Steps to Set Up Custom ConnectR by adding a new bullet list about add section to workday-delivered.

Replaced the Wizard word with ConnectRs

How to Customize Workday-Delivered ConnectRs.

Updated the existing topic based on the 26R2 release

Updated the Context Section
Updated steps 9 and 10

Updated the info based on the 26R2 release to add visiblity rules to existing or new navigation items or groups.

Updated the context section
Added the steps 7 and 8
Added the Next Step section

How to create configurable hubs.

Added a inline linking in the step 3

Added a inline linking: create themes and sub-themes

How to create themes and sub-themes.

Updated to account for Benefits functionality.

Updated the Migrate Security Configuration Packages description in step 3 to mention domain and business process security configurations.

Updated the Object Transporter Migration Use Cases section to include security groups and their business process security policy permissions.

In the Premigration differences check section, updated the Modified tab description in the table to clarify that security group and business process security policy migrations are additive only.

Updated:

Security configuration package information in the Context section to include security groups, domain security policies, or business process security policies associated with a specified functional area.
The note in the Remove Security Groups from Target Tenant description to clarify that Workday does not remove security groups from business process security policies.

Updated the edit migration behavior step to include security groups and functional areas, and clarified in the Edit Migration Behavior table that security group migrations are additive only.

Updated step 14 to include security policies, groups, or functional areas that differ from the corresponding security configurations.

Updated step 18 to include security policies, groups, or functional areas that differ from the corresponding security configurations on the target tenant.

Updated step 12 to include security policies, groups, or functional areas that differ from the corresponding policies on the target tenant.

Updated to:

Clarify the differences between the non tenant-aware agent and the ASOR-enabled agent, which can read configuration metadata across non-production tenants.
Rename the task to Deployment Agent (Q&A).
Clarify operational limits.

Renamed:

The Configuration Intelligence underlying skill to Implementation Knowledge.
The task to Deployment Agent (Q&A).

Also clarified agent skills, underlying skills, and capabilities.

Renamed the task to Deployment Agent (Q&A).

Updated to:

Rename the task to Deployment Agent (Q&A).
Show how users now access the Deployment Agent (Q&A)task.

Added information on rich text editor and a related link to the release note after Step 4.

Created a new topic.

Created a new topic.

Added information about the Use Effective Dating for Service Dates feature.