A calculated field that “fails” inside a condition rule usually did one of three documented things: it returned its Default Value because no Evaluate Expression row was true, it read a field that is null after termination, or the processing user could not see a secured field so Workday skipped the step. The report that shows the field for an admin is not proof that the Term business process will branch.
Workday allows calculated fields as condition rules and metrics for business processes, including controlling condition steps. It does not allow them as eligibility rules (Setup Considerations: Calculated Fields). You need Custom Field Management for tenant-wide fields.
Failure modes that look like a bad condition
| Symptom | Documented cause | What to check |
|---|---|---|
| SymptomRule never matches; field shows blank or default on a report | Documented causeEvaluate Expression returns Default Value when every condition is false; it stops at the first true condition | What to checkCondition order, tenant labels (Lead vs Manager), constants created first |
| SymptomWorks on active workers; fails on Term / after Term | Documented causeTermination clears position-tied fields to null (cost center, supervisory org, job profile, job family/group, time in position, time type, and similar) | What to checkMaintain Attributes for Terminated Workers |
| SymptomFires for admins, skipped for managers | Documented causeProcessing user lacks access when security is inside the report field | What to checkCreate Business Process Condition Rules |
| SymptomField missing from the condition prompt | Documented causeWrong business object, or report-specific field used where a tenant-wide field is required | What to checkBusiness Object Details; convert or recreate as tenant-wide |
| SymptomSomeone moved the logic to eligibility | Documented causeCalculated fields are not eligibility rules | What to checkPut the logic back on a condition step |
Workday resolves calculated fields when they run, because the fields they read can change. A screenshot from yesterday’s report is not the value at Term submit time.
Term and position fields
When a worker terminates, employment status becomes inactive and Workday clears fields that belong to the position, leaving them empty. Person-describing fields (date of birth, gender, home address, email) remain. Any condition or calculated field that still reads cleared attributes on or after Term sees null.
Workday’s published pattern for keeping a value through termination (shown in the Peakon attribute topic, reusable for the same null problem):
- Increment or Decrement Date on the termination date by -1, with Return Blank Date on Error = Yes.
- Lookup Value As of Date on the source field (for example Employee Type), effective on that day-before date.
- Evaluate Expression that, when the worker is terminated based on report date, returns the lookup result instead of the live (now blank) field.
Point the condition rule at the Evaluate Expression field, not at the raw cleared attribute.
Prove it before you change the BP again
- Confirm the field is tenant-wide if the process must use it. Report-specific fields stay on that report.
- Add it to a custom report. Include an active worker, a worker who should hit the first true Evaluate Expression row, a worker who should fall through to Default Value, and a terminated worker if Term is in scope.
- Run Calculated Field Exception Audit (or the report-specific audit). Fix severity and location before editing the BP.
- Attach the field to the condition rule. Avoid Initiator on the initiation step; Workday says it returns no results before the process starts.
- Run Rule Tester from the event related actions. Read which And/Or row stopped.
- Retest as the processing user if the step still skips after the field looks correct on a report.
Build foundational calculated fields first when several stack. Test incrementally in a non-production tenant for the roles who actually process the steps.
Kiweely Vine can help you inspect a tenant calculated-field or condition-rule question with consent. Rule Tester and the exception audit remain the logs of record.
Frequently asked questions
Can I use a calculated field as a business process eligibility rule?
No. Workday’s calculated-fields considerations say you cannot set up calculated fields as eligibility rules for business processes. Use them on condition steps and metrics instead.
Why does my Term condition see blank cost center or job profile?
On termination, Workday clears many position-tied fields (cost center, supervisory organization, job profile, job family, time type, and similar) to null. Person fields such as date of birth stay. Build Lookup Value As of Date / Evaluate Expression patterns that read values as of the day before termination when you still need those attributes.
Where do I see calculated field exceptions?
Run Calculated Field Exception Audit for tenant-wide fields, or Report Specific Calculated Field Exception Audit for report-specific fields. View Calculated Field shows the definition in use.
Frequently asked questions
Can I use a calculated field as a business process eligibility rule?
No. Workday’s calculated-fields considerations say you cannot set up calculated fields as eligibility rules for business processes. Use them on condition steps and metrics instead.
Why does my Term condition see blank cost center or job profile?
On termination, Workday clears many position-tied fields (cost center, supervisory organization, job profile, job family, time type, and similar) to null. Person fields such as date of birth stay. Build Lookup Value As of Date / Evaluate Expression patterns that read values as of the day before termination when you still need those attributes.
Where do I see calculated field exceptions?
Run Calculated Field Exception Audit for tenant-wide fields, or Report Specific Calculated Field Exception Audit for report-specific fields. View Calculated Field shows the definition in use.