---
title: "Prove AI calculated fields in Workday — Kiweely"
description: "Check a Deployment Agent calculated-field answer against Evaluate Expression, then prove it with a report and a business process condition rule."
url: https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof
---

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

-   **Checked** against Workday on November 19
-   Applies to **Workday Extend**
-   8 min read
-   Published November 16
-   By Kiweely

An AI suggestion for a calculated field is a draft of logic, not a field. Workday’s Deployment Agent example for a Conditional Management Level field says the agent typically recommends **Evaluate Expression** and lists parameters. You still run **Create Calculated Field**, compare the result to your management-level hierarchy, and only then reference the field from a report, an integration, or a business process condition rule. Calculated fields resolve when they run, because the fields they read can change. A screenshot of a chat is not proof.

You need **Custom Field Management** in the System functional area to create, change, or delete tenant-wide calculated fields. Report-specific fields use **Private Calculated Field Management**. Build and test in Implementation, Preview, or Sandbox. Deployment Agent itself is not a Production assistant.

## What you are allowed to ask the agent to design

Workday’s calculated-fields considerations say you can use calculated fields:

-   As condition rules and metrics for business processes, including controlling condition steps.
-   On integrations, including connectors and Enterprise Interface Builder (EIB).
-   On custom reports.
-   On schedules for recurring processes.

You cannot set them up as **eligibility rules** for business processes. If the agent tells you to hang the new field on eligibility, stop. That is outside the published use.

The same topic says the business object decides where the field can be used and which fields you may reference. Run **Business Object Details** for that object before you accept a suggestion that names a related field you have never seen.

## The published pattern: Evaluate Expression on Worker

**Evaluate Expression** evaluates true/false conditions in order, returns the value for the first true condition, and otherwise returns **Default Value**. It stops testing after the first true condition. Field type controls what **Return Value If Condition is True** can return: text returns text, dates return dates, numbers return numbers. Multi-instance and single-instance types have their own prompt behavior. Create any date, numeric, or text constants first. The conditions have to exist on the business object already.

Workday’s own employment-status example on that page:

| Prompt | Value |
| --- | --- |
| Field Type | Text |
| Business Object | Worker |
| Default Value | Empty String |

| Condition (tested in order) | Return if true |
| --- | --- |
| Worker Active | Active |
| On Leave | On Leave |
| Worker Retired | Retired |
| Worker is Terminated (but not Retired) | Terminated |

Order is the proof problem. A terminated worker who is also “on leave” in your data will return whichever condition is higher in the grid. Put the condition you most need to win first, then test workers who match more than one row.

The Deployment Agent example asks for a different Worker field: Management Level at Manager or above returns the text Manager; everyone else returns Individual Contributor. The published prompt is:

> I am a Workday administrator. I need to create a calculated field on the Worker business object. The logic should be: if a worker’s ‘Management Level’ is ‘Manager’ or any level above that (like Director or VP), return the text ‘Manager’. Otherwise, return ‘Individual Contributor’. Can you provide the step-by-step configuration and the specific calculation type I should use?

The example says you should expect business object Worker, function Evaluate Expression, default Individual Contributor, a Management Level condition with an In Selection List operator, and return value Manager. If your tenant says Lead instead of Manager, ask that as a follow-up. Do not edit the condition until you have looked at the hierarchy.

## Proof sequence

Do this in a non-production tenant, in this order. Workday’s considerations topic says to test calculated fields incrementally in non-production for all users, and to label fields so people can tell what they are.

### 1\. Prefer a delivered field

Run **Calculated Fields Defined** and **Report Fields** before you create anything. Delivered tenant-wide fields are one less field you have to own. **All Calculated Fields** lists what the tenant already has.

### 2\. Decide tenant-wide or report-specific

| Use | When |
| --- | --- |
| Report-specific | One report or one integration, and you want the definition to live on that report. Not allowed on simple reports. |
| Tenant-wide | You will reuse it on a business process, several reports, or an EIB, and you do not expect to keep changing the parameters. |

You can convert either way later. **Maintain Calculated Fields** converts a tenant-wide field to report-specific only when it has a single usage, that usage is a custom report, and you own the report. **Maintain Calculated Fields for Report** converts the other direction when the field does not depend on other report-specific fields.

### 3\. Build the foundational field first

When several calculated fields stack, Workday says to create the foundational fields first: the specific data you want back, then the fields that combine them. Use the most granular report field on related business objects so fewer instances are evaluated. For arithmetic, the considerations topic says to follow standard order of operations (PEMDAS). Numeric results display up to 6 decimal places. Currency decimal places follow ISO currency codes. Configure currency rates before a currency field runs, or the run errors.

### 4\. Rebuild the agent’s grid yourself

In **Create Calculated Field**, select **Evaluate Expression**. Enter the field type, business object, and default. Enter conditions from top to bottom. If your names differ, fix the condition against **Business Object Details** and the management-level hierarchy, not against the chat.

### 5\. Prove it on a report before a business process

Add the field to a custom report whose data source can return Worker (or whichever object you chose). Pick at least:

-   One worker you expect to hit the first true condition.
-   One worker you expect to fall through to the default.
-   One worker who could match two conditions, to prove the first-true stop.
-   One worker whose management level uses your local name (Lead, not Manager).

**Calculated Field Exception Audit** shows severity, location, and solutions for tenant-wide exceptions. **Report Specific Calculated Field Exception Audit** does the same for report-specific fields. **Calculated Field Usage Hierarchy** shows what a later edit will hit. **Recently Updated Calculated Fields** shows when and where a field changed.

### 6\. Only then attach a condition rule

From the business process related actions, or from a step on **Business Process Steps**, create the condition rule. The rule examines conditions in the order you specify until it finds a match. **And** stops at the first false condition. **Or** stops at the first true condition. Put the condition most likely to decide the step at the top.

Use the calculated field as the source external field, and compare it to the text you return (Manager, Individual Contributor, or whatever you proved on the report). Parentheses set precedence when you mix And and Or: (A and B) or C.

On the **initiation** step, do not choose **Initiator** as the source. Workday says that field returns no results before the process has been initiated. If the processing user on a later step cannot see a field whose security is inside the field itself, the step is skipped. Workday does not check domain security of a report field in a condition rule unless that security logic is part of the field.

Run **Rule Tester** from the related actions of a business process event. It shows the execution flow. It is not available for Workday-owned condition rules.

### 7\. Rate the agent, then record the proof

Thumbs up or thumbs down rates the logic the agent gave you. It does not version the field. Keep the report filters and the Rule Tester event in your test notes. **View Calculated Field** is the definition reviewers should open, not the chat.

## Failure modes

| Symptom | Check |
| --- | --- |
| Everyone returns the default | The true condition never matches your real management-level values. Ask the follow-up that names your labels. |
| Managers return Individual Contributor | A broader condition sits above the manager condition, and evaluation stopped. |
| The field is missing on a simple report | Report-specific calculated fields are not supported on simple reports. |
| The condition rule never sees the worker | Initiation is using Initiator, or the processing user fails security that is built into the field, so the step is skipped. |
| You cannot use the field as eligibility | That is a published limitation, not a bug in the agent. |
| Editing the field changes a live hiring process |  **Calculated Field Usage Hierarchy** before you save. The considerations topic calls out hiring processes and financial reports as downstream impact. |
| Discovery board or Report Writer filter does nothing | You cannot filter on fields that return derived instances, such as lookup date rollup. |

Security for who may create fields is separate from who the field describes. The considerations topic says to think about security groups for create and edit access when you add fields.

## Watch Kiweely Vine build a complex calculated field

![The Evaluate Expression calculated field Kiweely Vine built in Workday, with its conditions in order](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof/media/vine-calculated-field-2f60eac728e5.webp)

From the film: one saved Evaluate Expression applies the rules in order.

Kiweely Vine designs and builds a benefits review status calculated field in a Workday Development tenant. It is an Evaluate Expression that combines employment status, worker type, FTE, service dates, a 90-day waiting period and missing information in ordered outcomes, and it is used in a saved report. 50 minutes of recorded build. An independent acceptance passed six checks, with two not run.

[Watch the film (10 min)](https://www.youtube.com/watch?v=aHnNpdrkTdA) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Should the agent create the field for me?

The published example tells you to take the steps into **Create Calculated Field** yourself. With [Configuration Cloud](https://blog.workday.com/en-us/configuration-cloud.html), in opt-in early access for Workday partners since 18 Nov 2026, Deployment Agent can carry out changes once approved. Proof is the field definition plus a report row plus, if a process will use it, a Rule Tester run.

### Can one field serve a report and a condition rule?

Yes, if it is tenant-wide. A report-specific field is for that report definition. Convert it only when the convert rules above are true.

### What if the agent suggests a function other than Evaluate Expression?

Build only if you can point at that function’s admin topic and the business object has the fields it names. The published management-level example is Evaluate Expression. A different function still needs the same report proof before a condition rule.

### Does a correct report prove every security group?

No. The report runs as you. A condition rule later runs as the processing user of the previous step. Proxy or a test user in the real security group is a separate check from the field’s math.

## Sources checked

Frontmatter pages, fetched 2026-11-16.

## Sources checked

-   [Example: Create a Calculated Field with the Deployment Agent](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--create-a-calculated-field-with-the-deploy.html)
-   [Evaluate Expression](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370796323223.html)
-   [Setup Considerations: Calculated Fields](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/ova1547251060954.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)

-   [### 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)
-   [### CRAFT prompts for the Workday Deployment Agent Workday’s Deployment Agent sample-prompts topic, updated 2026-11-06, says accurate answers come from five CRAFT elements. This guide restates that method, shows which elements you can omit, and rewrites the published samples so an administrator can see what each word is doing.](https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns)
-   [### A Workday admin’s first week with Deployment Agent Deployment Agent is a non-production assistant for implementers and administrators. This week plan follows Workday’s setup: confirm UMSA, set up Agent System of Record per tenant, secure Deployment Agent Users, register skills, and prove one tenant-grounded prompt.](https://kiweely.com/guides/workday-admin-first-week-deployment-agent)

### More guides on Reports and calculated fields

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

-   [Life-Event 834 Feeds for Birth, Divorce, and COBRA](https://kiweely.com/guides/life-event-834-feeds-for-birth-divorce-and-cobra)
-   [Expense Report Create-and-Submit Screens Outside Workday Menus](https://kiweely.com/guides/expense-report-create-submit-outside-workday-menus)
-   [Workday calculated field not showing in a report: why it is missing from the field picker](https://kiweely.com/guides/workday-calculated-field-not-showing-in-report)
-   [How to debug a Workday calculated field that returns the wrong value](https://kiweely.com/guides/workday-calculated-field-returns-wrong-value)
-   [Preventing Accidental Indirect-Report Visibility in Workday Intersection Security Groups](https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility)
-   [How to Sum or Count Multi-Instance Rows in Workday Using Aggregate Related Instances (ARI)](https://kiweely.com/guides/workday-aggregate-related-instances-ari-sum-count)
-   [Blank vs. Empty in Workday Report Filters and Condition Rules: Why Your Filter Misses Rows](https://kiweely.com/guides/workday-blank-vs-empty-report-filter-prompts)
-   [How to Fix CellLimitExceededException: Exceeded Cell Limit in Workday Custom Reports and EIBs](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception)

### From the blog on Reports and calculated fields

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

-   [Kiweely builds a prompted Workday report, then answers from the tenant](https://kiweely.com/blog/workday-report-built-and-tenant-answer)
-   [How to Review an AI-Built Calculated Field Chain Like a Senior HCM Lead](https://kiweely.com/blog/review-ai-built-calculated-field-like-senior-hcm)
-   [Approving Workday Expense Reports and Purchase Requisitions in Teams and Slack](https://kiweely.com/blog/workday-expense-report-and-requisition-approvals-in-teams-slack)

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