Technical accuracy note (v1.1): Workday-specific task names and behaviors in this version were rechecked against current official Workday Administrator Guide and Workday Education documentation in August 2026. Tenant-dependent recipient fields, security groups, notification topics, data sources, business objects, and UI labels remain marked for validation.
Representative technical work product. This SOP demonstrates a Workday reporting and People Systems operating approach and is not presented as a prior-client deliverable. Tenant configuration, security, business objects, data sources, and organizational policies must be validated before implementation. Warren Sanders is not a Workday-certified consultant.
1. Purpose
This SOP defines the end-to-end process for designing a custom report that drives a Workday configurable alert and then configuring that alert through the Configure Alert task for daily notification delivery.
Workday alerts are report-driven. The report's filter criteria define the exception condition; Workday generates a notification for each report instance returned and groups notifications by recipient when more than one instance belongs to the same recipient.
2. Business Scenario
Alert name (example): Daily — Overdue Recruiting Action Exception
Illustrative business need: Notify the appropriate recruiting stakeholder when an active requisition meets a defined exception, such as:
- Requisition open more than a defined threshold with insufficient pipeline activity
- Candidate or recruiting action overdue beyond a defined threshold
- Target fill date approaching without a required milestone
[TENANT-SPECIFIC — threshold definitions, fields, recipient relationships, and policy require client validation]
Cadence: Daily, example 7:00 AM
Delivery: Workday notification and/or email depending on tenant setup and user preferences
3. Prerequisites
| Access | Purpose |
|---|---|
| Notification Alerts domain | Secures the Configure Alert task |
| Report Writer membership + Custom Report Creation | Required for the user creating/editing the alert-driving custom report |
| Data-source and field security | Required to build and test the underlying report |
Alert-compatible report design
Workday recommends using Simple or Advanced report types for configurable alerts. Workday alerts do not support Filter on Aggregations or Subfilters. Composite/matrix combinations also have documented alert limitations.
Design implication: If the business condition depends on a related-object count or aggregate, do not assume an aggregation filter will work for an alert. Validate whether an appropriate field or calculated-field design can place the condition on the primary business object without unsupported alert filter criteria.
Prompt requirement
If the alert-driving custom report contains prompts, Workday requires each prompt used by the alert to have a default value and Do not prompt at runtime selected on the report definition's Prompts tab.
4. Part A — Build the Alert-Driving Report
Step A1: Select the report type and data source
Use Create Custom Report. For this example, select Advanced because the use case benefits from richer filter and field options; Advanced is a design choice, not a generic requirement for all alerts.
Use the Data Sources and Business Object Details reports to validate the data source, PBO, available fields, and security in the client tenant.
Step A2: Define the exception filter
The filter is the alert condition. Every report instance returned can generate a notification, so the filter must return only actionable exceptions.
Requisition Status = Open [TENANT-SPECIFIC]
AND
(
Days Open > [threshold] [TENANT-SPECIFIC]
OR
Pipeline Exception Indicator = True [TENANT-SPECIFIC]
)
Do not use Filter on Aggregations or Subfilters for the alert-driving condition. If the desired exception cannot be expressed without them, redesign the data/report logic with a Workday reporting administrator before proceeding.
Step A3: Add fields needed for action
Include only the fields recipients need to understand and act on the exception. Example concepts: requisition reference, job title, accountable manager/recruiter, age of exception, target date, and status. Exact field names are tenant-specific.
Step A4: Configure prompts
- Open the report definition's Prompts tab.
- For every prompt required by the report, set an appropriate default.
- Select Do not prompt at runtime.
- Remove prompts that are unnecessary for the alert-driving report.
Maintainability recommendation: If an interactive report needs flexible prompts but the alert requires non-interactive defaults, consider a dedicated alert-driving copy rather than weakening the interactive report's usability.
Step A5: Test the report by itself
- Run it with the intended defaults.
- Validate known positive and negative cases.
- Confirm zero exceptions returns zero report instances.
- Confirm each returned instance represents a notification worth sending.
5. Part B — Configure the Alert
Step B1: Access Configure Alert
Search Configure Alert and select the alert-driving report.
Workday derives the Notification Topic from the custom report's Data Source and Primary Business Object. Validate the resulting topic before continuing.
Step B2: Configure recipients
The exact recipient controls depend on report context, notification topic, tenant configuration, and current release. Configure only the recipient options Workday presents in the tenant:
| Recipient approach | Use | Validation |
|---|---|---|
| Context-based recipient fields | Send to a worker/manager/project-manager-style field made available for the report context | [TENANT-SPECIFIC — confirm exact field and relationship] |
| Security Groups | Send to a role/group audience where appropriate | Validate membership and avoid duplicate audiences |
| Direct email recipient input, if exposed | Use only where policy permits | Workday warns email may use a potentially unsecured protocol unless SMTP is configured appropriately |
Important: Do not invent field labels such as “Additional Email Recipients” if they are not visible in the tenant. Validate the current UI in Preview/sandbox.
Step B3: Configure subject and body
Use a concise subject that signals the alert category and urgency. Populate the body with static guidance plus report-context details needed for action.
[Daily TA Alert] Recruiting exception requires review
A recruiting exception currently meets the configured threshold.
Review the record in Workday and take the appropriate action.
Details:
- Requisition: [dynamic field]
- Job Title: [dynamic field]
- Exception Age: [dynamic field]
- Target Date: [dynamic field]
[TENANT-SPECIFIC — available dynamic fields and token behavior must be confirmed in Configure Alert]
Field-visibility security
Workday documents different field-visibility behavior by data-source type:
- Workday data source: field/value visibility is determined by the notification recipient's security.
- Prism data source: visibility is determined by the security of the administrator configuring the alert.
Even when field values are suppressed, the existence of an alert can itself reveal that a record meets a condition. Include this in the privacy/security review.
6. Configure Daily Recurrence
When the run frequency is not Run Now, configure the Schedule tab. Workday supports daily, weekly, monthly, dependent, and customized recurring alert schedules.
| Field | Example | Notes |
|---|---|---|
| Run Frequency | Daily Recurrence | Use the cadence the business actually needs |
| Start Time | 07:00 AM | [TENANT-SPECIFIC] |
| Time Zone | Organization-appropriate zone | [TENANT-SPECIFIC] |
| Start / End Date | Governed activation range | Set ownership for renewal before expiration |
7. Testing & Validation
- Keep the alert suspended or in a non-production tenant while validating.
- Run the underlying report and capture expected recipients/instances.
- Use Run Now for a controlled alert test when appropriate.
- Verify notification content and recipient mapping.
- Run Process Monitor; Workday displays configurable alerts as Alert Job processes.
- Review background-process messages before changing configuration when a test fails.
8. Duplicate Report Parameter Protection
Workday performs an automatic validation check when an alert job is triggered to prevent active alerts with duplicate report parameters from notifying unintended recipients. Duplicate parameters can involve report filters, prompt filter values, or report fields.
If Workday detects duplicate report parameters, the alert job terminates and surfaces messages through the background-process experience. Use the Alerts with Duplicate Report Parameters report to identify impacted alerts.
Resolution
- Run Alerts with Duplicate Report Parameters.
- Open the impacted alert from View Alerts.
- Use Schedule Future Process → Edit, review the report parameters, and save.
- Verify the parameter values are correct.
- Rerun from View Alerts → Schedule Future Process → Run Now.
9. Noise & Duplicate-Audience Controls
| Control | Operating approach |
|---|---|
| Precise filter | Only return conditions that require action |
| Threshold tuning | Baseline volume and adjust with the business owner |
| Targeted recipients | Send to the person/role able to act, not a broad observer list |
| Duplicate-audience review | Check whether context fields, groups, and direct emails overlap |
| Zero-row behavior | If the report returns no instances, there are no report instances to generate notifications from; validate this in testing |
10. Migration, Suspension & Retirement
Changes to the underlying report — especially prompt changes — can affect alert migration and runtime behavior. Validate alerts after migrating report changes.
Migration controls
- Validate the underlying report in the target tenant.
- Review all prompt defaults and Do not prompt at runtime settings.
- Keep the alert Suspended until target-tenant validation is complete.
- Review the future End Date for expired/suspended alerts.
Lifecycle controls
Use View Alerts and Schedule Future Process related actions to suspend/activate, edit, or run alerts. When retiring an alert, suspend it first, document the reason, review dependent report use, and only then remove obsolete scheduling/configuration.
11. Troubleshooting
| Symptom | Likely area | Action |
|---|---|---|
| Alert job terminates immediately | Duplicate report parameters | Run Alerts with Duplicate Report Parameters; edit and re-save the alert |
| No notifications | Zero report instances or recipient setup | Run the report interactively first, then review recipient configuration |
| Wrong recipients | Context recipient field/group/email audience | Suspend and correct recipient mapping before reactivation |
| Prompt-related error | Missing default or Do not prompt at runtime | Correct the report definition and revalidate the alert |
| Blank fields in body | Recipient field security for a Workday data source | Review field-level security and use only appropriate fields |
| Migration failure | Report/prompt structure changed | Review Workday migration messages, repair the alert, and re-migrate |
12. Production Checklist
- Alert-driving report returns only genuine exceptions
- No Filter on Aggregations or Subfilters used
- Every prompt has an appropriate default and Do not prompt at runtime
- Notification Topic validated
- Recipient fields/groups/direct-email audience validated
- Subject/body tested with representative data
- Daily cadence/time zone/start/end date approved
- Run Now test completed in non-production or controlled test context
- Process Monitor reviewed
- Duplicate report-parameter baseline checked
- Alert owner and backup owner documented
- First production run monitored
13. Official Workday References
- Workday Administrator Guide — Concept: Alerts
- Workday Administrator Guide — Configure and View Alerts
- Workday Education — Report Administration
- Workday Education — Reporting Overview
Representative technical work product — Warren Sanders | Version 1.1 | August 2026
Not a prior-client deliverable. Not presented as Workday-certified output.