A business process design that stakeholders can read is a sequence of steps plus the rule that lets each step run. Workday configures that rule as one or more conditions, examined in the order you specify, until one matches. Plain language is how you agree the rule. The condition grid is how Workday runs it. An AI explanation is not either of those until you attach it to a step and run Rule Tester.
Two Workday-built agents sit next to this work, and they are not the same tool. BP Optimize Agent analyzes current processes, finds improvements, and gives recommendations with step-by-step guidance. Deployment Agent answers implementation questions and can inspect configuration in Implementation, Preview, Sandbox, and Customer Central connected to non-production. Neither one saves the business process for you.
You need Manage: Business Process Definitions in the System functional area to create condition rules.
Write the process in four sentences
Use this shape in the design note before you open the definition. It maps onto the condition-rule topic without adding steps Workday does not have.
- Who starts it. The initiation step. Do not describe the starter as “Initiator” if you mean a worker attribute. On the initiation step, Workday recommends a source other than Initiator, because that field returns no results before the process starts.
- What must be true for the next step. One condition, or several joined by And or Or.
- Who acts, and what happens if they cannot see the data. If the person who processed the previous step cannot access fields or values used in the next step, and that security is part of the field, Workday skips the step.
- What you will compare. A value you type, or another field. For a boolean, “equal to true” means the comparison check box is selected. “Not equal to true” means it is cleared.
Read those four sentences to the process owner. Then configure only what survived that reading.
Ask for plain language on purpose
Deployment Agent’s CRAFT method says to set Tone when the audience is not a configurator, and to set Format when you want a list. The published learning sample is:
As a Workday administrator, give me a layman’s terms explanation of the ‘Top of Stack’ concept. Provide the answer in bullet points.
Reuse that Tone and Format for a process concept, and keep the Action to one concept:
As a Workday administrator, give me a layman’s terms explanation of how a business process condition rule uses And and Or. Provide the answer in bullet points.
That prompt does not say “in my tenant,” so you get the concept, not your hiring process. When you want your definition inspected, add the tenant phrase from the sample-prompts topic:
In my tenant, how does this condition rule work: [rule name]
BP Optimize Agent is the product Workday describes for “where is this process slow or ineffective,” with recommendations. Use Deployment Agent for “what does this rule do” and “how do I configure the condition.” Do not expect either chat to replace Edit Condition Rule.
Configure the rule the way the plain language actually evaluates
From the business process related actions, choose Business Process, or from a step on Business Process Steps choose Create Condition Rule.
| Plain sentence | What you enter | How Workday evaluates it |
|---|---|---|
| Plain sentence“Both of these must be true.” | What you enterAnd between conditions | How Workday evaluates itStops at the first false condition. Later rows are not checked. |
| Plain sentence“Either one is enough.” | What you enterOr between conditions | How Workday evaluates itStops at the first true condition. |
| Plain sentence“A and B, or just C.” | What you enterParentheses: (A and B) or C | How Workday evaluates itParentheses set precedence. Without them, the mix is not the sentence you read aloud. |
| Plain sentence“Check the usual case first.” | What you enterPut that condition at the top | How Workday evaluates itWorkday says this is how you keep the rule from doing extra work. It also changes which row wins when more than one could match. |
| Plain sentence“Compare to this text or number.” | What you enterComparison value | How Workday evaluates itEqual to: the field matches. For true/false, selected means true and cleared means not equal to true. |
| Plain sentence“Use this calculated field.” | What you enterSource external field | How Workday evaluates itAllowed for condition rules and metrics. Not allowed as an eligibility rule. |
Evaluate Expression is the calculated-field function that matches most plain-language “if this, say Manager, otherwise say Individual Contributor” designs. It tests conditions from the top and stops at the first true row, otherwise it returns Default Value. If you use that field inside a condition rule, you now have two orders: the order inside the field, and the order inside the rule. Prove the field on a report first, then the rule on an event.
The source prompt only lists rules whose fields are relevant to that business process. If the agent’s field is missing from the prompt, it is the wrong business object or it is not a valid source for this process. Check Business Object Details rather than typing a field name that the prompt does not offer.
Alerts and delegations are other rules
The condition-rule topic separates these from step conditions:
| Need | Task | Caution |
|---|---|---|
| NeedAlert on a process or task | TaskCreate Alert Rule | CautionEdits affect processes that have already started. |
| NeedSomeone else may start a process or complete My Tasks | TaskCreate Delegation Rule | CautionYou cannot edit or delete a delegation rule that is in use. |
| NeedWhich delegation rule a person should pick | TaskManage Delegation Settings | CautionIdentifies the rule. It does not create the condition. |
You cannot delete a rule that an alert notification references, a rule that only ran once, or a rule with an expired schedule. Object Transporter can move condition rules between tenants. The topic’s example is to test alert rules in Sandbox, then migrate them to Production. A rule that “works in chat” and was never saved cannot be transported.
Prove the sentence against an event
Rule Tester, from the related actions of a business process event, shows the execution flow. It is not available for Workday-owned condition rules. Run it on:
- An event that should enter the step.
- An event that should skip the step because And failed on the first false row.
- An event that should enter because Or succeeded on an early row, even if a later row would have failed.
- An initiation where you almost used Initiator.
- An event processed by someone who does not have the field, if the field carries its own security. Expect a skip, not an error in the initiator’s inbox.
If the tester disagrees with the four sentences, change the grid or change the sentences. Do not leave both in the design note.
Calculated-field side effects belong in the same proof. Calculated Field Usage Hierarchy shows reports and other uses. Hiring processes and financial reports are the downstream examples Workday names. Recently Updated Calculated Fields shows whether someone changed the field after you tested the rule.
Failure modes
| What stakeholders see | What the condition-rule topic points at |
|---|---|
| What stakeholders see“The extra approval never happens.” | What the condition-rule topic points atAnd stopped on an earlier false row, or the true row is below a different match. Or the initiation source is Initiator and returned nothing. |
| What stakeholders see“People skip a step and nobody approved.” | What the condition-rule topic points atThe processing user could not access the next step’s fields, so the step was skipped. |
| What stakeholders see“The AI said this is an eligibility rule.” | What the condition-rule topic points atCalculated fields cannot be eligibility rules. |
| What stakeholders see“We changed the alert text and old processes changed too.” | What the condition-rule topic points atAlert-rule edits affect processes already started. |
| What stakeholders see“We cannot delete the old rule.” | What the condition-rule topic points atIt is referenced by an alert, it ran once, its schedule expired, or it is a delegation rule in use. |
| What stakeholders see“Sandbox matches Production language but not Production rows.” | What the condition-rule topic points atThe rule was edited in one tenant and not moved with Object Transporter. |
Frequently asked questions
Is a written process description a Workday object?
No. The objects are the business process definition, its steps, and condition rules (plus alert rules and delegation rules when you need those). The description is how you check the grid.
Should BP Optimize Agent be on before we design?
Only if that agent is in your SKUs and you have registered it. Its published job is to analyze processes you already have and recommend improvements. A new condition rule is still Create Condition Rule.
Can I ask for layperson’s terms and tenant inspection in one prompt?
Yes. CRAFT allows Tone and “in my tenant” together. If the answer mixes a definition with your step names, split it: one learning prompt, then one inspection prompt that names the rule.
Do we activate security for a condition rule?
The condition-rule topic does not add a separate activation for the rule itself. Domain changes you make so the processing user can see a field still go through Activate Pending Security Policy Changes. Until that activation, a test user will not match Production behavior.
Sources checked
Frontmatter pages, fetched 2026-11-16.