---
title: "Business process change, Claude: the full transcript"
description: "Every turn of Claude on the business process change task in Kiweely’s Workday tenant test, word for word with its times."
url: https://kiweely.com/tenant-test/transcripts/t4-cl
---

# T4 · CL · Claude: Anthropic Claude Opus 5.5 (effort high) via Claude Code CLI

## Turn 1: prompt (sent 2026-11-20T04:48:50.243Z)

In our Workday tenant, on the Change Job business process for our top-level company organization, add a To Do step for the HR Partner called “Confirm workspace move TT-CLA” that comes after the manager’s approval. The business process must still work for Change Job events started after the change. Please give me what I need to make the change.

## Turn 1: answer (2026-11-20T04:49:22.000Z, 31.8 s)

I can’t reach your Workday tenant, so here are the steps to do it yourself. Try it in a sandbox or implementation tenant first if you have one.

## 1\. Create the To Do

1.  Search for and run the task **Create To Do**.
2.  **To Do Name:** `Confirm workspace move TT-CLA`
3.  **Instructions:** Add something like “Confirm the worker’s workspace or desk move is arranged for the new job/location, then mark this To Do done.”
4.  **Related Task:** Leave this blank unless you want a task link.
5.  Click **OK**.

The To Do has to exist before a business process step can use it.

## 2\. Open the Change Job definition

1.  Search for and run **Business Process Definition**. If you only have the organization, run **View Business Process Definition** instead.
2.  **Business Process Type:** Change Job
3.  **Organization:** your top-level organization

**Check the organization:** Change Job is defined on the **supervisory organization** hierarchy, not the company hierarchy. The default definition sits on the top-level supervisory org. If you pick a company org, you may not find a definition, or you may edit the wrong one. Also, if a lower org has its own Change Job definition, that definition is used for workers in that org, and your change won’t reach them. Check for these with **Business Process Definitions for Organization** or the **Business Process Definitions** report.

## 3\. Add the step

1.  On the definition, choose **Business Process → Edit Definition** (or **Maintain Steps**).
2.  Find the manager’s approval step and note its **Order** letter, for example **b**, with Type **Approval** and Group **Manager**.
3.  Add a row with these values:

| Field | Value |
| --- | --- |
|  **Order** | A letter after the manager’s step, e.g. **ba** if the next step is **c**. Workday sorts these alphabetically, so **ba** fits between **b** and **c**. Use **c** if nothing follows. |
|  **If** | Blank, so it always runs. Add an entry condition if only some job changes involve a move, e.g. location changed. |
|  **Type** |  **To Do** |
|  **Specify** | `Confirm workspace move TT-CLA` |
|  **Optional** | Leave unchecked if the step is required |
|  **Group** |  **HR Partner** (a role-based security group) |
|  **All** | Leave unchecked so any one HR Partner can complete it |

If the manager approval step has parallel steps with the same letter, give the new step a letter after all of them so it doesn’t run alongside them.

1.  Click **OK** and **Done**.

## 4\. Make sure new events use it

-   **Effective date:** When you save, Workday creates a new version of the definition with an effective date and time. Set it to now or earlier. Change Job events started on or after that moment use the new version.
-   **Events already in progress:** They keep running on the version that was in effect when they started. They won’t get the new step, and they won’t break.
-   **Unassigned HR Partners:** Check that the role is assigned on the supervisory orgs, either directly or inherited from a parent org (**Organization Assignments / Assign Roles**). If nobody holds HR Partner for a worker’s org, the step can’t route properly.
-   **Activate pending security changes:** Usually you don’t need to touch the security policy for a role on an approval or To Do step. If you did change the Change Job business process security policy, run **Activate Pending Security Policy Changes**.
-   **Other definitions:** If lower orgs have their own Change Job definitions (see step 2), add the same step to each one, or delete them so they inherit from the top-level org.

## 5\. Test it

1.  Start a new Change Job for a test worker.
2.  Approve it as the manager. You can use **Start Proxy** or log in as the manager.
3.  Check that the To Do **Confirm workspace move TT-CLA** shows up in an HR Partner’s inbox, and that the event moves on after they mark it done.
4.  Run **View Business Process Definition** with the date as of now and check that the new step shows in the right order.
5.  If it all works in the sandbox, repeat the change in production, or move it with an Object Transporter or Solutions migration.

## Turn 2: follow-up (sent 2026-11-20T07:44:22.497Z)

Step 1 says to search for and run the task “Create To Do”. Searching Workday for “Create To Do” finds no task with that name. Tasks and Reports (4) shows only: “Create Total Rewards Section (Do Not Use)” / “Create Total Rewards Template (Do Not Use)”, “Create Goal” and the report “Processes Awaiting Me”. No task named Create To Do is offered.

## Turn 2: answer (2026-11-20T07:44:52.578Z, 30.1 s)

I got the task name wrong in step 1. Workday has no task called **Create To Do**. You create To Dos with **Maintain To Dos**, which Workday’s documentation describes as the task to “create, edit or delete a To Do” ([Concept: To Do Step](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-step-types/dan1370797857694.html)).

## Corrected step 1: Create the To Do

1.  Search for **Maintain To Dos**. If the search box doesn’t find it, try the prefix `task:` or type the full name.
2.  The task lists your existing To Dos. Add a new row (**+**).
3.  **Name:** `Confirm workspace move TT-CLA`
4.  **Description / Instructions:** Explain what the HR Partner should do, for example “Confirm the worker’s workspace or desk move is arranged for the new job/location, then submit.” If the work happens on a specific Workday page, include how to get there ([Hire Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/hire-business-process-guidelines--new-.html?toc=6.9.2)).
5.  Leave optional fields blank, such as a related task link, unless you need them.
6.  Click **OK**.

The To Do will now appear in the **Specify** list when you add the To Do step in step 3, since that list only shows To Dos already set up in Maintain To Dos ([Onboarding Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/onboarding-business-process-guidelines.html)). Steps 2–5 of my earlier instructions stay the same.

## If Maintain To Dos doesn’t come up either

The most likely reason is that your account doesn’t have security access to the task. Search only shows tasks you’re allowed to run. I couldn’t confirm from the documentation which security domain controls it, but it’s usually part of business process administration. If you can’t find it:

-   Ask your Workday security admin to run **View Security for Securable Item** on **Maintain To Dos**. That shows which domain controls the task and which groups can use it.
-   Or ask someone who already has that access to create the To Do. You can then add the step yourself, if you have permission to edit the Change Job definition.

Sources:

-   [Concept: To Do Step – Workday Admin Guide](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-step-types/dan1370797857694.html)
-   [Onboarding Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/onboarding-business-process-guidelines.html)
-   [Hire Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/hire-business-process-guidelines--new-.html?toc=6.9.2)
-   [Business Process Framework – Workday Education](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/business-process-framework.html)

## Turn 3: follow-up (sent 2026-11-20T07:49:07.187Z)

Step 1 is done: the To Do “Confirm workspace move TT-CLA” now exists (Maintain To Dos, new row, OK).

Step 2 says to search for and run the task “Business Process Definition”, or “View Business Process Definition”. Searching Workday for “Business Process Definition” and for “View Business Process Definition” finds no task or report with either name. The Tasks and Reports results are: Business Process Definitions (report: “View all business process definitions, owner, and any organization-specific custom business processes”), Business Process Definitions for Business Object (report, prompts: View as of, Organization), Business Process Definitions with Integration Steps using Deprecated Fields, Create Business Process Definition (Default Definition) (task), Maintain Business Process Definition Selection, Audit Trail - Business Process Definition, Business Process Types with Default Definitions in Use, Maintain Precedence for Business Process Definition Selection, All Business Process Definitions for Business Objects, Extract Business Process Definitions Summary, Extract Business Process Definitions, Inactivate Orphaned Business Process Definitions.

## Turn 3: answer (2026-11-20T07:49:21.324Z, 14.1 s)

Those two task names were wrong too. There’s no single task that opens a definition. You find it through a report and then edit it from its related actions. Two of the reports in your search results will get you there.

## Corrected step 2: Open the Change Job definition

**Option A (recommended): Business Process Definitions for Business Object**

1.  Run **Business Process Definitions for Business Object**.
2.  **View as of:** today
3.  **Organization:** your top-level **supervisory** organization. As I mentioned earlier, Change Job definitions sit on the supervisory hierarchy, not the company one.
4.  In the results, find the row for **Change Job** and click the definition.

**Option B: Business Process Definitions**

1.  Run **Business Process Definitions**. It lists every definition along with its organization.
2.  Filter or sort the **Business Process Type** column to **Change Job**.
3.  Click the one for your top-level organization. It’s usually marked as the default definition.

While you have Change Job filtered, check whether other organizations also have their own Change Job definitions. Workers in those orgs follow their own definition and won’t get your new step unless you add it there too.

## Edit the definition

From the Change Job definition:

1.  Click the **related actions** button (the “…” or twinkie icon) next to the definition name.
2.  Go to **Business Process → Edit Definition**. If you don’t see that exact name, look for **Maintain Steps** or **Edit** in the same submenu.
3.  If the page shows an **Effective Date** (or date/time) field, keep it at today or now. That way events started after you save use the new version, and events already in progress stay on the old one.

Then continue with step 3: add the row with order after the manager approval (e.g. **ba**), Type **To Do**, Specify **Confirm workspace move TT-CLA**, Group **HR Partner**.

**Don’t use** **Create Business Process Definition (Default Definition)**. It creates a separate new definition instead of changing the existing one, which can affect which definition gets picked for Change Job events.

If the **Edit Definition** option isn’t in the related actions menu, your account probably doesn’t have permission to edit business process definitions. A Workday admin with business process administration access would need to make the edit or give you access.
