Skip to content
KiweelyKiweelyKiweely

Why are Change Organization Assignments fields blank after a Change Job that changes the position?

In Change Job, organization assignments default from the job requisition, then the proposed position restriction, supervisory organization or current position, by staffing model. Blank values mean the source had none, or the type is not allowed.

  • Checked against Workday on
  • Applies to Workday HCM, Change Job and Change Organization Assignments for Worker
  • 7 min read
  • Published
  • By Kiweely
On this page

Change Job fills the organization assignments from one source, picked by a fixed order that depends on the staffing model. When the fields come out blank, the source that won had no organization of that type, or the type is not allowed on the proposed supervisory organization or location hierarchy. This page walks through the order, the settings that change it, and how to check each one without guessing.

How does Change Job default organization assignments?

The Change Organization Assignments for Worker subprocess sets the defaults when the Change Job event runs. Workday documents the order below.

Staffing model Source of the defaults, first match wins
Staffing modelJob management, filling a requisition that has organization assignments Source of the defaults, first match winsThe job requisition.
Staffing modelJob management, current and proposed supervisory organizations both job management Source of the defaults, first match winsEither the current job or the proposed supervisory organization, set by the Change Job Use Default Organizations for Job Management check box in Edit Tenant Setup - HCM.
Staffing modelJob management, otherwise Source of the defaults, first match winsThe proposed supervisory organization if it has defaults, else the current job.
Staffing modelPosition management, filling a requisition that has organization assignments Source of the defaults, first match winsThe job requisition.
Staffing modelPosition management, creating a new position Source of the defaults, first match winsThe proposed supervisory organization if available, else the current position.
Staffing modelPosition management, using an existing position Source of the defaults, first match winsThe proposed position restriction. If it has no organizations, the proposed supervisory organization. If that has none, the current position.

Source: Reference: Default Organization Assignments, doc.workday.com. The worker transfer concept page lists the same position-management chain as: proposed requisition, proposed position, proposed supervisory organization, current position.

The last column is the point. Workday describes each default as populating from one source, not as a merge of several. A source with a cost center and no region is therefore a source with no region to give, and Workday’s page does not describe it falling back to the current position for that one type.

Why are the fields blank after the position changed?

The documented causes, each of which you can confirm on a single record:

  1. The new position restriction has no organizations. In position management with an existing position, the restriction is read first. Open the position restriction for the proposed position and look at its organization assignments.
  2. A new position was created from a supervisory organization with no default organizations. The new position takes the supervisory organization’s defaults, so an empty set gives empty fields. Check the organization’s assignments.
  3. The job management tenant option is not set as expected. With Change Job Use Default Organizations for Job Management checked, Workday moves the worker into a new job, populates organizations from the requisition or the proposed supervisory organization, removes role assignments and creates a new position ID. Unchecked, it moves the job with the worker, keeps the same organizations, role assignments and position ID. A team expecting carried-over values with the box checked sees defaults from the new supervisory organization instead.
  4. The organization type is not allowed. The Organizations section shows only the types set as Allowed Organizations on both the supervisory organization and the location hierarchy. If the position’s location is in several location hierarchies, only the organizations allowed across all of them as of the effective date are shown.
  5. The type is not enabled for staffing. A costing or custom organization type must have Show in Change Organization Assignments and Job Requisition selected in Maintain Organization Types. Without it, some organization data is not available and the organization does not display on the worker position.
  6. Related worktags. For cost centers, custom organizations, gifts and grants with related worktags, values from the worktags override what the position holds. Moving a worker to a position with no organization assignments and no supervisory defaults populates only worktag-related organizations, and no others populate.
  7. The initiator cannot see the section. The initiator’s access to the supervisory organization decides which Change Job fields are visible, and roles that can initiate Change Organization Assignments for Worker also need edit permission on the Staffing Organizations: Header domain. A hidden section can look like an empty one.

Does Change Job run Change Organization Assignments for Worker at all?

Only when it is configured. Per Set Up Job Changes, each consolidated subprocess must be an action step on the Change Job definition, added before the Complete step, and the consolidated template (Business Process > Configure Consolidated Template from the business process type) must include Change Organization Assignments for Worker. Change Job stays first in the order.

Two behaviors change what the initiator sees:

  • With the subprocess consolidated, Workday re-evaluates the defaults each time the proposed supervisory organization changes. Run alone, the defaults do not change after the first selection.
  • A condition rule on the step can skip it. Workday’s own example runs the step only when the worker’s location changes. A position change that leaves the location alone would then never reach the organizations.

The consolidated template can also be overridden per initiating action (Change Job, Request Transfer, or Change Location from a worker) with Configure Consolidated Template Override, so the same tenant can show the section from one entry point and not from another.

What does the by Organization process show in its Review step?

Change Organization Assignments for Workers by Organization is the mass version. It launches the Change Organization Assignments for Worker subprocess for each position in the organization, and the subprocess completes automatically. A Review or Approval step placed where the subprocess would be has nothing to show. Workday’s concept page says to add condition rules and workflow steps to the parent business process.

For Move Workers (Supervisory) with the Change Organization Assignments subprocess, Workday routes one task for each inbound organization, based on the security of the inbound supervisory organization, and bypasses per-employee reviews. The tenant option Mass Change Organization Assignments Defaulting sets the default behavior for that subprocess, and it can be changed on a specific transaction.

In the mass task, a blank Proposed Organization deletes the worker’s current organization of that type. A review step that looks empty may be hiding that.

How do you configure it so the values carry?

  1. Decide the source. Put the organizations on the position restriction (position management) or on the supervisory organization defaults (job management), because that is where Change Job reads them.
  2. In job management, set Change Job Use Default Organizations for Job Management to match what you want: checked to take the new supervisory organization’s defaults, unchecked to keep the current ones.
  3. Add Change Organization Assignments for Worker as an action step before Complete on the Change Job definition, and include it in the consolidated template.
  4. Review any condition rule on the step. If it is meant to run on position changes, the rule must test the position, not only the location.
  5. Confirm Allowed Organizations on the supervisory organization and the location hierarchy include the types you expect, and that custom types have Show in Change Organization Assignments and Job Requisition selected.
  6. Run the Organization Assignment Exception Audit report, which lists invalid organization assignments for a position restriction based on the allowed values of its supervisory organization or location hierarchy.
  7. If a finished event came out wrong, run a Change Organization Assignments for Worker correction or a new event. Workday notes you can correct the latest event when it is standalone or a subprocess, and that after correcting a Change Job supervisory organization or position you should review the worker’s organization assignments.

Worked example: moving Logan McNeil to a new position

Logan McNeil in Global Modern Services moves to a position under a new supervisory organization that uses position management. The initiator opens Change Job, selects the proposed supervisory organization and an open position, and reaches the Organizations section with Cost Center filled and Region empty.

This is an illustrative case, not a recorded run. Reading the table: no requisition, an existing position, so the proposed position restriction is read first. It has a cost center and no region, so the cost center is used and nothing else is added from the current position. Fixing it means adding the region to the position restriction, or setting it by hand in the section before submitting. If the section is missing, the Change Organization Assignments for Worker step is not in the definition or its condition rule skipped it.

How Kiweely does this job

Kiweely is an AI agent for Workday in a desktop app. With your consent it can read the Change Job definition, the consolidated template and the position restriction in your tenant to show which source supplied each blank, and it changes the tenant only with consent.

Frequently asked questions

Does Change Job copy the old organization assignments to the new position?

Only in some cases. In job management it depends on the Change Job Use Default Organizations for Job Management setting in Edit Tenant Setup - HCM. In position management the order is job requisition, proposed position restriction, proposed supervisory organization, then current position, so the old values carry only when nothing earlier in that list has organizations.

Why does the Change Organization Assignments step not appear in my Change Job?

The subprocess has to be an action step on the Change Job definition, added before the Complete step, and be part of the consolidated template. A condition rule on the step can also skip it, and Workday cancels the subprocess in some staffing events when you leave the defaults unchanged.

What happens if I clear a proposed organization?

In Mass Change Organization Assignments, a blank Proposed Organization deletes the worker's current organization of that type. Check blank proposed values before submitting.

Why does the Review step on Change Organization Assignments for Workers by Organization show nothing?

That process launches Change Organization Assignments for Worker for each position and the subprocess completes automatically. Workday's guidance is to put condition rules and workflow steps on the parent process.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.