After updating our supplier onboarding business process last week to include additional approval steps, we’ve discovered that email notifications are no longer reaching the procurement managers who need to review new supplier applications.
The business process completes successfully - suppliers move through the workflow stages and eventually get approved. However, the stakeholders at the “Procurement Manager Review” step aren’t getting notified, which means applications sit idle until someone manually checks the inbox.
We added two new approval steps between the initial submission and final approval. The notification configuration shows email is enabled for the step, and we’ve verified the email addresses are correct in the worker profiles. Interestingly, the final approval notification still works fine - it’s only the middle review step that’s affected.
<notification step="Procurement_Manager_Review">
<recipients type="static">
<worker>John_Smith</worker>
</recipients>
</notification>
We’re using static recipients pointing to specific workers. Could the workflow routing be bypassing the notification somehow? Has anyone dealt with notifications failing after modifying a supplier onboarding process?
Good point - I see we have version 2.0 active now, but there are still some applications in progress on version 1.8. The notification issue is definitely happening on the 2.0 applications.
The step name is the same, but we did change its position in the sequence. It was step 2, now it’s step 4 after adding the two new approval stages. Would that affect how static recipients resolve?
Another thing - check your business process activation status. When you modify a BP and save it, sometimes it creates a new version but doesn’t automatically activate it for all in-flight transactions. You might have some supplier applications running on the old BP version (which works) and new ones on the updated version (which has the notification issue). Go to Business Process > View Business Process and check which version is marked as active.
I’ve identified the issue based on your configuration snippet and symptoms. The problem involves all three focus areas:
1. Business Process Notification Setup:
Your notification is configured with static recipients, but the step context has changed. When you added new approval steps and shifted the Procurement Manager Review to position 4, the notification configuration didn’t update its step binding properly.
Fix the notification setup:
- Go to Business Process: Supplier Onboarding
- Navigate to the Procurement_Manager_Review step
- Click Configure Notifications
- Remove the existing static notification configuration
- Add a new notification with proper step binding
2. Dynamic vs Static Recipients - The Core Issue:
Static recipients in your XML configuration reference a specific worker (John_Smith), but this approach has several problems:
- No fallback if the worker is unavailable
- Doesn’t scale when you need multiple reviewers
- Step position changes can break the reference
Replace static recipients with dynamic assignment:
<notification step="Procurement_Manager_Review">
<recipients type="dynamic">
<role>Procurement_Manager_Role</role>
<org_type>Supervisory</org_type>
<org_context>Supplier_Management</org_context>
</recipients>
<delivery>Immediate</delivery>
</notification>
This configuration:
- Dynamically identifies procurement managers based on their role assignment
- Uses supervisory org context to find the right organizational reviewers
- Automatically handles role changes and multiple assignees
- Sets immediate delivery to prevent digest bundling
3. Supplier Onboarding Workflow - Step Sequence:
When you inserted two new approval steps, the workflow step sequence changed but the notification triggers didn’t update accordingly. Here’s what you need to verify:
- Open Business Process Designer for Supplier Onboarding
- View the complete step sequence: Initial Submit > [New Step 1] > [New Step 2] > Procurement Manager Review > Final Approval
- For the Procurement Manager Review step, verify these settings:
- Step Type: Approval (not review or notification-only)
- Notification Timing: On step activation (not on completion)
- Step Condition: No auto-skip conditions are configured
- Notification Frequency: Immediate (not daily digest)
Critical Configuration Check:
Go to Configure Business Process > Procurement Manager Review step > Advanced Options:
- Ensure “Skip notification if step completes within X minutes” is NOT checked
- Verify “Send notification to” is set to “All step assignees”
- Confirm “Notification template” is properly selected (not blank)
Activation and Testing:
- Save your business process changes
- Activate version 2.1 (create new version to avoid affecting in-flight applications)
- Set activation date to tomorrow to ensure clean cutover
- Test with a new supplier application submission
- Monitor the notification queue: Business Process > View Notifications to confirm delivery
The combination of static recipient references and step position changes is causing the notification engine to fail silently. Switching to dynamic recipients with proper role-based assignment will resolve this and make your workflow more maintainable going forward.
Static recipients can be problematic when you modify business process steps. Did you check if the worker reference is still valid after your changes? If you renamed the step or changed its position in the workflow, the static reference might be pointing to a step that no longer exists in that context. Try switching to dynamic recipients based on supervisory org or role assignment instead.
Yes, step position matters for notification triggers. When you insert new steps, Workday recalculates the step sequence IDs internally. If your notification configuration references a specific step position rather than step name, it could be firing at the wrong point. Go to your business process definition and check the notification setup. Click on the Procurement Manager Review step and verify the notification is attached to that specific step definition, not just positioned at a certain sequence number. Also check if there’s a condition on the notification that might be evaluating to false now that the workflow structure changed.
I’d recommend checking the notification frequency settings too. If you have multiple approval steps close together and notifications are set to digest mode rather than immediate, they might be getting bundled in a way that causes delays or suppression. Also verify that the step isn’t configured as an “auto-approve” condition which would skip the notification entirely.