Edit Approved GTOR

The Edit Approved GTOR extension streamlines the management of time-off requests.

Note: This business process is an extension model that is developed outside the normal release schedule to meet specific customer needs. To request one of these models, you must submit a Salesforce Service Request to UKG. After the model is delivered to your tenant, you can edit it to meet your needs.

This workflow provides opportunities for the employee to

view and select approved time-off requests that fall within a specified time span.
edit the start and end dates of approved requests, including those that span multiple periods.
cancel individual days within a time-off span.
view and edit time-off requests based on the employee's assignment.

Additionally, the workflow

fully supports multiple periods in a time-off span.
requires no cancellation of the original time-off in a signed-off period thus minimizing historical corrections.

What does this extension support?

The workflow allows the employee to edit time-off requests that fall in both non-signed off and signed-off periods providing that timecard editing is enabled in signed-off periods.

If the employee chooses to add days to an approved time-off request, the system references the existing request subtype settings and then generates a new request for the additional days.

When the employee chooses to cancel days from the approved time-off, the system adheres to cancellation-specific settings defined in the request subtype. These settings include: Request Cancellation, Restore Shift Only if Open Shift is Available, and Automatically Create Open Shift.

What is the approach?

The workflow determines whether the request falls in a non-signed off or signed-off period, and then follows one of two paths – extend or cancel days.

Non-signed off periods

Extend days
- Creates a new time-off that covers the additional days in the Schedule Planner.
Cancel individual days
- Retains the original leave request.
- Removes the time-off paycode associated with the request from both the Schedule Planner and the Timecard.
- Adds a schedule tag in the Schedule Planner on the canceled days.
- Restores the shifts based on the request subtype configuration.

Signed-off periods

Extend days
- Creates a new time-off that covers the additional days in the Schedule Planner.
Cancel individual days
- Retains the original leave request.
- Adds a paycode with negative hours associated with the leave request in the Timecard.
- Adds an indicative paycode with 0 hours in the Timecard. Attaches a detailed comment and note to the indicative paycode that serves as reference for future analysis.

Considerations and limitations

If an employee needs to cancel an entire time-off request, they must rely on existing (core) GTOR functionality.
This extension supports:
- multiple assignments.
- the rerun functionality.
This extension respects the Employee Visibility Period. For example, assume that an employee initially requested leave from August 25 – August 30. Further assume that the Request Period within the Employee Visibility Period ends on September 1. If the employee attempts to extend leave from August 30 – September 5, the edit is prevented because the leave extends beyond the allowed visibility period; the system rejects the request and notifies the employee.
The Edit Approved GTOR business process must be attached to employee process profile assignments.
When the Request Cancellation option in the Request Subtype configuration is set to Disallow, the workflow permits only leave extensions. Cancellation of any part of the leave is not permitted.
Employees can edit only approved time-off requests through this workflow.
If a time off request needs to be approved at multiple levels, this workflow only supports 20 reviewers in a single step for symbolic reviewers.
If an employee cancels or modifies a leave request, the corresponding days are excluded from the form in a subsequent run.
When an employee extends leave, the workflow generates a new time-off request. This newly created request includes a comment indicating that it was generated by the workflow. During a subsequent processing cycle, it appears as a new entry in the user form.
Do not remove the
- indicative paycode that the workflow adds to the employee timecard.
- schedule tag that the workflow adds to the employee schedule.

User experience

Extend a time-off request in a non-signed off period

Employee A previously requested vacation that spans Monday – Wednesday during a particular week. The request was approved.

As the week approaches, Employee A decides to extend the vacation through Friday of the same week.

Employee A navigates to My Business Processes tile and selects Edit Approved GTOR.

When the form displays, the employee selects the approved time-off request, then selects the option to Modify Start or End Dates, and moves to the next form.

On the subsequent form, the employee selects the dates that correspond to the revised request, and then moves to the next form.

On the final form, the employee enters a comment that supports revision, and submits the request.

The reviewer, who is identified based on the approver settings in the request subtype, receives a system task to act on the request. After entering a comment in the request form, the reviewer submits the approval, and the employee receives an approval status notification.

The system creates a new time-off request.

Reduce a time-off request in a non-signed off period

Employee B takes maternity leave that spans the months of June – August.

During the final month of leave, the employee decides to return to work a week earlier than originally planned.

Employee B navigates to My Business Processes tile and selects Edit Approved GTOR.

When the form displays, the employee selects the approved request, then selects the option to Modify Start or End Dates, and moves to the next form.

On the subsequent form, the employee selects an earlier date that correspond to the revised request, and then moves to the next form.

On the final form, the employee enters a comment that supports revision, and submits the request.

No changes are made to the original leave request. Instead, the system removes the absence paycode from the schedule and adds a schedule tag on each of the cancelled days. A detailed comment accompanies the tag, and includes comments from the employee and each approver.

The employee receives an approval notification.

Cancel individual days in a request

Employee C requires non-contiguous medical leave throughout the month of July. On Wednesday and Thursday of each week, the employee attends all-day appointments.

Midway through the month, the doctor determines that the employee does not require the last week of treatment.

Employee C navigates to My Business Processes tile and selects Edit Approved GTOR.

When the form displays, the employee selects the approved request, then selects the option to Cancel Individual Dates, and moves to the next form.

On the subsequent form, the employee selects the dates that are no longer required, and then moves to the next form.

On the final form, the employee enters a comment that supports revision, and submits the request.

Extend a time-off request in a signed-off period

Employee D requires sick leave that spans Monday – Wednesday during a particular week.

On Thursday, the employee needs to extend sick leave for the remainder of the week; but cannot access the system to submit a leave request to cover the additional days. The pay period is signed off before the employee returns to work on the following Monday.

Employee D navigates to My Business Processes tile and selects Edit Approved GTOR.

When the form displays, the employee selects the approved time-off request, then selects the option to Modify Start or End Dates, and moves to the next form.

On the subsequent form, the employee selects the dates that correspond to the additional sick leave, and then moves to the next form.

On the final form, the employee enters a comment that supports revision, and submits the request.

No changes are made to the original leave request. The system creates a new time-off request for the extended days.

Note: This scenario assumes that

editing in the signed-off pay period is enabled.
the LookBackMonths value in the Parameters decision table exceeds 0.

Reduce a time-off request in a signed off period

Employee E requests personal leave that spans 3 days during a particular week. Instead of taking the entire 3 days, the employee returns to work after the second day of leave.

Two weeks later, after the period was signed off, the employee realizes that they forgot to cancel the third day of personal leave.

Employee E navigates to My Business Processes tile and selects Edit Approved GTOR.

When the form displays, the employee selects the approved request, then selects the option to Cancel Individual Dates, and moves to the next form.

On the subsequent form, the employee selects the date that was not taken, and then moves to the next form.

On the final form, the employee enters a comment that supports revision, and submits the request.

No changes are made to the original leave request nor the schedule. The system adds a personal leave paycode with negative hours in the timecard. It also adds an indicative paycode with 0 hours in the timecard. A detailed comment and note accompany the indicative paycode and serve as reference for future analysis.

Note: This scenario assumes that

editing in the signed-off pay period is enabled.
the LookBackMonths value in the Parameters decision table exceeds 0.
the indicative paycode is hidden from the timecard.

Before you start

Before you configure this business process, you must configure the following:

System Settings: System setting site.timekeeping.allowRequestsInSignedOffPeriod must be set as true. See theTimekeeping System Settings topic.
Comments: Create a comment, such as Adjusted by Workflow, that tracks and identifies workflow-driven adjustments to employee time-off requests. Select Paycodes, Shifts, and Requests Categories during configuration. See the Comments topic.
Reviewer Lists: Create a reviewer list with a Scheduling Request Type. See the Reviewer Lists topic.
Note:
- Only one reviewer is configured at each step. Do not repeat the same reviewer on multiple steps.
- Assign the Reviewer List to the employee in People Information under Timekeeping > Approvals & Reviewers.
Paycodes: Create multiple paycodes dedicated to the Edit Approved GTOR extension. See the Paycode definition topic.

The workflow adds one of the paycodes paycode to the Timecard to indicate that the employee canceled leave during a signed-off period.

Define this paycode as a standard hours type. Additionally, define this paycode as nonproductive schedule hours type. We recommend that this paycode be defined as hidden. Example:

Time Off Adjustment

The workflow needs two additional standard paycodes that it uses as placeholders to free up the accrual balance until the time-off is successfully edited.

Define one paycode as an hour type and the other as a day type. Example:

TemporaryHour

TemporaryDay
Tag Definition: Create a Schedule type tag that the workflow adds to the schedule when the employee cancels leave before the timecard is signed-off. See the Tag definition topic. Example:

TIme Off Adjustment
Workflow Notifications: Create two workflow notifications that initiate either when the employee modifies an approved time-off request or an error occurs during processing. Examples:

Name: Edit Approved GTOR Status Employee

Recipients

Workflow notifications: Create two generic workflow notifications — one for the employee and the second for the administrator. During the configuration of each notification, select Do not suppress duplicates in the Suppress Duplicate Alerts section. See the Configure Notifications for Business Processes topic. Examples include:

Name: Edit Approved GTOR Status Employee Notification

Select Send to employee in the Recipients section.

Short Message: Request to edit the Time Off Request <Status>

Long Message:

Time Off Request:

<CurrentAssignmentName>

<RequestSubtype>

Original Time Off Request: <OriginalTimeOffRequest>

Updated Time Off Request: <UpdatedTimeOffRequest>

Employee Comment: <EmployeeComment>

Reviewer Comments: <ReviewerComment>

Name: Edit Approved GTOR Error Notification

Select Recipient List will be supplied at runtime and Send to employee in the Recipients section.

Long Message: <ErrorValidationMessage>

Note: Notifications are automatically generated as system messages. System messages must be part of the employee and manager Control Center Profile.

Custom tags

Variable definitions

Tag name	Description
`<CurrentAssignment>`	Assignment for which time off was applied.
`<RequestSubtype>`	Request subtype for which time off was applied.
`<OriginalTimeOffRequest>`	Original time off duration.
`<UpdatedTimeOffRequest>`	Updated time off duration
`<Status>`	Request status — Approved or Rejected.
`<EmployeeComment>`	Comment entered by the employee.
`<ReviewerComment>`	Comment entered by the reviewer.
`<ErrorValidationMessage>`	Error message captured during processing.

Configure the Edit Approved GTOR business process model

Note: The process for configuring and deploying this and other Business Process Extensions is the same as all .

Migrate the Edit Approved GTOR business process model to the customer tenant.
1. Log in to the appropriate tenant.
2. Go to Main Menu > Administration > Setup Data Manager.
3. Select the Source tenant where the Process Model resides, and select the template to copy. It is a .zip file. A message appears in the Source column: Source: Import from <filename>.zip.
4. Click Tap Review and Publish. The Publish Summary panel appears.
5. Review the Publish Summary panel. It lists the items that were extracted from the migration file. If you approve, click tap Publish with Comment or just Publish.
6. Click Tap Go to Publish History at the bottom of the panel to view the status of the data transfer. The Publish History page contains a table that lists the items you have published. If there were errors during the transfer, the button under the Errors column for that row is black.
7. To view details, click tap the appropriate row and click tap View Selected.
8. On the History for publish run page, click tap Show all to view the setup data that you published, and the errors that occurred, if any, listed by item type and name.

Configure the Edit Approved GTOR decision tables.

Note: Decision tables are configurable based on user requirements and can be changed accordingly. These tables are dynamic and can be updated at any time without redeployment of the process model.

Go to Main Menu > Administration > Application Setup > Business Process setup > Process Models.
Select the EditApprovedGTOR_v1 process and click Edit. The process model enters edit mode.
Select the Decision Tables tab.
Click Everyone's, and then select the decision table to edit.
Click Decision Table Editor to add or update the rows in the table.

Click Save and close.

Caution:

Values entered in the decision tables are case-sensitive, and must match configured values in the application.
Do not remove variables, variable names, or variable types from any decision table.

Edit the following decision tables:

EditApprovedGTOR_v1_InternalParameters — Controls internal Edit Approved GTOR configuration variables that optimize workflow system performance. The default values are pre-configured.

Edit Approved GTOR — Internal Parameters decision table structure

Parameter name	Description	Default value
Admin	Account that makes API calls.	SERVICE-LEVEL3
ApprovedTORStatus	Symbolic value that identifies the approved time-off request.	APPROVED
ActivitiFormDateFormat	Activiti date format.	MM/dd/yyyy
AddedDelayInSec	Delay time in seconds before the workflow adds paycodes to the Timecard.	2

EditApprovedGTOR_v1_Parameters — Allows configuration of the parameters used in the workflow. The default values are pre-configured.

Edit Approved GTOR — Parameters decision table structure

Parameter name	Description	Default value
NoOfLeaveDaysDisplayed	Controls the number of days that display when the employee chooses to cancel individual dates in a time-off request.	15
EnabledMultipleAssignment	Determines whether the assignment displays with time-off request details. Note: This parameter assumes that Multiple Assignments is enabled on the tenant.	true
LookBackMonths	Determines the number of months prior to the current date that display on the form.	0
LookForwardMonths	Determines the number of months beyond the current date that display on the form.	6
TORAdjustmentComment	The comment that the workflow adds to the schedule tag and indicative paycode. A note attached to this comment contains the request ID and employee comment.	Adjusted by Workflow
TORAdjustmentScheduleTag	The schedule tag that the workflow adds to the schedule when the employee cancels leave before the timecard is signed-off.	Time Off Adjustment
IndicativePaycode	The paycode that the workflow adds to the timecard when the employee cancels leave in a signed-off period.	Time Off Adjustment
TemporaryPlaceHolderPaycodeDay	Day type paycode that the workflow uses as a placeholder to free up the accrual balance until the time-off is successfully edited.	Temp_Day
TemporaryPlaceHolderPaycodeHour	Hour type paycode that the workflow uses as a placeholder to free up the accrual balance until the time-off is successfully edited.	Temp_Hour
ErrorWorkflowNotification	Workflow notification that the process sends to the administrator and employee when an error occurs.	Edit Approved GTOR Error Notification
StatusToEmployeeWorkflowNotification	Workflow notification that the process sends to the employee.	Edit Approved GTOR Status Employee Notification

EditApprovedGTOR_v1_ReviewerList — The workflow references this table when the request subtype is configured to use approval settings.

Edit Approved GTOR — Reviwer List decision table structure

Parameter name	Description	Default value
Approval Setting	Contains the approval setting defined in the request subtype.
Reviewer List	Identifies the default approval sequence associated with the approval setting.

Note:

The Approval Setting and Default Approval Sequence of the associated Reviewer Lists must match the values in the Request Subtype. Both are case sensitive.
When an employee extends their leave, the system generates a new leave request to ensure that all configurations associated with the request subtype are properly applied. In contrast, when a leave is canceled — even if it was previously extended — the system follows the cancellation-specific settings defined for that subtype. These settings include:
- Request Cancellation
- Restore Shift Only if Open Shift is Available

EditApprovedGTOR_v1_Locale — Contains configurable labels and messages to support the Edit Approved GTOR extension.

Edit Approved GTOR — Locale decision table structure

Variable name	Variable type	Description
Key	String	Internal field label; do not change.
Locale Policy	String	Name of the locale policy for which the label applies. When the label applies to all locales, retain the empty value.
Message	String	Label displayed in the Workflow form, or error message.
Description	String	(Optional) Additional information.

Note:

Localization of business process workflows remains optional, but is supported.
You can translate some or all messages by adding lines to the table in their preferred translation for specific locales. Decision tables are scanned from top to bottom; therefore, place messages for the most commonly used Locale Policy at the top of the decision table and less-restrictive locale policies at the bottom.
Text within tags ("<>") must not be changed.
The decision table holds all messages represented with standard English labels; these apply to all locales when the Locale Policy is set to !=empty.
Names of the parameters in the decision table column Parameter Name must be used as is. If any parameter value needs to be localized for a different Locale Policy, copy the Parameter Name with the !=empty Locale Policy, add a new row to the decision table with the appropriate Locale Policy, and then add the localized value in the Message column.
Decision tables support operators like "Contains," "Starts with," "Ends with," and "Is Not Empty." You can achieve your preferred results by following these examples:
- To match any non-empty or any string (like *), use the "Is Not Empty" operator.
- To match a string starting with "ABC" (like "ABC*"), use the "Starts with" operator and set the value to "ABC".
- To match a string containing "English" as substring, use the "Contains" operator with the value "English".

Key	Locale Policy	Message	Description
Error_Generic	!= empty	Workflow encountered an error.	Message for error notification sent to the user.
Error_InvalidComment	!= empty	Comment is invalid or not provided.	Error message for invalid comment.
Error_InvalidIndicativePaycode	!= empty	Indicative Paycode is invalid or not provided.	Error message for invalid indicative pay code.
Error_InvalidScheduleTag	!= empty	ScheduleTag is invalid or not provided.	Error message for invalid schedule tag.
Error_SystemAdministrator	!= empty	Please contact your system administrator.	Message for error notification sent to the user.
Error_TemporaryPaycodeIsNull	!= empty	Temporary Placeholder Paycode is not provided.	Error message when temporary pay code is not provided or is invalid.
Label_assignmentMessage	!= empty	Assignment	Label for assignment information.
Label_Cancel_summaryMessage	!= empty	Time-off request for the following days will be cancelled.	Message related to time-off request status or details.
Label_CancelEmployeeFormMessage	!= empty	Following selected days will be cancelled.	Message used in the time-off request interface.
Label_CancelIndividualDates	!= empty	Cancel Individual Dates	Option to cancel specific dates within a time-off request.
Label_commentmessage	!= empty	Comment	Label for entering a comment.
Label_CommentRequestIdText	!= empty	Request ID	Label for displaying the request ID.
Label_CustomDateRangeMessage	!= empty	Select the new date range.	Prompt for users to select a new range of dates.
Label_DateInvalidFormat	!= empty	Invalid date format. Please check the input dates.	Error message for incorrect date format.
Label_DateNotNull	!= empty	Start date or End date cannot be null.	Error message when either start or end date is missing.
Label_DateOutOfRange	!= empty	Selected Date is out of Range	Prompt for user when they select a date range to cancel within a time-off request and that range is falls outside the original time-off.
Label_DateRangeSeperator	!= empty	to	Message used in the time-off request interface.
Label_DatesMessage	!= empty	Dates	Message related to date selection or validation.
Label_durationMessage	!= empty	Duration	Label for the duration of the time-off request.
Label_EmployeeCommentText	!= empty	Employee Comment	Field or message related to user comments.
Label_EndDateMessage	!= empty	End Date	Label for selecting the end date of a time-off request.
Label_ExceedsOneYearMessage	!= empty	Date Range is more than 1 year. Please select a valid date range	Message related to date selection or validation.
Label_FullDayMessage	!= empty	FULL	Message used in the time-off request interface.
Label_gobackmessage	!= empty	Go Back	Label for the button to return to the previous step.
Label_GreaterEndDate	!= empty	End date must be greater than Start date.	Error message when the end date is earlier than start date.
Label_ListSymbol	!= empty	\u2022	Bullet point symbol.
Label_ManagerFormButton	!= empty	Submit	Label or button for submitting a form or request.
Label_ManagerFormCancelOptionMessage	!= empty	Employee requested to cancel following days	Message used in the time-off request interface.
Label_ManagerFormDisplayMessage	!= empty	Please review the below modified Time-off request	Message related to time-off request status or details.
Label_ManagerFormEmployeeComment	!= empty	Employee Comment	Label for Employee Comment
Label_ManagerFormModifiedDurationMessage	!= empty	Updated Time-Off:	Message used in the time-off request interface.
Label_ManagerFormNotesHeader	!= empty	Approver comment	Option for approving or rejecting a request.
Label_ManagerFormOrignalDurationMessage	!= empty	Original Approved Time-Off:	Option for approving or rejecting a request.
Label_ManagerFormRadioOptionApproved	!= empty	Approve	Option for approving a request.
Label_ManagerFormRadioOptionHeader	!= empty	Action	Label for action.
Label_ManagerFormRadioOptionRefuse	!= empty	Reject	Option for rejecting a request.
Label_ManagerFormReviewerComment	!= empty	Reviewer Comment	Label for Reviewer Comment
Label_MergeandModifyDates	!= empty	Merge or Modify Dates	Message related to date selection or validation.
Label_ModifyStartEndDate	!= empty	Modify Start or End Dates	Prompt to change the selected date range.
Label_NextMessage	!= empty	Next	Label for the button to proceed to the next step.
Label_noApprovedLeaveMessage	!= empty	No approved time-off requests found from <startDate> to <endDate>. Choose a new date range.	Message shown when no approved time-off requests are found for the given range.
Label_noApprovedLeaveMessageForCurrentDate	!= empty	No approved time-off requests found for <startDate>. Choose a new date range.	Message shown when no approved time-off requests are found for the current date.
Label_PayCodeMessage	!= empty	Pay Code	Message used in the time-off request interface.
Label_refinedateMessage	!= empty	This request covers a range of more than <days> days. Please refine your search to the specific range you want to cancel.	Message prompting user to refine the date range if it exceeds a certain number of days.
Label_RemaningDates	!= empty	Remaining Days	Label for remaining days in a request.
Label_RequestMessage	!= empty	Time-off	Message related to time-off request status or details.
Label_RequestPeriod	!= empty	Period : <Number>	Message used in the time-off request interface.
Label_RequestSubtypeMessage	!= empty	Request Subtype	Message used in the time-off request interface.
Label_rerunDateRangeMessage	!= empty	No Time-off Request Found for Previous Selected Date Range Please Choose a new date range.	Message shown when no time-off requests are found for the selected date range.
Label_selectcancelDatesMessage	!= empty	Select Days to Cancel	Prompt to select specific days to cancel.
Label_Selectoptionmessage	!= empty	Select Option	Prompt selecting an option from available choices.
Label_SelectRadioButtonOption	!= empty	Please Select Option	Prompt for users to select.
Label_SelectRequestMessage	!= empty	Select	Prompt for user to make a selection.
Label_StartDateMessage	!= empty	Start Date	Label for selecting the start date of a time-off request.
Label_StaticWeekMessage	!= empty	WEEK	Label for week display.
Label_SubmitMessage	!= empty	Submit	Submit button
Label_SummaryMessage	!= empty	Summary	Label for summary section.
Label_TimeOff	!= empty	Request <Number>	Message used in the time-off request interface.
Label_TORListMessage	!= empty	Approved Time-off Requests from <startdate> to <enddate>	Header showing approved time-off requests for a specific date range.
Label_TORListMessageForCurrentDate	!= empty	Approved Time-off Requests for <startdate>	Header showing approved time-off requests for a specific day.
Message_EditRequestNotAllowed	!= empty	Request for Cancellation of Leave could not be processed as request subtype does not allow cancellation.	Message for error notification sent to the user when he tries to cancel a leave for which cancellation is not allowed.
Message_EntireTimeoffCancelled	!= empty	This was an edit request for cancelling Single Day Time-Off.	Message used in the time-off request interface.
Message_ErrorStatus	!= empty	Error	Error message displayed to the user.
Message_RequestApproved	!= empty	Approved	Option for approving or rejecting a request.
Message_RequestFailed	!= empty	Failed	Message used in the time-off request interface.
Message_RequestRejected	!= empty	Rejected	Option for approving or rejecting a request.

Deploy the updated Edit Approved GTOR business process model
Note: Process models must be redeployed every time changes are made to an existing model. Re-deployment is not required for decision table changes.
1. Go to Main Menu > Administration > Application Setup > Business Process setup > Process Models.
2. Select the EditApprovedGTOR_v1 model and click Deploy.
3. On the Business Process page, configure the required parameters and deployment dates.
  - (Optional) In Description, enter EditApprovedGTOR_v1.
  - In Display Name, enter EditApprovedGTOR_v1.
  - In Start Effective, select the effective start date.
  - In End Effective, select Forever to make the Business Process available indefinitely.
  - In Status, select Active.
  - In Action List, select Hide.
  - In Tile List, select Show.
  - In GoTo List, select Hide.
  - Do not make a selection from Template Categories.
4. Click Save and then Return.

APIs

API name	Type	Resource path	Description
GET Person Extension	GET	/v1/commons/persons/extensions?person_number=	Retrieve person extensions using a person number.
Get Tenant Default Locale to get Date Format	GET	v1/commons/user_preferences/locale_policy?tenantDefault=true	Retrieve user preferences for the current user's locale policy.
Get the Locale Details for Date Format using Retrieve Locales	POST	/v1/commons/locale_policies/multi_read	Retrieves the date format used by tenant locale.
Retrieve Time Off Requests as Manager	POST	/v1/scheduling/timeoff/multi_read	Retrieves time-off requests as a manager.
Retrieve timecards as a manager.	POST	/v1/timekeeping/timecard/multi_read	Allows managers to retrieve timecard data for multiple employees.
Create Time Off Request as Manager	POST	/v1/scheduling/timeoff	Create new time-off request when employee wants to extend a leave request.
Get Step Wise Reviewer	POST	v1/commons/reviewer_lists/reviewers/apply_read	Fetch all the reviewer at a particular step in the reviewer list.
Schedule Audit	POST	/v1/scheduling/audits/multi_read	Fetch the shift and open shift details. This restores the open shifts when an employee cancels leave.
Get Reviewer List	GET	/v1/commons/reviewer_lists?name="+encodeURI(reviewerListName)	Fetch the reviewer list details.
Get Request Subtype Configurations	GET	/v1/scheduling/setup/request_subtypes?name="+encodeURI(subtype)	Fetch the request subtype details.
Create Schedule Tag	POST	/v1/scheduling/schedule/schedule_tags/multi_create	Create schedule tag.
Update Shift by ID	POST	/v1/scheduling/schedule/shifts/{shiftID}	Update shift using the shift ID.
Update Schedule Paycode Edit	POST	v1/scheduling/schedule/pay_code_edits/multi_update	Update the schedule Paycode edit.
Retrieve Timecard as Manager	POST	v1/timekeeping/timecard	Fetch timecard details.
Delete Schedule Pay Code Edits	POST	v1/scheduling/schedule/pay_code_edits/multi_delete	Delete schedule paycode edits.

Version history

Version	Description
1.0	Initial release.