Workflow Business Process Field Descriptions

Approve a Work Code Request

To show a notification’s parameter fields:

Select the desired Business Process in the Business Process area.
Select the desired Workflow Setting to enable the Edit button.
Click Edit to show the Parameters page for the selected workflow.

>>> IMPORTANT <<<
Whether a work code requires approval is determined by the configuration of the work code in Setup > Codes. Additionally, Notification Groups and Notification Group Assignments must be configured to tell the system who or which group of people to notify.

The Approve a Work Code Request business process controls whether notifications are sent to a group of people. When Notices are activated, a work code requiring approval will automatically send a notification to a group of people for approval.

Field Name	Approve a Work Code Request Field Descriptions
Legacy	Keeps the previous work code work flow the same. This is the default setting.
Notices	Turns approval notifications ON when active for all work code types.

Field Name	Approve a Work Code Request Notification Parameter Field Descriptions
Approval Expiration Date Offset	Controls when the work code approval status expires and the approval setting disables. This setting is applicable when the work code has been configured to require approval. For example: 0 zero means the approval expires on the TARGET date. This means midnight of the calendar date. -2 negative two means the approval setting expires two days before the TARGET date. For example, suppose the work code is Vacation for 06/15/2016, -2 means expire on 06/13/2016@00:00:00. 2 two means the approval setting expires two days after the TARGET date. For example, suppose the work code is Vacation for 06/15/2016, 2 means expire on 06/17/2016@00:00:00.
Approval Reminder Frequency	Controls the frequency of the notification and applicable when the work code has been configured to require approval. Simply put, how often do you want to alert the approver or approvers of the request? This applies across all work codes so all work codes carry the same frequency. Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 two means send initial notification once and remind every two days after the initial notification has been sent. The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3 PM then the next notification will be two days later around 3 PM.

Field Name

Approve a Work Code Request Notification Parameter Field Descriptions

Approval Expiration Date Offset

Controls when the work code approval status expires and the approval setting disables. This setting is applicable when the work code has been configured to require approval. For example:

0 zero means the approval expires on the TARGET date. This means midnight of the calendar date.
-2 negative two means the approval setting expires two days before the TARGET date. For example, suppose the work code is Vacation for 06/15/2016, -2 means expire on 06/13/2016@00:00:00.
2 two means the approval setting expires two days after the TARGET date. For example, suppose the work code is Vacation for 06/15/2016, 2 means expire on 06/17/2016@00:00:00.

Approval Reminder Frequency

Controls the frequency of the notification and applicable when the work code has been configured to require approval. Simply put, how often do you want to alert the approver or approvers of the request? This applies across all work codes so all work codes carry the same frequency. Send a reminder every X days.

0 zero means send initial notification once and don’t remind again.
2 two means send initial notification once and remind every two days after the initial notification has been sent. The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3 PM then the next notification will be two days later around 3 PM.

Work Code Trade

The Work Code Trade business process gives employees the ability to confirm shift trade transactions amongst each other. If an approval is needed, acknowledging the trade transaction only tells the Approver that both employees are aware and in agreement of the shift trade. Acknowledging a trade is not an approval.

Field Name	Work Code Trade Field Descriptions
Legacy	Keeps the previous Cover work code workflow the same - this means the trade acknowledgment feature is not available. This is the default setting.
Acknowledgments	Turns notifications and shift trade acknowledgments ON when active.

Field Name	Work Code Trade Notification Parameter Field Descriptions
Approval Expiration Date Offset	Controls when the Cover work code approval status expires and the approval setting disables relative to the target date. This setting is applicable when the work code has been configured to require approval. For example: 0 zero means the approval setting expires on the TARGET date. This means midnight of the calendar date. -2 negative two means the approval setting expires two days before the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, -2 means expire on 06/13/2016@00:00:00. 2 two means the notification expires 2 days after the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, 2 means expire on 06/17/2016@00:00:00.
Approval Reminder Frequency	Controls the frequency of the notification and applicable when the work code has been configured to require approval. This applies across all Cover type work codes so all Cover type work codes carry the same frequency. Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 means sends initial notification once and remind every two days after the initial notification has been sent. The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3 PM then the next notification will be two days later around 3 PM.
Acknowledgment Expiration Date Offset	Controls when the Accept Trade/Reject Trade status expires and the acknowledgment setting is no longer available. For example: 0 zero means the acknowledgment setting expires on the TARGET date. This means if the position starts at 08:00:00 AM on 07/12/2016 then the acknowledgment link disables on the calendar date of 07/12/2016@00:00:00 not 7/12/2016@08:00:00. -2 negative two means the acknowledgment setting expires 2 days before the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, -2 means expire on 06/13/2016@00:00:00. 2 means the acknowledgment setting expires 2 days after the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, 2 means expire on 06/17/2016@00:00:00.
Acknowledgment Reminder Frequency	Controls the frequency of the reminder. Essentially, how often do you want to alert the person of this trade? Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 two means sends initial notification once and remind every 2 days after the initial notification has been sent. The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3pm then the next notification will be two days later around 3pm.

Work Code Trade Cancellation

This is used to give employees the ability to confirm shift trade cancellations amongst each other. If an approval is needed, acknowledging the trade cancellation tells the Approver that both employees are aware and in agreement of the shift trade cancellation. Acknowledging a trade cancellation is not an approval.This is used to give employees the ability to confirm the cancellation of a shift trade. Moreover, a shift trade work code that requires an Approver to approve the code will also require an Approver to approve the cancellation.

Field Name	Work Code Trade Cancellation Field Descriptions
Legacy	Keeps the previous Cover work code work flow the same - this means the cancellation feature is not available. This is the default setting.
Acknowledgments	Turns notifications and the shift trade cancellation feature ON when active.
Acknowledgment Expiration Date Offset	Controls when the cancellation acknowledgment status expires and the Trade Accept/Reject Cancellation settings are no longer available. For example: 0 zero means the cancellation acknowledgment setting expires on the TARGET date. This means if the position starts at 08:00:00 AM on 07/12/2016 then the cancellation acknowledgment settings are no longer available on the calendar date of 07/12/2016@00:00:00 not 7/12/2016@08:00:00. -2 negative two means the cancellation acknowledgment setting expires 2 days before the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, -2 means expire on 06/13/2016@00:00:00. 2 two means the cancellation acknowledgment setting expires 2 days after the TARGET date. For example, suppose the work code is Trade-Off for 06/15/2016, 2 means expire on 06/17/2016@00:00:00.
Acknowledgment Reminder Frequency	Controls the frequency of the reminder. Essentially, how often do you want to alert the person of this trade cancellation? Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 two means send the initial notification once and remind every 2 days after the initial notification has been sent. The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3pm then the next notification will be two days later around 3pm.

Field Name	Work Code Trade Cancellation Notification Parameter Field Descriptions
Approval Expiration Date Offset	Controls when the work code approval notification will expire relative to the target date. This setting is applicable when the work code has been configured to require approval. For example: 0 zero means the notification expires on the TARGET date. This means midnight of the calendar date. -2 negative two means the notification expires 2 days before the TARGET date. For example, if the target date on the calendar or the Roster associated with the work code such as Vacation for 06/15/2016, -2 means expire on 06/13/2016. 2 two means the notification expires 2 days after the TARGET date. For example, if the target date on the calendar or the Roster associated with the work code such as Vacation for 06/15/2016, 2 means expire on 06/17/2016.
Approval Reminder Frequency	Controls the frequency of the notification and applicable when the work code has been configured to require approval. Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 two means send the initial notification once and remind every two days after the initial notification has been sent.
Acknowledgment Expiration Date Offset	Controls when the Cancellation Acknowledgment setting will disable relative to the target date. For example: 0 zero means the acknowledgment expires on the TARGET date. This means if the position starts at 08:00:00 AM on 07/12/2016, the cancellation acknowledgment link disables on the calendar date, which is 00:00:00 on 7/12/2016 not 08:00:00. -2 negative two means the notification expires two days before the TARGET date. For example, if the target date on the calendar or the Roster associated with the work code such as Vacation for 06/15/2016, -2 means expire on 06/13/2016. 2 two means the notification expires 2 days after the TARGET date. For example, if the target date on the calendar or the Roster associated with the work code such as Vacation for 06/15/2016, 2 means expire on 06/17/2016.
Acknowledgment Reminder Frequency	Controls the frequency of the reminder. Essentially, how often do you want to alert the person of this trade cancellation? Send a reminder every X days. 0 zero means send initial notification once and don’t remind again. 2 two means send the initial notification once and remind every two days after the initial notification has been sent.The frequency is relative to when the initial notification request was received by the workflow engine. So if the system receives the initial notification at 3pm then the next notification will be two days later around 3pm.

Note:

A cancellation can only be processed by the last two people who committed the trade. For example, suppose John trades with Ron and that trade is approved. Ron then trades that same day with Les and that trade is approved. John then decides he no longer needs the trade in effect and wants to cancel the trade, but John cannot cancel the trade because the trade is now between Ron and Les. However, Ron and Les can cancel and if they do, the trade goes into its previous state which was John and Ron, so from this point John may send a trade cancellation request.