Concept: Editing Organization Units in Statement of Work
You can edit organization units on both
Draft
and Active
Statements of Work (SOWs). Editing Organization Units on Draft SOWs
To edit the
Organization Unit
on Draft
SOWs, navigate directly to a specific SOW's Overview
tab. Your edits immediately apply to the SOW and any of its roles. If contractors are applied to any of the SOW's roles, your edits also apply to their pending work orders.Programs with the Workday Integration
If your program uses the Workday integration, you can only change the
Organization Unit
to a unit with a different staffing model if the Prevent switching between staffing models on SOWs and SOW roles
setting is disabled in the Workday Settings
section of your VNDLY Company Settings
. If an SOW's
Organization Unit
changes from a unit with a Staffing Model
of Position Management
and any of the SOW’s roles are eligible for provisioning, VNDLY automatically removes any previous Workday position IDs from the roles. You can manually add new Workday position IDs to the roles, or you can wait for the Workday integration to assign Workday position IDs once the SOW is approved. If the SOW's Organization Unit
changes to a unit with a Staffing Model
of Position Management
, you can choose to make all roles eligible for provisioning so that Workday position IDs can be added.Editing Organization Units Active SOWs
To edit the
Organization Unit
on an Active
SOW, create a change order. Once the change order is approved, the organization unit updates on the SOW and any of its roles. If contractors are applied to any of the SOW's roles, the organization unit also updates on their pending work orders, but active work orders aren't updated. You can skip the vendor review process for these change orders by selecting Organization Unit
for the Skip Vendor Review for Change Orders
field in your SOW Configuration
settings. We also recommend selecting Role Resource Manager
for this field, since changing organization units often requires changing resource managers.Programs with the Workday Integration
If your program uses the Workday integration, you can only change the
Organization Unit
to a unit with a different staffing model if the Prevent switching between staffing models on SOWs and SOW roles
setting is disabled in the Workday Settings
section of your VNDLY Company Settings
. If an SOW's
Organization Unit
changes from a unit with a Staffing Model
of Position Management
, you'll have one of several options to manage any unfilled Workday positions on the SOW's roles The available option depends on your Close Unfilled Positions on SOW Roles and Close Positions for all Workflows
setting configuration in your integrations settings ():- IfClose Positions for all Workflowsis enabled, an alert notifies you that all unfilled positions will close automatically.
- IfClose Positions for all Workflowsis disabled andClose Unfilled Positions on SOW Rolesis enabled, a check box displays for SOW managers to choose if they want to close unfilled positions automatically.
- IfClose Positions for all Workflowsis disabled andClose Unfilled Positions on SOW Rolesis disabled, an alert notifies you that all unfilled positions will remain open.
If an SOW's
Organization Unit
changes to a unit with a Staffing Model
of Position Management
, you have the option to make all roles eligible for provisioning, which allows the Workday integration to add Workday position IDs. Once the change order is approved internally, VNDLY sends the changes to Workday for approval, and the change order status displays as
Connector in Progress
in VNDLY. While in this status, VNDLY pauses onboarding for SOW roles to prevent onboarding contractors with position IDs that are closed in Workday. If the change order is approved in Workday, the organization unit updates on the SOW and its roles. Additionally, if contractors are applied to any of the SOW's roles, the organization unit updates on their pending work orders, but active work orders aren't updated. If Workday rejects the change order, the organization unit doesn't update in VNDLY.