Create Position Business Process Guidelines
Overview
The
Create Position
business process enables you to create new positions within a supervisory organization that is set up with the position management staffing model. Before you can hire an employee, an open position must be available with the necessary details and approvals.Key information captured during this process includes:
- Job posting title.
- Number of positions: You can create multiple positions with the same characteristics in a single event.
- Availability date: When the position is available on the organization chart.
- Earliest hire date: When you can start the recruiting or hiring process for the position.
- Any attributes you configure. Example: Job profile.
Subprocesses
The
Create Position
business process can have several other business processes configured to run as part of its workflow. While not an exhaustive list, these are common sub-processes you can include:
- Change Organization Assignments: To assign the position to a specific company, cost center, or other organizational units.
- Request Default Compensation: To set the default compensation for the new position.
- Assign Costing Allocation: To define how earnings for the position are allocated across ledger accounts, cost centers, projects, or grants before a worker is hired.
- Assign Pay Group: To pre-assign a pay group to the position restrictions for open positions.
Create Position
can be used as a subprocess of the Job Requisition
business process. This enables the creation of a new position and the requisition to fill it in a single workflow.Prerequisites
- There must be an existing supervisory organization where the position will be created, and it must be configured to use the position management staffing model.
- Security:
- Configure the business process security policy to grant specific security groups permission to these action steps:
- Cancel: Determine who can stop in-progress events. Typically the initiator and these security groups can cancel: Business Process Administrator, HR Administrator, and HR Partner.
- Correct: Restrict to groups with the domain expertise to correct data entry and who understand the cross-functional and downstream impacts. Typical security groups include HR Administrator.
- Initiating Actions: Determine who can start the Create Position process. Typical security groups include HR Administrator and HR Partner.
- Rescind: Restrict rescind permissions to central administrator-level groups. Typical security groups include HR Administrator.
- Review and Approval Steps: Determine who can approve the creation of the position. Typical security groups include HR Partner, Manager, Compensation Partner, and Finance Partner.
- View All: Determine who can view the in-progress or completed create position transaction. Typical security groups include HR Administrator, Business Process Administrator, and HR Partner.
- To view a list of all relevant security domains, access theDomain Security Policies for Functional Areareport and select the Staffing functional area.
- To view the security domains for a specific securable item, access theView Security for Securable Itemreport.
Process Initiators
Initiation of the
Create Position
business process is controlled by the Create Position
business process security policy. It is commonly initiated by:
- HR Partners from theCreate Positiontask or by selectStaffing>Create Positionfrom the related actions menu of the supervisory organization.
- Managers or HR Partners when theCreate Positionbusiness process is a subprocess of theJob Requisitionbusiness process.
- HR Administrator using the Create Position EIB. See Concept: Create Position EIB.
Your organization's specific configuration will determine which roles have the authority to initiate this process.
Limitations
The
Create Position
business process has the following limitations:
- While you can create a new position on theChange Jobtask, this action doesn’t trigger the fullCreate Positionbusiness process with its defined approval steps, validation rules, or review tasks. To ensure proper control over headcount, you can build position approval logic into theChange Jobbusiness process.
- You can’t directly trigger theJob Requisitionbusiness process as a sub-process ofCreate Position. However, you can add aTo Dostep at the end of theCreate Positionbusiness process to remind a user to initiate theJob Requisitionprocess.
Common Business Process Workflows
These are common workflow configuration paths for the
Create Position
business process, with the applicable steps for each flow.To view the diagram of a business process workflow, click
View Diagram
on the View Business Process Definition
page when you are editing the business process definition.You can customize the specific steps and the order in which they appear to fit your organization's unique requirements. You can add, remove, or reorder steps, and use condition rules to create different paths for different scenarios.
Path 1: Standalone Create Position with Full Approvals
This workflow is used when an organization separates headcount planning and approvals from the recruitment process. Positions must be approved and budgeted before a recruiter can link them to a job requisition.
A: Initiation by Manager
>
B: Action (Review Position Request) by HR Partner >
C: Action (Subprocess - Change Organization Assignments) by HR Partner >
D: Action (Subprocess - Request Default Compensation for Position Event) by Compensation Partner or HR Partner >
E: Action (Approval Chain) by Manager Group >
CompletionPath 2: Create Position as a Sub-Process of Job Requisition
This is a common configuration where a new position is created as part of the process of opening a new job requisition. This is ideal for agile organizations where positions are created on-demand when there is an immediate need to source and hire.
A: Initiation (as a sub-process of the
Job Requisition
business process) by Manager or Recruiter >
B: Action (Subprocess - Change Organization Assignments) by HR Partner or Recruiter >
C: CompletionPath 3: Standalone Simplified
This configuration is designed for organizations that leverage a centralized HR Operations team. All position creation requests are managed offline or through budget planning tools, and HR Administrators enter approved positions directly into Workday.
You can use this method to create multiple positions at once, such as during a reorganization or budget planning using:
- Org Studio and Mass Actions
- The Enterprise Interface Builder (EIB). When the EIB is configured for automatic processing, many of the standard business process steps like approvals and notifications may be skipped.
- Custom integrations with Workday web services.
A: Initiation (manually or with the Create Position EIB, Org Studio and Mass Actions, Adaptive Planning, or a custom integration) by HR Administrator
>
B: Action (Subprocess - Change Organization Assignments) by HR Administrator >
C: CompletionCommon Business Process Workflows for Consolidated Approvals
These are common workflow configuration paths for consolidated approval steps for the
Create Position
business process.Path 1: Consolidated Approval for a Single Reviewer
Use this path when a single person or group, like a Manager or HR Partner, needs to approve the position and its organizational and compensation details together.
A: Initiation
>
B: Action by HR Partner (Change Organization Assignments) >
C: Action by Compensation Partner or HR Partner (Propose Default Compensation) >
D: Consolidated Approval (Approve the Create Position, Change Organization Assignments, and Default Compensation events) >
E: CompletionPath 2: Consolidated Approval Chain for Hierarchical Review
Use this path when the position request needs to be approved by multiple levels of a management or organizational hierarchy.
A: Initiation
>
B: Action (Change Organization Assignments) >
C: Consolidated Approval Chain (Approve the Create Position and Change Organization Assignments events) by the management hierarchy >
D: CompletionWorkflow Step Types
These are the common step types used to build the Create Position business process workflow:
- Initiation
- Step Order: Always the first step in the business process.
- Group: Initiation is not performed by a single role but is controlled by the business process security policy. This policy grants specific security groups permission to use different initiating actions. Common roles and groups that are granted initiation rights include: Manager, HR Partner, HR Administrator, and Recruiter.
- Security Domains (by Roles):
- Manager: Modify access to these domains:Staffing Actions: Location and Worker Data: All Positions.The initiator needs View access to Staffing organization domains. Example:Staffing Organizations: Company.To create and place the position within that organization, you need Modify access to Staffing organization domains.
- HR Partner, HR Administrator, Recruiter: Modify access to these domains:Business Process AdministrationorManage: Business Process Definitions,Staffing Actions: Location,andWorker Data: All Positions.The initiator needs View access to Staffing organization domains. Example:Staffing Organizations: Company.To create and place the position within that organization, you need Modify access to Staffing organization domains.
- Specify: Not applicable. This step launches the process.
- Step Type Guidelines:
- Best practice: Ensure that only the appropriate roles have the security permissions to initiate the creation of a position to maintain control over headcount and organizational structure.
- Uses Case: A manager needs to hire a new team member for a newly approved project.
- Example: The manager of the Marketing Campaigns supervisory organization initiates the Create Position task to create a Marketing Specialist position.
- Action
- Step Order: Place anywhere after theInitiationstep.
- Group: Performed by Compensation Partner, HR Partner, Finance Partner, or Recruiter.
- Security Domains (by Roles): To determine the exact domains required for a specificActionstep in your tenant, use theView Security for Securable Itemreport.
- Specify: Select the specific business process to launch as a subprocess. Common examples forCreate Position:
- Assign Pay Group for Position Restriction
- Change Organization Assignments
- Step Type Guidelines:
- Best practices:
- UseActionsteps to delegate specific data entry tasks to the appropriate functional expert. This maintains a clear separation of duties and improves data accuracy.
- Use theReview Position Requestsubprocess when you want to enable the reviewer to correct minor mistakes directly and approve the request, rather than sending the task back to a manager for correction and delaying the process.
- Example: A Compensation Partner receives the initiated position request and uses the Change Default CompensationActionstep to add the appropriate compensation grade, grade profile, and salary range before it routes for approval.
- Condition Rule Guidelines:
- Best practice: Use entry conditions to route theActionstep only when necessary to skip steps that aren't relevant to a specific scenario.
- Uses Cases: Route to a Compensation Partner to default compensation only for salaried positions, not for hourly ones.
- Example: Use an entry condition rule that checks whether Pay Rate Type is equal to Salary to ensure the step only runs for salaried positions.
- For more information, see Concept: Action Step.
- Approval
- Step Order: Follows anInitiationstep or after any step where a decision needs to be reviewed and approved.
- Group: Performed by roles with authority. Example: Manager, Department Head, or HR Director. The choice of approver depends on your organization's policies and governance model.
- Security Domains (by Roles): You must specify the security group(s) responsible for the approval.
- Specify: You can configure an approval chain, which routes the approval up a management hierarchy until a certain level is reached.
- Step Type Guidelines:
- Best practices:
- Use an Approval step instead of an Action step that initiates theReview Position Requestprocess when you want a detailed audit trail of changes. The Approval step ensures that once a position request is submitted, nobody can alter the details without either sending it back to the initiator or denying it entirely.
- Use a singleApprovalstep for a single approver. For a hierarchy of approvers, use anApproval Chainstep.
- Use theConsolidated Approvalstep type when the approver needs to see details from subprocesses initiated by the main business process. The standardApprovalstep only displays information from the Create Position event, hiding details from related events like organization assignments or compensation changes.
- Uses Case: After the initiator and any specialist roles have entered all position details, anApprovalstep is routed to the HR Partner for final sign-off before the position is officially created.
- Example:
- Step a:Initiationby Manager.
- Step b:Approvalstep assigned to the HR Partner security group. The HR Partner reviews the core position details (Example: job profile and worker type) and approves.
- Condition Rule Guidelines:
- Best practice:
- For complex conditions, especially those based on data from other business processes (Example:Job Requisition), create calculated fields to retrieve the necessary information.
- Ensure your rules are precise to avoid unintended routing or skips. Test your rules thoroughly using theRule Testerreport on a specific event instance.
- Workday provides many delivered fields you can use in condition rules. Example: You can check if a position is being created as part of a job requisition process.
- Uses Cases: Require an additional approval from the Finance Director only if the proposed position's Job Level is Director or above.
- Example: Create a rule where Job Level (Proposed) is in the selection list Director and Above.
- For more information, see Concept: Approval Step.
- Approval Chain
- Step Order: Used after anInitiationstep and any other data-gathering steps when a management or organizational hierarchy requires multiple, sequential approvals.
- Group: This step dynamically routes up a defined hierarchy. It is not assigned to a single role but rather to a starting point in a Management Hierarchy or Organizational Hierarchy.
- Security Domains (by Roles): Not Applicable.
- Specify: Configure the chain by specifying the hierarchy it should follow and the starting point. Example: Management Hierarchy or Organization Hierarchy. To configure this, specify the security group that defines the hierarchy. Example: Manager for the management hierarchy. You can also define a stopping condition, such as reaching a specific management level or role.
- Step Type Guidelines:
- Best practices:
- Use exit conditions to stop the chain from going higher than necessary. This prevents senior executives from being inundated with routine approvals.
- For standard multi-level management sign-offs, such as a Manager then Manager's Manager, it's a best practice to use a singleApproval Chainstep. This configuration is significantly easier to build and maintain than creating multiple, separateApprovalsteps for each level.
- Clearly define the hierarchy you intend to use (Management or Organization) to ensure approvals route as expected. Use theView Diagramfeature of the business process to visualize the routing.
- Uses Cases: A new position request for a director-level role requires approval from the initiator's manager and all subsequent managers up to the Executive Vice President (EVP) of that division.
- Example: On theApproval Chainstep, Set the Group to Manager's Manager to start the chain one level above the initiator's direct manager. Define an exit condition rule to check if the approver's role is EVP. This stops the approval chain once it reaches the EVP role.
- Condition Rule Guidelines:
- Best practice:
- Use an entry condition to determine if the entire approval chain should run. This is effective for differentiating workflows based on the type of position or other attributes.
- Use an exit condition that evaluates a field that changes as the process moves up the chain, such as the approver's management level or role.
- Uses Cases: An organization has a policy that creating a new position for a regular Employee requires a full management chain approval up to the Senior VP. However, creating a position for a Contingent Worker only requires approval from the direct manager.
- Example: Configure a standardApprovalstep for the direct Manager to handle the contingent worker scenario. Configure a separateApproval Chainstep that starts with Manager's Manager and has an exit condition to stop at the Senior VP. Apply an entry condition to theApproval Chainstep. Create a condition rule that checks if the Worker Type for the new position is Employee.
- For more information, see Concept: Approval Chain Step.
- Consolidated Approval
- You can add aConsolidated Approvalstep in place of a standardApprovalorApproval Chainstep within the business process definition.
- Step Order: Place after theInitiationstep and anyActionsteps whose data you want an approver to view.
- Group: Performed by a Manager, HR Partner, or a specific management-level approver.
- Security Domains:
- Modify access on theBusiness Process Administrationdomain.
- View access on these domains:Position Management,Core HCM Data,Organization Management,Compensation(if compensation details are being consolidated)
- Specify: Not applicable.
- Step Type Guidelines:
- Best practice:
- Use this step to combine theCreate Positionbusiness process event with its subprocesses, giving the approver all necessary information in 1 place.
- When replacing a standardApprovalstep with aConsolidated Approval, ensure you migrate any existing configurations, such as condition rules, due dates, and help text, to the new step.
- A standardApprovalstep may be automatically skipped if the initiator is also the approver. AConsolidated Approvalstep ensures the approval task is still generated and routed as intended.
- Ensure the security group assigned to the step has the necessary permissions for all subprocesses being consolidated to avoid errors.
- Uses Cases: When a new position is created, an approver needs to review not only the position's attributes (like job profile and location) but also the financial and organizational assignments (like company and cost center) that are part of a separate subprocess.
- Example: A manager initiates theCreate Positionprocess for a new Analyst role. The business process includes anActionstep to perform theChange Organization Assignmentssubprocess. The next step is aConsolidated Approvalrouted to the Director. The Director receives a single notification in My Tasks that displays both the core position details and the organization assignments for their review and approval.
- Condition Rule Guidelines:
- Best practice:
- Use entry condition rules to ensure theConsolidated Approvalstep only runs when necessary, which helps to keep business processes efficient.
- Base your rules on clear and reliable data available within the business process at that point. Use fields directly on the position object.
- Thoroughly test your condition rules to confirm the step triggers as expected and does not cause the business process to get stuck or be routed incorrectly.
- Uses Cases: Your organization decides that only senior-level positions require a Finance Operations review, while lower-level positions can follow a more basic approval path.
- Example: Add a condition rule to theConsolidated Approvalstep so that it runs only for new positions at the Director level or higher. Rule logic:
- Source of Condition:Field
- Business Object:Create Position Event
- Field:Position's Management Level
- Relational Operator:in the selection list
- Comparison Value:Director, Executive
- For more information, see Concept: Approval Step.
- Consolidated Approval Chain
- You can add a consolidatedApproval Chainstep in place of a standardApprovalorApproval Chainstep within the business process definition.
- Step Order: Placed after theInitiationstep and anyActionsteps that need to be approved but before theCompletionstep.
- Group: Performed by the manager of the initiator (or another defined starting point) and moves up the selected hierarchy.
- Specify: Configure the chain by specifying the starting point and whether it follows the management or organization hierarchy. Select which subprocesses to include in the approval.
- Step Type Guidelines:
- Best practice: Define an exit condition to stop the chain from going all the way to the top of the hierarchy. This can be based on reaching a certain management level, a specific role, or after a certain number of approvals.
- Uses Cases: A manager initiates the creation of a new Director-level position. The organization requires that the position details and the associated organizational and cost center assignments are approved by the management chain up to the level of Vice President.
- Example: Configure aConsolidated Approval Chainstep to bundle theCreate PositionandChange Organization Assignmentsbusiness processes. Route the chain up the management hierarchy, starting with the initiator's manager. Set an exit condition to stop routing once the approval task reaches a manager with the Vice President role.
- Condition Rule Guidelines:
- Best practice:
- Use step entry condition rules to determine whether theConsolidated Approval Chainis required for a specific transaction. This enables dynamic approval routing based on the data.
- For complex scenarios, you can configure multipleConsolidated Approval Chainsteps, each with its own entry condition, to handle different approval paths within the same business process.
- Uses Cases: An organization has different approval requirements for creating positions for full-time employees and contingent workers. Full-time positions require a multi-level management review, while contingent positions only need approval from the direct manager.
- Example: Add aConsolidated Approval Chainstep for the full management hierarchy with the entry condition Worker Type Hiring Requirement is Employee. Add a standardApprovalstep assigned to the Manager with the entry condition Worker Type Hiring Requirement is Contingent. When a position is created, Workday evaluates the worker type and triggers only the appropriate approval step.
- For more information, see Concept: Consolidated Approval Chain Step.
- Edit Additional Data
- Step Order: Place before theCompletionstep to ensure data is saved correctly for all positions created in a single event.
- Group: Performed by Initiator and HR Partner.
- Security Domains: View and Modify permissions to the domain that secures the custom object being used in theEdit Additional Datastep.
- Specify: Select the effective-dated custom object that you want to be available for editing.
- Step Type Guidelines:
- Best practice:
- Ensure that any custom objects you use with this step are properly configured on the Position Restrictions business object and have at least one field.
- If you need to capture multiple distinct sets of information, you can add multipleEdit Additional Datasteps to the business process, each linked to a different custom object.
- Uses Cases: Your organization requires a budget code to be associated with every new position.
- Example: Create an effective-dated custom object on Position Restrictions called Budget Information with a text field for Budget Code. In theCreate Positionbusiness process definition, add anEdit Additional Datastep. In theSpecifycolumn, selectBudget Information. Assign this step to the Manager security group.
- Condition Rule Guidelines:
- Best practice:
- Use calculated fields to evaluate criteria that are not directly available on the business process object.
- Clearly name your condition rules so their purpose is easily understood.
- Uses Cases: You only want to capture additional details for Contingent Worker positions.
- Example: Create a condition rule that checks the value of the Worker Type field on the position being created. Configure the rule to evaluate to true if Worker Type is Contingent Worker. Apply this condition rule to theEdit Additional Datastep.
- For more information, see Concept: Edit Additional Data Step.
- Completion
- This step signifies that the main workflow is finished. Once theCompletionstep is executed, the position is considered fully approved, and subsequent steps can run without holding up the core process.Review the steps and identify which one should represent the final, required action for the time entry to be considered approved. This is often the finalApprovalstep in the sequence. Locate the row for this step in the grid, and from the related actions menu of that step, selectBusiness Process>Set to Completion.A business process can only have 1Completionstep. If another step is already marked as theCompletionstep, Workday will automatically uncheck it and apply the designation to the step you have just selected.
Integration
Adding an
Integration
step type allows you to initiate automated data sharing or system actions in external applications as part of your staffing workflow.- Step Order: Place after theCompletionstep to prevent transmitting unapproved or in-progress position data to external systems.
- Group: Performed by an Integration System User (ISU) that has the necessary security permissions to run the integration.
- Specify: Select the specific integration system to run. This could be a pre-built Workday connector or a custom-built integration using Workday Studio, Enterprise Interface Builder (EIB), or Core Connectors.
- Step Type Guidelines:
- Best practice:
- Use a dedicated ISU with the security permissions required to run the integration.
- Use Entry Conditions to ensure the integration only runs when all data is final and approved.
- Always configure a redirect on theIntegrationstep. If a network interruption or endpoint failure occurs, Workday can automatically route the failed step to an integration administrator or advance the process, rather than cancelling the entire position creation.
- Uses Cases: When a new position is created in Workday, it must be automatically synchronized with an external recruitment portal so that the recruiting team can begin sourcing candidates immediately.
- Example: In theCreate Positionbusiness process, you add anIntegrationstep after theCompletionstep. You configure it to run an outbound Studio integration. When a position is approved, the step initiates and securely transmits the position information to the external applicant tracking system (ATS) using a REST API.
- Condition Rule Guidelines:
- Best practices:
- Keep condition rule logic simple by using optimized calculated fields to minimize transaction processing overhead.
- Positions can be created through other business processes (Example:Job Requisition). Use condition rules to control which processes can initiate an integration.
- Uses Cases: Ensure that the integration runs only when a position is created as a standalone event. If a position is automatically created as part of theJob Requisitionbusiness process, skip this step because the job requisition workflow already handles its own downstream ATS provisioning.
- Example: Create a condition rule that checks that the business process parent event is empty.
- For more information, see Concept: Initiation Step and Create Integration (Step).
Notifications
System Notifications
System notifications are default alerts generated by Workday for business process events. You can view all system notifications on the
Notifications
tab of the BP. Workday allows you to disable a specific notification, though it’s often better to manage notification preferences at the user level or use custom notifications for more targeted alerts. See Configure Business Process System Notifications.Global notification settings are managed in the
Edit Tenant Setup - Notifications
task.Custom Notifications
You can create custom notifications that can initiate on any step of the business process to alert users about events, required actions, or status changes. To create a notification, navigate to the respective step in your business process definition and from the related actions menu of that step, select . See Create Custom Notifications.
- Guidelines and Best Practices:
- Ensure Proper Security Access for Dynamic Fields: When including report fields (Example: Job Profile, Compensation Grade) in the message body, verify that the notification recipients have security access to those fields. When a recipient lacks the necessary security permissions, Workday displays “not available” instead of the actual value.
- Manage Email Fatigue by Disabling System Defaults: If you are building a highly customized notification to replace a standard Workday-delivered email, disable the default system notification. This prevents users from receiving duplicate notifications.
- Designate From Email Addresses Strategically: You can customize the From email address in the notification configuration to use an organizational or shared mailbox (Example: recruiting@company.com) rather than a default system sender, making the communication more professional and recognizable.
- Test with Condition Rules: If a custom notification has condition rules applied, always test them thoroughly in a Sandbox environment. If the conditions are not met, the notification will not fire.
- Don’t Include Notification Details Link for External Users: If you send a notification to someone without a Workday account, selectDo Not Include Notification Details Link. This prevents external recipients from receiving a broken link to sign in to Workday.
- Use Cases with Examples:
- Notify Recruiters of Approved Positions to Initiate Hiring
- Goal: When a hiring manager gets approval for a new position, the Recruiting Team needs to know immediately so they can post a job requisition and start sourcing candidates.
- Setup:
- Trigger: Status: Completed.
- Recipients: Recruiter security group (related to the Supervisory Organization where the position was created).
- Condition Rule: None (applies to all completed positions).
- Example Message:Subject: Action Required: New Position Created - {Position ID}Hello Recruitment Team,A new position has been successfully created and approved:
- Position ID: {Position ID}
- Job Profile: {Job Profile}
- Supervisory Organization: {Supervisory Organization}
- Target Start Date: {Target Start Date}
Please log into Workday to open a Job Requisition for this position.
- Notify Compensation/Finance of High-Level Executive Positions
- Scenario: The creation of senior-level positions requires additional scrutiny from the Compensation and Finance teams for budgeting purposes.
- Trigger: Status: Completed (or on entry of the final approval step).
- Recipients: Compensation Partner security group.
- Condition Rule:Management Level of Job Profileis equal to or greater thanDirector.
- Example Message:Subject: Notification: High-Level Position Created - {Job Profile}Hello Compensation Team,Please be advised that a new executive-level position has been created:
- Position: {Position ID} - {Job Profile}
- Manager: {Manager}
- Supervisory Organization: {Supervisory Organization}
This notification is for your records. No further approval actions are required in this process.
- Notify the Initiator of a Denied Position Request
- Scenario: If a request to create a position is denied by an approver, the initiator needs to be notified immediately so they can review the comments, make corrections, or re-apply.
- Trigger: Status: Denied.
- Recipients: Initiator.
- Condition Rule: None.
- Example Message:Subject: Create Position Request Denied: {Job Profile}Hello,Your request to create a new position for the job profile {Job Profile} has been denied.To view the reasons and comments provided by the approver, access yourArchivetab and search for the Create Position event.
Issues and Solutions
Issue | Cause and Solution |
|---|---|
The create position event does not follow the default definition workflow. | Cause: There are 2 Create Position business process definitions, the default definition and a rule-based business process definition. When a stand alone event was initiated, the rule-based business process definition condition rule was met, initiating the rule-based business process definition instead of the default definition.Solution: To identify the active business process definition, select Business Process > View Definition from the related actions menu of the event. From the related actions menu of the rule-based business process definition, select Business Process > Rule Based Business Process Configuration . Review and adjust the condition rules to ensure correct routing logic. |
Users can’t initiate the Create Position task in specific supervisory organizations. | Cause: Initiators are assigned to a constrained, role-based security group, which limits their access to only the specific organizations they support. Solution: Assign the users to an unconstrained security group or assign them to the appropriate supporting role for the target supervisory organizations. Cause: Initiators are assigned to a supervisory organization with no superior organization or an incorrect superior organization. Solution: From the related actions menu of the supervisory organization, select Reorganization > Assign Superior to link the organization to the correct position within the hierarchy. |
The newly created position is unavailable when trying to create a job requisition. | Cause: There is an in-progress or future-dated transaction (such as a pending Edit Position Restrictions or Edit Position Restrictions Additional Data step) locking the position.Solution: On the Job Profile report for the position, select the Business Process History tab. Complete, reassign, or cancel the in-progress business process event to release the lock on the position.Cause: There is a pending staffing transaction associated with this position. Example: Job Requisition. Solution: Cancel the in-progress transaction or use the existing transaction instead of creating a new one. Cause: The position or supervisory organization is frozen. Solution: Use the Manage Position Freeze task to unfreeze the position.Cause: The date you’re trying to create a position for is before the availability date specified for the position. Solution: Edit the position restrictions. |
A validation error occurs during Org Studio mass actions, preventing position creation. | Cause: The Create Position business process definition includes approval or manual intervention steps that disrupt automated mass processing.Solution: Simplify the Create Position business process definition used for mass actions by removing manual steps and approvals to allow automated completion without user intervention. |
The EIB upload fails with the error: "Validation error occurred. The Position Organization Assignments Data element is required when Automatically Complete is True". | Cause: During automated processing, required organization assignment data is missing from the template, or the Change Organization Assignments step is not bypassed.Solution: Populate the required organization assignments in the EIB input file, or configure the business process step processing instructions to skip processing when the step is marked optional. |
Bulk position creations (typically over 100 positions in a single transaction) fail to inherit organization assignment details (Example: Company, Cost Center, Region). | Cause: There is a limitation on the number of positions that can be successfully processed in a single transaction. Solution: Divide bulk position creation requests into batches with fewer than 100 positions per batch. Verify that organization assignments default correctly before loading subsequent batches. |
An error or conflict occurs when executing the Create Position business process. | Cause: There are multiple Change Organization Assignments steps in the business process flow without mutually exclusive condition rules, causing them to execute simultaneously.Solution: Review the business process definition and configure mutually exclusive condition rules on the Change Organization Assignments steps so that only 1 step fires per transaction. |
The Create Position subprocess remains pending on the Change Organization Assignments step when loaded with the Create Job Requisition EIB. | Cause: The step is routed to a user role that doesn’t resolve or cannot complete during an external integration load. Solution: Add a condition rule on the Change Organization Assignments step to skip the step for integration loads. Example: External Load not equal to Yes. |
Position creation via EIB fails with the error, "At least one of the Custom organization types is required based on the position assignment details settings but has no entries."
| Cause: 1 or more custom organization types are marked as required for positions in the tenant, but are missing from the load file. Solution: Access the Maintain Organization Types report. On the Custom tab, identify which custom organizations have Position Assignment Required set to Yes. Either populate these in the EIB spreadsheet, or default them on the supervisory organization. |
Custom validation rules on the Create Position business process are ignored during job changes. | Cause: Selecting the New Position option within a Change Job flow triggers an internal automated creation event that bypasses the standalone Create Position business process.Solution: Configure required position validations at the Change Job business process level, or apply validations directly to the job profile or supervisory organization settings rather than relying solely on the Create Position business process. |
For issues not listed here, we recommend searching for knowledge articles in Community. For the best results:
- Search for the exact name of the process using double quotes (for example, "Onboarding Business Process").
- Refine the initial results by selecting these search filters:
- Content Group:Articles
- Content Type:Knowledge Article
- Use theSort byfilter to view the results byRelevanceorNewest.