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 such as, vacation, sick, training while on-duty, shift adjust, and so on.
Working fills a position on the Roster. Use working codes to denote a different assignment such as working out of class or to denote an additional assignment such as overtime, court off-duty, mandatory, holdover, special event, training off-duty, and so on.
Regular Duty: fills a position. Use regular duty codes to signify that a person is in their scheduled place of duty for the day. This is straight pay and a non-exception code that is automatically applied to the person on the Roster.
Signup used mainly for volunteering purposes. Use signup codes to indicate availability or nonavailability. See Signup Types topic for additional information. Signup Codes are not pushed to Dimensions.
In Dimensions a nonworking type code translates to schedule pay code edits by default. To override the default behavior, choose Send as Segment with Tag.1
In Dimensions regular and working time translates to a shift with segment; 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.
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. 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 display 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=NoPaySegmentTag2020Important: When using the above mentioned properties be sure to configure the Regular Duty/Working code properly. A non-working work code that does not have a matching Regular Duty or Working type work code must have a Regular Duty/Working code with Send as Segment with Tag selected in the code’s configuration to cover the time gap. This also means the work code used to define Regular Duty must have Include in Integration and Send as Segment with Tag selected, and must be the work code assigned to the List Plan associated with the position, or the work code referenced in an Overriding Assignment Work Code.
Merge Adjacent Working Period in the Dimensions Integration area is not supported when changing the default behavior of work code types.