Companies with a Corporate plan can streamline the job creation process by establish dependencies between Job and Org fields and their values. Instead of having to pick from all available fields and values at the same time, job creators select details in sequence, and pick from only fields and values that are relevant to the job. Each choice they make determines the next available fields and values.
As a result, even for companies with complex and large organizational structures, job creators can easily create jobs and eliminate errors to ensure accurate reporting.
You'll need an Administrator account to set up dependencies.
You can also set up dependencies using our Configuration API.
Imagine this organizational structure:
- Company A organizes its hiring into the following structure: Business Unit -> Business Type -> Division -> Cost Center -> Job type.
- There are two business types: retail store and office.
- There are seven divisions: Sales, Customer Support, Product Development, Inventory, Marketing, Legal, and Finance.
- Retail stores have Customer Support and Inventory divisions. Offices have Sales, Marketing, Legal, Customer Support, and Finance divisions.
- Each division has at least one cost center.
- Retail stores hire for two position types: full- and part-time. Offices hire for only full-time jobs.
Even in this simple example, recruiters have to make a number of choices when creating a job, and can easily make mistakes, such as selecting the Sales division when hiring for a part-time job in a retail store, which has no Sales division.
This company’s admin can set up parent-child dependencies between these fields (and their values) so that:
- Recruiters make choices in this sequence: Business Type > Divisions > Cost Center > Position Type.
- If a recruiter chooses Retail Store as the business type, their options for Divisions are Customer Support and Inventory, and they can hire for full- or part-time positions.
- If a recruiter chooses Office, they can’t select Inventory as a Division, and can only hire for full-time positions.
Essentially, the process of creating dependent fields takes your existing Job or Org fields and organizes them into a tree of parent/child dependencies.
- Each tree can have up to 10 levels.
- At each level, each parent field can have one or more child fields.
- Each child field can have only one parent field.
- Any job field can be a parent or child of another job or org field, but not all fields must be a parent or child.
- Org fields other than Country and Brand can be a parent or child of another job or org field. Country and Brand can only be parents.
If you're not already on the Job Fields page:
- Navigate to Settings / Admin.
- Click Job Fields in the Configuration list.
Set field dependencies
- Decide which field should be displayed first. This is the root of the tree.
- Click the Dependencies icon for the root field.
- From the list of fields without parents, choose one or more children and click Save.
- Repeat for other children.
- Continue until you’ve created the entire tree.
Set value dependencies
By default, only the child field itself is dependent, and all of its values are available when any value for its parent is selected. You can also set dependencies on child values, so that the value selected for its parent determines which of a child field’s values are available.
To set value dependencies:
- Click the Edit icon for child field.
- In the Configure Dependencies table, select a value for the parent, and select the child values that should be available when that parent value is selected.
- Click Save.
Let's look at an example. Suppose a company has two Org fields: Division and Business Type.
- The Parent field is Business Type, with two values: Office and Retail Store.
- The Child field is Division, with seven values: Sales, Customer Support, Product Development, Inventory, Marketing, Legal, and Finance.
Business rule 1
When a job creator selects Retail Store as the value for Business Type, they should only see the Customer Support and Inventory options for Division.
To set this dependency:
Business rule 2
When a job creator selects Office as the Business Unit, they should should see all values for Division, except for Inventory.
To set this dependency: