Workforce Structures

This topic lists the implementation considerations for Workforce Structures processes.

Departments

You can typically use field value defaulting and validation in these cases.

  • Default Location in department based on a specific set.
  • Default Internal Address Line based on descriptive flexfield values.
  • Default Department Title from Department Name and Set.
  • Validate that Department Set and Location should match.
  • Enforce valid combinations of Department Name and department descriptive flexfield segments.

This table lists the supported attributes, exceptions, and the mplementation recommendations for the Departments page.

In the Conditions To Default Field Values To Validate Field Values Implementation Guidelines
  • ActiveStatus
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId
  • Name
  • SetCode
  • Title
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId Name
  • Title
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId
  • Name
  • Title

These aren't currently supported:

  • Defaulting in edit and duplicate flows
  • Attachments
  • Initial field values
  • Defaulting and validation for extensible flexfields

Jobs

You can typically use field value defaulting and validation in these cases.

  • Default Full time or Part time field with value as Part time
  • Default job level based on selected management level
  • Validate job name doesn't contain special characters
  • Validate job code contains six characters of which the first 3 are alphabets and the last 3 are numbers, without any special characters.

This table lists the supported attributes, exceptions, and the implementation recommendations for Jobs.

It applies to the Jobs pages under My Client Groups tab.

Flow In the Conditions To Default Field Values To Validate Field Values Implementation Guidelines
Jobs: Add, Duplicate, and Update flows
  • User Roles
  • Full time or Part time
  • Manager level
  • Level
  • Regular or Temporary
  • Jobs descriptive flexfield
  • Job Family Id
  • Job Name
  • Job Code
  • Job Function Code
  • Level
  • Jobs descriptive flexfield

Positions

You can typically use field value defaulting and validation in these cases.

  • Default assignment category.
  • Default location based on position descriptive flexfield (DFF).
  • Validate that position name includes job name and department name.
  • Validate standard working hours is not equal to 375 or 40.

This table lists the supported attributes, exceptions, and the implementation recommendations for the Positions pages.

It applies to the Positions pages under My Client Groups tab.

Flow In the Conditions To Default Field Values To Validate Field Values Implementation Guidelines
Positions: Add, Duplicate, and Update flows
  • User Roles
  • BargainingUnitCode
  • Budget Currency Code
  • BudgetedPositionFlag
  • Business Unit ID
  • Department ID
  • FullPartTime
  • HiringStatus
  • Job ID
  • Location ID
  • OverlapAllowedFlag
  • Position DFF
  • PositionType
  • ProbationPeriod
  • ProbationPeriodUnitCode
  • Regular or Temporary
  • Requisition Template ID
  • Union ID
  • ActionReasonId
  • PositionName
  • PositionCode
  • JobName
  • DepartmentName
  • LocationName
  • PositionsDFF
  • RequisitionTemplateId
  • AssignmentCategory
  • FullPartTime
  • RegularTemporary
  • Status
  • BusinessUnitId
  • StandardWorkingHours
  • Type
  • WorkingHours
  • EffectiveStartDate
  • BargainingUnitId
  • CollectiveAgreementId
  • UnionId
  • HiringStatus
  • ParentPositionCustomField
  • FTE
  • Cost Center ID
  • Headcount
  • StartTime
  • OverlapAllowedFlag
Any rule that refers to incumbent assignment data or collective agreement data is currently not supported.