---
title: "Current vs Proposed fields in Workday condition rules"
description: "Use Proposed for values entered on the initiating page and Current for the worker’s existing values when a Change Job condition should fire only on a real…"
url: https://kiweely.com/guides/workday-condition-rules-current-vs-proposed
---

# Current vs Proposed fields in Workday condition rules

Workday Change Job condition rules compare Proposed fields (what the initiator just entered) to Current fields (what already exists). A rule that reads only Current will miss the change. Workday evaluates those rules from initiating-page data before later subprocesses run.

-   **Checked** against Workday on November 17
-   Applies to **Workday Change Job and staffing condition rules**
-   3 min read
-   Published November 17
-   By Kiweely

In Change Job, **Proposed** fields are what the initiator entered on the initiating page. **Current** fields are what already exists on the worker. A condition that should fire only when something changes compares Proposed to Current. A rule that reads only Current (or only Proposed against a hard-coded value that matches both) will look “broken” when the step never opens.

## The published Change Job pattern

[Concept: Condition Rules for Job Changes](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/change-job/new-change-job/dan1370797455862.html) shows a subprocess for **Change Organization Assignments** that should run only when location changes:

| And/Or | Source External Field | Relational Operator | Comparison Type | Comparison Value |
| --- | --- | --- | --- | --- |
| And | Location - Proposed | NOT exact match with the selection list | Value from another field | Location - Current |

Workday evaluates Change Job condition rules from the data submitted on the initiating page. Evaluation order for what runs is:

1.  Condition rules
2.  Business process definition
3.  **Maintain Change Job Templates** configuration
4.  Change job consolidated template

If the initiator changes location on the initiating page, that rule can open organization assignment even when the template did not surface that section as a free-form edit. Approving later does not invent a Proposed value that was never submitted.

## Current vs Proposed: pick by intent

| Intent | Field pattern | Why |
| --- | --- | --- |
| Fire only when a value changes | Proposed vs Current (not exact match / not equal) | Compares the new entry to what already exists. |
| Fire when the new value is a specific choice | Proposed equal to a fixed value or list | Uses what was entered this event. |
| Fire based on what the worker already has | Current equal to a value | Ignores the new entry; use only when that is deliberate. |
| Drive Change Job field defaults from what the user typed | Proposed (for example Scheduled Hours - Proposed, Job Profile - Proposed) |  [Staffing field defaults](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/change-job/new-change-job/steps--set-up-defaults-for-change-job-fields.html) examples use Proposed in the condition grid. |

Common false negatives:

-   You meant “location changed” but compared **Location - Current** to a static list that still matches.
-   You compared Proposed to Proposed (or Current to Current).
-   The initiating page never changed the field, so Proposed equals Current and a NOT-match rule correctly stays false.
-   You tested with an event started before the rule edit. Start a new event after the change.

## How to build and prove it

1.  From the Change Job definition (or step related actions), create the condition rule with **Manage: Business Process Definitions**.
2.  In the grid, select the **\- Proposed** report field as the source when the decision depends on this event’s entry.
3.  For a change detector, set comparison type to another field and choose the matching **\- Current** field.
4.  Put the deciding condition near the top of And/Or lists; Workday short-circuits And on the first false row and Or on the first true row ([Create Business Process Condition Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/customize-business-processes/dan1370796347209.html)).
5.  Submit a Change Job where Proposed differs from Current, and one where it does not.
6.  Run **Rule Tester** from the event related actions. Confirm which row passed or failed.

For defaults that should follow Proposed hours or job profile, create the defaults condition rule first, then attach it on **Maintain Staffing Field Defaults**. Workday processes those rules in grid order and stops after the first match for a field.

## Frequently asked questions

### What is the difference between Current and Proposed in a Change Job rule?

Current is the value already on the worker. Proposed is the value submitted on the initiating page for this event. A location-change rule compares Location - Proposed to Location - Current.

### When does Workday evaluate Change Job condition rules?

For Change Job subprocess routing, Workday evaluates the condition rules from the data submitted on the initiating page, before later subprocess steps depend on that decision.

### Can I use Proposed fields in staffing field defaults?

Yes. Workday’s Change Job defaults examples use fields such as Job Profile - Proposed and Scheduled Hours - Proposed in condition rules that drive defaults.

## Frequently asked questions

### What is the difference between Current and Proposed in a Change Job rule?

Current is the value already on the worker. Proposed is the value submitted on the initiating page for this event. A location-change rule compares Location - Proposed to Location - Current.

### When does Workday evaluate Change Job condition rules?

For Change Job subprocess routing, Workday evaluates the condition rules from the data submitted on the initiating page, before later subprocess steps depend on that decision.

### Can I use Proposed fields in staffing field defaults?

Yes. Workday’s Change Job defaults examples use fields such as Job Profile - Proposed and Scheduled Hours - Proposed in condition rules that drive defaults.

## Sources checked

-   [Concept: Condition Rules for Job Changes](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/change-job/new-change-job/dan1370797455862.html)
-   [Steps: Set Up Defaults for Change Job Fields](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/change-job/new-change-job/steps--set-up-defaults-for-change-job-fields.html)
-   [Create Business Process Condition Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/customize-business-processes/dan1370796347209.html)

## Related guides

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

-   [### 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.](https://kiweely.com/guides/workday-test-rule-vs-processing-user-security)
-   [### Explain a Workday business process in plain language, then configure the rule BP Optimize Agent recommends process improvements. Deployment Agent can explain a concept in layperson’s terms. The configuration is still a condition rule on a step: ordered conditions, And and Or short-circuit, and a Rule Tester run on a real event.](https://kiweely.com/guides/ai-workday-business-process-design-plain-language)

### 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)
-   [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)
-   [Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One](https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security)

### 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.
