Types of Work Codes

Four types of behaviors are associated with work codes: Non-Working, Regular Duty, Signup, and Working.

The most frequently created work code types are non-working followed by working.

  • Nonworking: creates a vacancy on the Roster. Use non-working codes to remove people from their regular assignment; for example, vacation, sick, on-duty training
  • Working: fills a position on the Roster. Use working codes to denote a different or an additional assignment; for example, overtime, court off-duty, mandatory, holdover, special event, off-duty training, and so on.
  • Regular Duty: fills a position. Use regular duty codes to signify that a person is in their scheduled job for the day (their ‘shift assignment’). This is straight pay and a non-exception code that is automatically applied to the person on the Roster. A regular-duty work code is typically preset with a white color background so that it blends with the user-interface.
  • Signup: used mainly for volunteering purposes. Use signup codes to indicate availability or nonavailability for additional working opportunities or jobs. See Signup Types topic for additional information. Signup Codes are not pushed to Dimensions.

Dimensions and Work Codes...

A nonworking type code translates to schedule pay code edits by default in Dimensions. To override the default behavior, choose Send as Segment with Tag.1

A regular and a working type work code translates to a shift with segment in Dimensions; except when a working type work code is flagged as On Call which translates to a schedule tag. To override the default behavior, choose Send as Pay Code Edit.2 A tag is optional and based on configuration.

Application version 7.1.13+ introduced two properties in the integration.properties file that return the corresponding shift segment for any period of time that an employee is not working as a result of a non-working exception in a Dimensions integration.

Note: In application version 7.4+ these settings are now built-in the database and located in the Integration table of the Tenant Properties section in the System area.
  • schedule.event.simple.assignment=true Main property which defines whether this application will send a virtual working segment for each non-working time to Dimensions. Default is false (Disabled).
  • schedule.event.simple.assignment.noPaySegmentTag= This optional property is only needed if schedule.event.simple.assignment=true and a No Pay Segment Tag is desired. Default is blank. This property defines the No Pay Segment Tag that will be sent as part of the virtual working time segment. If left blank, then No Pay Segment Tag will not appear in Dimensions. When a No Pay Segment Tag is supplied in the property, this tag must be different than the No Pay Segment Tag used in the Schedule Integration area located in the Import Manager. Sample Format: schedule.event.simple.assignment.noPaySegmentTag=NoPaySegmentTag2020.

Important: When using the above mentioned properties be sure to configure your regular duty or working type work code properly. This means, a non-working type work code that does not have a matching regular duty or a matching working type work code must have a regular duty or a working type work code with Send as Segment with Tag selected in the work code’s configuration in order to cover the time gap. This also means the work code used to define the regular duty work code must have Include in Integration and Send as Segment with Tag selected; and this regular duty work code must be the work code assigned to the List Plan that is associated with the position, or the work code referenced in an Overriding Assignment Work Code.

Note:

Merge Adjacent Working Period in the Dimensions Integration area is not supported when changing the default behavior of work code types.