FastTrack360 Version 12 Online Help
Important Notices and Breaking Changes V12.33
The enhancements described in the related pages below represent significant functional changes that you must be aware of prior to upgrading to this release. Some of these enhancements require specific actions before or immediately after upgrading and are therefore highlighted here for your reference. Please refer to the relevant sections of this What’s New Guide, as identified below, for detailed information about each enhancement and any configuration that is required.
Please be aware of the following important points about upgrading to this release:
Please ensure that no pay batches remain open in the Payroll module at close of business on your notified upgrade date. All pay batches must be closed before FastTrack can proceed with upgrading your environment.
New APIs
The following new APIs have been created:
Leave Balance API
API consumers may wish to be able to import payees' leave accrual and entitlement balances into FastTrack360 in bulk. This may, for example, be required where an Agency acquires another business and the payment and management of leave for the incumbent payees is required in FastTrack360.
API: PATCH/leaveBalance
API Changes
The following changes have been made to the FastTrack360 external APIs:
There has been a change to the validations for the patch/interpretedTimesheet API to allow the status of an interpreted adjustment timesheet to be changed such that the adjustment timesheet can be billed before the original timesheet or a prior adjustment timesheet for the same job order and period ending date.
The GET/interpretedTimesheets API has been enhanced to include fields for ‘payBatchId’ and ‘billBatchId’ so the method can be used to determine if the Timesheets have been paid and or billed.
The following APIs have been enhanced to support the ability to add an Additional Item where the Pay Code Type is leave that has been linked to an Absence Type to support the payment of leave. Changes include validating if the Pay Code is linked to an Absence Type and where true, checking to see if there are any clashes with Leave Requests and other Leave items being added to the Timesheet. Where there is a clash, the call is rejected and a response will advise of the clash.
The following changes APIs have been updated with the logic changes:
POST/timesheet - this sets status as 'Saved'.
POST/timesheet/adjustment - this sets status as 'Saved',
PATCH/timesheet/{id}/status/{statusId} - where a call is made to change a timesheet status to ‘Submitted’, ‘Approved’.
POST/timesheet/additional items - this provides the ability to add additional items to a timesheet prior to being Submitted.
POST/timesheet/attendance absence - this provides the ability to add attendance/absence items to a timesheet in the ‘Saved’ state.
The PATCH/timesheet/{id}/status/{statusId} has been enhanced to return an error where there is an overlap (clash) of Attendance/Absence items in the call. This validation will be triggered where the status is changed to ‘Submitted’ or ‘Approved’.
Classification-Public