---
title: "Test Rule says Yes but the Workday BP step still skips…"
description: "Rule Tester can show Yes while the next business process step is skipped when the processing user cannot see a secured report field in the condition rule."
url: https://kiweely.com/guides/workday-test-rule-vs-processing-user-security
---

# Test Rule says Yes but the Workday BP step still skips: processing-user security

Workday evaluates field security inside a condition rule for the person who completed the previous step. Testers with broad access see Yes on Rule Tester; the real processing user can still cause the step to skip. Fix security for that user, then retest as them.

-   **Checked** against Workday on November 17
-   Applies to **Workday business processes and condition rules**
-   4 min read
-   Published November 17
-   By Kiweely

Rule Tester can show **Yes** and the next business process step can still be skipped. Workday evaluates security on a report field used in a condition rule for the **processing user**—the person who completed the previous step. If that person cannot see the field or its values, Workday skips the step. Broad admin testers often miss this because their security never fails the check.

You need **Manage: Business Process Definitions** to maintain the rule. Rule Tester is available from the related actions of a business process event that uses a condition rule, and it needs **Business Process Administration**. It is not available for Workday-owned condition rules.

## What Workday actually checks

From [Create Business Process Condition Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/customize-business-processes/dan1370796347209.html):

| Behavior | What Workday documents |
| --- | --- |
| Domain security on a plain report field | Not checked just because the field sits in a condition rule. |
| Security logic inside the report field | Evaluated for the processing user before results return. |
| Processing user fails that check | The next step is skipped. |
| Rule Tester | Shows the full execution flow for the event; not available for Workday-owned rules. |

Entry conditions skip a step when the condition is false. That is normal BP design. The trap here is a different skip: the rule looks true under a privileged account, then the real processor never sees the step.

## Reproduce the mismatch

1.  Start a non-production event that should hit the step.
2.  Open the event related actions → **Business Process** → **Test Rule** (or **Rule Tester**).
3.  Confirm the condition rows you care about evaluate as expected for that event.
4.  Look at who completed the previous step. That account is the processing user for the next evaluation.
5.  Retest the same flow while acting as that processing user (proxy where your tenant policy allows it), not as a security admin.

If Rule Tester under the admin says Yes, and the step vanishes only when the manager (or other prior actor) advances the event, treat it as a security mismatch until proven otherwise.

## Fix the right layer

| You see | Do this |
| --- | --- |
| Admin Yes, manager skips the step | Grant the processing user’s security groups access to the secured field or values the rule reads. Activate pending security policy changes before you retest. |
| Rule false for everyone | Fix the condition (And/Or order, comparison, wrong field). Security is not the problem. |
| Rule on initiation with source **Initiator** | Workday says Initiator returns no results before the process starts. Change the source; do not chase processing-user security. |
| Workday-owned rule | Rule Tester will not run. You cannot edit that delivered rule; adjust your custom entry conditions or surrounding steps instead. |
| Step skipped on web service / EIB auto-complete |  [Step Conditions](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-framework-concepts/dan1370796347609.html) notes conditions are not evaluated when a BP runs from a web service or EIB and is set to automatically complete. That is a different path from a UI skip. |

Prefer fields that do not embed security the processing user lacks. If the field must stay secured, put the people who actually complete the prior step into groups that can see it. Do not “fix” the BP only with Integration System Users or Super Users and call that proof.

## How to prove the fix

1.  Activate pending security changes.
2.  Run a fresh event (do not reuse an event that started before the security change if you need a clean compare).
3.  Complete the prior step as the real role (manager, HR partner, or whatever your definition uses).
4.  Confirm the next step appears for that role.
5.  Run Rule Tester again on that event and keep the event ID in your test notes.

Kiweely Vine can help you walk a tenant question about which domain or group a field uses, with your consent, in a non-production tenant. It does not replace Rule Tester or proxy proof as the person who processes the step.

## Frequently asked questions

### Why does Rule Tester say Yes when the step never appears?

Rule Tester shows how the rule evaluated for that event. If a report field carries its own security, Workday still checks the processing user before returning results. When that user cannot see the field or values, Workday skips the step even if a broad tester would see Yes.

### Who is the processing user?

Workday defines the processing user as the person who processed the previous step. That is who must pass security on a report field that embeds security logic inside the field.

### Does Workday always check domain security on report fields in condition rules?

No. Workday does not check domain security of a report field in a condition rule unless the security logic is part of the field itself. When it is, the processing user must pass that check or the next step is skipped.

## Frequently asked questions

### Why does Rule Tester say Yes when the step never appears?

Rule Tester shows how the rule evaluated for that event. If a report field carries its own security, Workday still checks the processing user before returning results. When that user cannot see the field or values, Workday skips the step even if a broad tester would see Yes.

### Who is the processing user?

Workday defines the processing user as the person who processed the previous step. That is who must pass security on a report field that embeds security logic inside the field.

### Does Workday always check domain security on report fields in condition rules?

No. Workday does not check domain security of a report field in a condition rule unless the security logic is part of the field itself. When it is, the processing user must pass that check or the next step is skipped.

## Sources checked

-   [Create Business Process Condition Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/customize-business-processes/dan1370796347209.html)
-   [Concept: Step Conditions](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-framework-concepts/dan1370796347609.html)
-   [Business Process Framework (Workday Education)](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/business-process-framework.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Start a proxy test after an AI-suggested Workday change Workday’s Adaptive Planning proxy procedure uses a proxy policy, Start Proxy, and Stop Proxy in non-production, and records the proxy user. After an AI-suggested security or rule change, add the tester that matches the object you edited.](https://kiweely.com/guides/workday-start-proxy-testing-after-ai-changes)
-   [### Prove an AI-suggested Workday calculated field before it drives a condition rule Deployment Agent’s documented example suggests Evaluate Expression logic for a Worker field and you build it in Create Calculated Field; Configuration Cloud (partner early access) can make approved changes. This guide shows how to prove the field before a rule or integration uses it.](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Review security group changes an AI assistant suggested in Workday](https://kiweely.com/guides/review-ai-workday-security-group-changes)
-   [Explain a Workday business process in plain language, then configure the rule](https://kiweely.com/guides/ai-workday-business-process-design-plain-language)
-   [Turn a requirements note into a Workday business process](https://kiweely.com/guides/ai-brd-to-workday-business-process-design)
-   [Benefits Life-Event Intake That Starts the Right Workday Process](https://kiweely.com/guides/benefits-life-event-intake-workday-business-process)
-   [How do I document Workday configuration and business processes from a live tenant?](https://kiweely.com/guides/document-workday-configuration-and-business-processes)
-   [How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)
-   [Aligning Workday Session Timeouts with External OAuth Access Token Lifetimes](https://kiweely.com/guides/workday-anonymous-vs-authenticated-session-timeout-oauth)
-   [How Workday Terminations and Job Transfers Affect Active OAuth Grants](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)

### From the blog on Business processes and security

[All posts](https://kiweely.com/blog)

-   [Designing Privacy-Safe Mobile Push Notifications for Workday Approvals and Pay Updates](https://kiweely.com/blog/privacy-safe-push-notifications-for-workday-tasks-on-phones)
-   [Why Building Internal Workday Apps in Retool or Lovable Stalls on OAuth and Security](https://kiweely.com/blog/retool-superblocks-lovable-on-workday-oauth-trap)
-   [How Submitting Workday Time Off from Claude or ChatGPT Works Safely End to End](https://kiweely.com/blog/submitting-workday-time-off-from-claude-chatgpt-with-approval)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
