Reference: Event-Specific Best Practices

Set up the

Launch Calibration

business process for a single organization, instead of multiple organizations.

Avoid overlapping the Launch Calibration event with any major deadlines for other customer activities or large volume events.

Review the schedule for long running background jobs, integrations, and reports during Launch Calibration.

Define the

nBox

report to include only fields in Detail Data and necessary facets for the calibration decision process.

Minimize the use of calculated fields in the

nBox

report definition.

Avoid using filters defining a subset of the worker population on the

nBox

report. Instead, use a

Calibration Program Rule

on the

Calibration Program

.

Limit the organization levels in the

Restrict Organization Level View

prompt, under the

Calibration Program

.

Run the

Add Goals to Employees

task during off hours or quiet periods.

For very large volumes of more than 100K workers, you can break up your cascade goals into smaller groups to balance the performance impact. Example: Run tasks by line of business.

Schedule the review period and carefully decide on the important dates: Initiation,

Compensation Snapshot Dates

,

Organization Snapshot Date

, and

Effective Date

. Build in extra time for auditing and to address any technical or data issues that arise.

Avoid overlap between the compensation review and any major deadlines for other customer activities or large volume events.

During the final week of the compensation review, check the schedule for long running background jobs, integrations, and reports.

For an audience size that exceeds 100,000, break up the audience into multiple campaigns.

For campaign schedules:

Include specific due dates when communicating campaign deadlines.
Stagger overlapping campaigns to avoid heavy-traffic for the same day.
Consider other large processes to prevent conflicts with Learning consumption peaks or campaign notifications. Example: Payroll.
When adding a new campaign, consider how the additional media traffic might impact the performance of ongoing media campaigns.
For an audience size of 100,000, Workday recommends a minimum campaign duration of 30 days.

Reduce the number of triggered reminders for static campaigns. Example: A campaign with 55,000 audience members and 3 campaign items (each with a configured reminder) causes Workday to schedule 165,000 reminders.

Avoid learning campaign spikes in content consumption that occur at the beginning and ending of the campaign.

Stagger send and due dates to distribute media traffic.
Avoid starting a campaign on the end date of another.
Spread campaign email out across the work week to avoid heavy traffic on a single day.

Prepare custom reports before the mass archival to track which goals to archive, and to verify the results afterward.

Ensure your custom reports use the same conditions that will be in the goal template rules for the mass archival.

Run the reports and conduct extensive testing before running the production archival.

Archive goals in batches instead of 1 large archive job. Use the mass archival goal template rule to account for the batches. Example: Set up goal template rules to batch by organization.

Run the mass archival during off-hours to minimize impact on workers, and to reduce chances of impacting other processes at the same time.

Disable automatic candidate merging when creating more than 500,000 records.

Create records in batches. Example: Instead of creating 200,000 records at once, create 50,000 at a time.

Test mass loading in your Sandbox environment before loading in your tenant.

When mass loading or creating candidates, avoid using the same phone number or email for all candidates if you have enabled automatic candidate merging.

Launch multiple benefit groups in 1 event, instead of launching an event for each benefit group.

Avoid overlap between the week you close open enrollment and any major deadlines for large volume events.

During the final week of open enrollment, review the schedule for long running background jobs, integrations, and reports.

For very large volumes, you can break the organization into smaller groups to balance the performance impact.

Avoid overlap between the week that self-evaluations are due and any other major deadlines for customer activities or large volume events.

During the final week of self-evaluations, review the schedule for long running background jobs, integrations, and reports.

Access the

Schedule Print for Employee Reviews

task to print reviews or create PDFs in advance. Run during off hours. You can use custom layouts.

Pull the calibration task forward.

Enable the highest-level manager to use

Complete on Behalf of

.

Test the custom report and purge in your Sandbox environment before you purge any data in your tenant.

To avoid unintentionally purging data, always use a filter on the custom report for privacy purges.

Avoid purging more than 25,000 instances at once.

When applying AND and OR filter conditions, verify that the filter returns the correct data in your Sandbox environment before purging in your tenant. Example: You want to purge the candidate John Smith in London by adding a filter condition to the

Name

and

Location

fields. If you use the filter condition John Smith OR London, you purge all candidates named John Smith and all candidates based in London regardless of their names. The correct filter condition is John Smith AND London.

Avoid overlap between running the

Update Profile

step and any other large volume events.

During the final week of the

Update Profile

step, review the schedule for long running background jobs, integrations, and reports.

Access the

Print Talent Cards for Organization

task to create talent cards in advance. Run during off hours. Use custom layouts.