FastTrack360 Version 12 Online Help

Defect Fixes V12.33

The following defects have been fixed in this release:

Item No.

Module

Description

Resolution

Item No.

Module

Description

Resolution

AV-1481

Maintenance

We created a Custom Field of a ‘Numeric' type, however where the item displayed in Recruitment Manager, users could not enter a decimal value in the numeric field.

This item has been fixed. Now where a Custom Field is configured of type ‘Numeric’, where the field displays in a Recruitment Manager record, users can enter in decimal values.

CY-705

Time & Attendance

A user was able to import a Reimbursement item for a Job Order with Agreement Rates that did not have a Reimbursement item in the Rates. When the timesheet was approved, the Reimbursement was not included in the interpreted timesheet.

This issue has been resolved. Now where importing a Reimbursement item for a Job Order with Agreement Rates the logic will check to see if the item is available in the rates. Where false the timesheet will be excepted and in the report an error will display next to the item to advise it is not available for the timesheet.

CY-3150

Payroll

When editing a Payee record an error message displayed “Postponement cannot be applied as payee is already a member of a qualifying pension scheme.” The Payee had been auto enrolled during a pay batch, and then later an eligible jobholder postponement had been applied by the system.

The validation has been updated to check to allow the postponement if a payee had an enrolment override applied and thus to allow the postponement.

CY-3189

Payroll

FPS forms were rejected where a Payee’s LEL YTD figures included decimal values.

This issue has been resolved. A validation has been added to prevent a user from entering LEL YTD figures with a decimal. Only whole pound values are accepted. The FPS form will be accepted as expected.

NE-1375

Payroll

When updating YTD figures in a payee record and you save and then you go back to the YTD screen and save again, it was removing the flag that marks the update to include in the next pay batch. If the payee did not have any other transactions the payee was not included in the next pay batch to notify HMRC of the update to their YTD figures. If the payee had other transactions, then the figures would be reported.

This issue has been resolved. If a user modifies the YTD figures and saves and then saves again, the marker to indicate if the payee is to be included in the pay batch will remain.

CY-2794

Billing

When a user tried to preview a Timesheet Based Invoice/Credit Note document format that had ‘Include a Sub Totals Row’ selected AND no Rate column, an “Oops” error displayed. The invoice also could not be emailed or printed.

This defect has been fixed. Now if a Timesheet Based Invoice/Credit Note with ‘Include a Sub Totals Row’ selected and no Rate column is generated, the item can be previewed, emailed or printed as required.

CY-865

Billing

The Address Details displayed were incorrect (from the Debtor rather than the Cost Centre) where the Debtor had the following settings:

  • Customer Type = Client

  • Data Group = Cost Centre

  • Bill To Address = From Client Cost Centre

  • Document Format uses Debtor Address database fields

This issue has been resolved. Now where a Debtor has settings for a Customer Type of Client, with a Data Group of Cost Centre, a Bill To Address from Client Cost Centre and the Document Format for the invoice has the Debtor Address fields applied, the correct address details from the Cost Centre are displayed as expected.

CY-877

Leave

In a Leave Type a Hierarchy Level filter was applied for a level other than Country, Leave Sets did not display even though there were some that met the filter value applied.

This item has been fixed. Now in a Leave Type where a Hierarchy Level/Value filter is applied, the list of relevant Leave Sets display as expected.

CY-2557

Leave

A Timesheet had an Absence Item automatically added to it from a Leave Request, where the Leave had already been processed in a pay batch.

This issue has been resolved. If a Leave Request has a payment state of ‘Processed’, and a timesheet that intersects with the leave period is opened in edit mode, the paid Leave Request will not apply to the timesheet.

 

Classification-Public