The following defects have been fixed in this release:
Item No. | Release | Module | Description | Resolution |
|---|---|---|---|---|
CY-3115 | 12.23 | Billing | The Base Salary value from the corresponding permanent Job Order was being included in the calculation of a Generation 3 AOG Billing Fee for perm/service invoices and credit notes despite. This was incorrect because the Generation 3 calculation must be exclusive of any pay amounts. | If a Generation 3 AOG Billing Fee is applied to a perm/service invoice or credit note, the Base Salary from the corresponding permanent job order is no longer included in the calculation of the Billing Fee. |
CY-28882979 | 12.23 | Billing | If an invoice with a Generation 3 AOG Billing Fee was rebilled using the Credit/Rebill process, the resulting credit note was correct but the billing fee on the rebilled invoice was calculated with the pre Generation 3 billing fee formula. | Now where a Credit/Rebill is actioned on an invoice with a Generation 3 AOG Billing Fee, the rebilled invoice will be calculated using the Generation 3 billing fee formula was expected. |
TR-4924 | Billing | When using the Credit/Rebill process to create a rebill invoice, billing fees were calculated for reimbursement items on the rebill invoice. | Billing fees are no longer applied to reimbursement items when a rebill invoice is generated via the Credit/Rebill process. | |
CY-2979 | Billing | Changes were made in V12.22 to exclude Adjustment Timesheets from an invoice batch where they are included in an open credit rebill batch. However Timesheets were also excluded from an invoice batch where they were not in an open credit rebill batch, or the original timesheet was included in a credit rebill batch, even though the batch had been closed. | Now Adjustment Timesheets are only excluded from an invoice batch where they are in an open credit rebill batch. If the original timesheet was in a closed credit rebill batch, the related Adjustment Timesheet will be included in the invoice batch as long as it is not in an open credit rebill batch. | |
CY-1912 | Billing | In the Debtor record where a Bill To Contact is selected, their name was defaulted as a Delivery Contact. If the Bill To Contact was then subsequently changed, the new Bill To Contact was not defaulting as the Delivery Contact. | Now where a new Bill To Contact is selected in a Debtor record, the new contact is automatically defaulted as a Delivery Contact. | |
CY-2769 | Billing | When a user attempted to email a large number of invoices, the “Email Invoice to Debtors” screen displayed with a message showing “No records found.” | This has been resolved. Now where a large number of invoices is selected in the Manage Delivery process, in the Email Invoice to Debtors screen, the relevant invoices are listed. | |
CY-2580 | Billing | The Billing Sales Report by Debtor was timing out on occasion. | The Sales Report by Debtor has been reviewed and optimised to improve the report’s efficiency so the report will run and load as expected. | |
CY-2220 | Billing | When a Credit Rebill batch was opened in multiple tabs (same or different users), users were able to create multiple rebill Credit Notes. | Now where a Credit Rebill batch is open in multiple tabs and multiple users are attempting to make changes, a hard warning will display 'Multiple users are making changes within the current Credit Rebill and your attempted changes have conflicted. Please close the current screen and notify the other user of the conflict so you may apply the required changes.' | |
CY-2212 | Billing | A user was able to create a Purchase Order with a duplicate PO number. When this occurred the debtor record could no longer be edited, displaying the message ‘The following PO numbers are currently existing in system and could not be added: DuplicatePONo, DuplicatePONo.’ | This problem has been fixed. Now where a user attempts to change a Purchase Order number to the same number as an existing Purchase Order, a hard warning will display ‘PO Purchase Order No. must be unique. <<PONumber>> is already used by another PO.’ | |
CY-2158 | Billing | In the Manage Delivery screen a search was run to retrieve invoices that have Delivery Method ‘No Send’ and Delivery Status ‘No’. When a large number of invoices were returned in the results and a user clicked the ‘Set Delivered Flag’ action, the delivered flag is not set. | This issue has been fixed. In the Manage Delivery screen where a large number of invoices that have Delivery Method ‘No Send’ and Delivery Status ‘No’ are selected and the ‘Set Delivered Flag' is selected, the flag is set as expected. | |
CY-2246 | Job | In a Job Order with a Service Fee scheduled for ‘Auto Invoice’, the item was then flagged as ‘Ready For Invoice’ and the invoice was subsequently raised. A user was then able to select the ‘Clear Auto Invoice Creation’ date. | Now where a user adds a Service Fee for ‘Auto Invoice' then the invoice is generated via the Raise Invoice action, if the user selects the ‘Clear Auto Invoice Creation Date’ action, a hard warning will display ‘Unable to clear the creation date as one or more invoices have already been generated.’ | |
CY-662 | Job | In a Referral Workflow for a Stage that is set for automated email, the automation email was not sending at the time the Candidate is moved to the stage (Candidate has not been moved to the stage previously). Secondly an automation email was sent on a date that was different to when the Candidate was moved to the stage with Automation. | These problems have been fixed. Now where a Candidate assigned to a referral workflow is moved to a stage with automation for the first time, the email is generated and dispatched on the date the stage was applied as expected. | |
CY-1965 | Leave | When editing a Leave Rate Type, the Pay Codes listed for selection in the pop up were not correct if the selected Country is not the default. This affected Leave Rate Types with a Type of Average Rate or Greatest Rate. For example, if the default country is Australia and there are pay codes that belong to the countries of Australia and New Zealand respectively, when editing a Leave Rate Type that belongs to New Zealand the pay codes that were available for selection showed those assigned to Australia. | This bug has been fixed. Now when editing Pay Codes for a Leave Rate Type for Average Rate or Greatest Rate, the Pay Codes available will be as per the Country of the Leave Rate Type. | |
CY-884 | Maintenance | In the Global Maintenance item for Communication History, there was no Pending status for SMS Medium Type. This was in the V11 product. | Now the Pending Status option is available as a filter for SMS Medium Type communications in the Global Maintenance item for Communication History. | |
CY-2239 | Maintenance | The customer address for a Debtor at the Cost Centre or Parent level for Timesheet Based invoices was displaying the wrong address on the invoices. In the Document Format tool the Address 1 items were assigned, however mailing address is displaying. | This item has been fixed. Now where the Document Format for Timesheet Based Invoices has been selected for Address 1 etc, this is the address that will apply from the Cost Centre/Parent assigned to the Debtor. Where Mailing Addresses are selected, then the related record’s mailing address will apply as expected. | |
CY-2230 | Maintenance | The Custom Action Trigger for ‘Job Order Fill’ was not working as expected as triggered where a filled job was edited as well as when it is was filled. | This issue has been resolved. Now where the Custom Action Trigger ‘Job Order Fill’ is applied, the action will only be triggered where an action to fill a job is run. | |
CY-2398 | Payroll | In a Payee Record a user was unable to save a Deduction where the ‘Apply Order’ was zero '0'. An error displayed “Deductions: Apply Order is mandatory.” | This issue has been resolved. Now where a deduction is added or edited, where the ‘Apply Order’ is zero, the deduction saves as expected without error. | |
CY-2039 | Payroll | The following issues were occurring when a Deduction Header was edited:
| These issues have been resolved. Editing of Deduction Headers now works as expected. | |
CY-958 / CY-1295 | Payroll | The following issues were affecting the Payee Payroll - Detailed Report:
| These issues how now been resolved and the Payee Payroll - Detailed Report now works as expected. | |
CY-841 | Payroll AU | Workcover Super and Salary Sacrifice Rules were being applied based on the state of the Job Order office instead of the WorkCover state that was selected in the Pay/Bill section of the Job Order. | This issue has been resolved. For pay items that are linked to a Job Order, Workcover Super and Salary Sacrifice Rules are now applied based on the WorkCover state that is selected in the Pay/Bill section of the Job Order as expected. For pay items that are not linked to a Job Order (e.g. manual pay items or adjustments), the Workcover Super and Salary Sacrifice Rules are applied based on the state to which the candidate office is linked. | |
CY-2145 | Rates & Rules | A user was able to save changes to a Bill Agreement when the Bill Rate Rule did not have a Start Date for Validity. | Now where saving changes to a Bill Agreement, the system will display a hard warning where the Validity Start Date has not been entered for the Bill Rate Rule ‘A value is required for start date.’ | |
CY-2142 | Rates & Rules | A user when editing a Bill Agreement where an existing Bill Rate Rule was Changes were made in V12.22 to exclude Adjustment Timesheets from an invoice batch where they are included in an open credit rebill batch. However Timesheets were also excluded from an invoice batch where they were not in an open credit rebill batch, or the original timesheet was included in a credit rebill batch, even though the batch had been closed. | Now Adjustment Timesheets are only excluded from an invoice batch where they are in an open credit rebill batch. If the original timesheet was in a closed credit rebill batch, the related Adjustment Timesheet will be included in the invoice batch as long as it is not in an open credit rebill batch. | |
CY-1912 | 12.23 | Billing | In the Debtor record where a Bill To Contact is selected, their name was defaulted as a Delivery Contact. If the Bill To Contact was then subsequently changed, the new Bill To Contact was not defaulting as the Delivery Contact. | Now where a new Bill To Contact is selected in a Debtor record, the new contact is automatically defaulted as a Delivery Contact. |
CY-2769 | 12.23 | Billing | When a user attempted to email a large number of invoices, the “Email Invoice to Debtors” screen displayed with a message showing “No records found.” | This has been resolved. Now where a large number of invoices is selected in the Manage Delivery process, in the Email Invoice to Debtors screen, the relevant invoices are listed. |
CY-2580 | 12.23 | Billing | The Billing Sales Report by Debtor was timing out on occasion. | The Sales Report by Debtor has been reviewed and optimised to improve the report’s efficiency so the report will run and load as expected. |
CY-2220 | 12.23 | Billing | When a Credit Rebill batch was opened in multiple tabs (same or different users), users were able to create multiple rebill Credit Notes. | Now where a Credit Rebill batch is open in multiple tabs and multiple users are attempting to make changes, a hard warning will display 'Multiple users are making changes within the current Credit Rebill and your attempted changes have conflicted. Please close the current screen and notify the other user of the conflict so you may apply the required changes.' |
CY-2212 | 12.23 | Billing | A user was able to create a Purchase Order with a duplicate PO number. When this occurred the debtor record could no longer be edited, displaying the message ‘The following PO numbers are currently existing in system and could not be added: DuplicatePONo, DuplicatePONo.’ | This problem has been fixed. Now where a user attempts to change a Purchase Order number to the same number as an existing Purchase Order, a hard warning will display ‘PO Purchase Order No. must be unique. <<PONumber>> is already used by another PO.’ |
CY-2158 | 12.23 | Billing | In the Manage Delivery screen a search was run to retrieve invoices that have Delivery Method ‘No Send’ and Delivery Status ‘No’. When a large number of invoices were returned in the results and a user clicked the ‘Set Delivered Flag’ action, the delivered flag is not set. | This issue has been fixed. In the Manage Delivery screen where a large number of invoices that have Delivery Method ‘No Send’ and Delivery Status ‘No’ are selected and the ‘Set Delivered Flag' is selected, the flag is set as expected. |
CY-2246 | 12.23 | Job | In a Job Order with a Service Fee scheduled for ‘Auto Invoice’, the item was then flagged as ‘Ready For Invoice’ and the invoice was subsequently raised. A user was then able to select the ‘Clear Auto Invoice Creation’ date. | Now where a user adds a Service Fee for ‘Auto Invoice' then the invoice is generated via the Raise Invoice action, if the user selects the ‘Clear Auto Invoice Creation Date’ action, a hard warning will display ‘Unable to clear the creation date as one or more invoices have already been generated.’ |
CY-662 | 12.23 | Job | In a Referral Workflow for a Stage that is set for automated email, the automation email was not sending at the time the Candidate is moved to the stage (Candidate has not been moved to the stage previously). Secondly an automation email was sent on a date that was different to when the Candidate was moved to the stage with Automation. | These problems have been fixed. Now where a Candidate assigned to a referral workflow is moved to a stage with automation for the first time, the email is generated and dispatched on the date the stage was applied as expected. |
CY-1965 | 12.23 | Leave | When editing a Leave Rate Type, the Pay Codes listed for selection in the pop up were not correct if the selected Country is not the default. This affected Leave Rate Types with a Type of Average Rate or Greatest Rate. For example, if the default country is Australia and there are pay codes that belong to the countries of Australia and New Zealand respectively, when editing a Leave Rate Type that belongs to New Zealand the pay codes that were available for selection showed those assigned to Australia. | This bug has been fixed. Now when editing Pay Codes for a Leave Rate Type for Average Rate or Greatest Rate, the Pay Codes available will be as per the Country of the Leave Rate Type. |
CY-884 | 12.23 | Maintenance | In the Global Maintenance item for Communication History, there was no Pending status for SMS Medium Type. This was in the V11 product. | Now the Pending Status option is available as a filter for SMS Medium Type communications in the Global Maintenance item for Communication History. |
CY-2239 | 12.23 | Maintenance | The customer address for a Debtor at the Cost Centre or Parent level for Timesheet Based invoices was displaying the wrong address on the invoices. In the Document Format tool the Address 1 items were assigned, however mailing address is displaying. | This item has been fixed. Now where the Document Format for Timesheet Based Invoices has been selected for Address 1 etc, this is the address that will apply from the Cost Centre/Parent assigned to the Debtor. Where Mailing Addresses are selected, then the related record’s mailing address will apply as expected. |
CY-2230 | 12.23 | Maintenance | The Custom Action Trigger for ‘Job Order Fill’ was not working as expected as triggered where a filled job was edited as well as when it is was filled. | This issue has been resolved. Now where the Custom Action Trigger ‘Job Order Fill’ is applied, the action will only be triggered where an action to fill a job is run. |
CY-2398 | 12.23 | Payroll | In a Payee Record a user was unable to save a Deduction where the ‘Apply Order’ was zero '0'. An error displayed “Deductions: Apply Order is mandatory.” | This issue has been resolved. Now where a deduction is added or edited, where the ‘Apply Order’ is zero, the deduction saves as expected without error. |
CY-2039 | 12.23 | Payroll | The following issues were occurring when a Deduction Header was edited:
| These issues have been resolved. Editing of Deduction Headers now works as expected. |
CY-958 / CY-1295 | 12.23 | Payroll | The following issues were affecting the Payee Payroll - Detailed Report:
| These issues how now been resolved and the Payee Payroll - Detailed Report now works as expected. |
CY-841 | 12.23 | Payroll AU | Workcover Super and Salary Sacrifice Rules were being applied based on the state of the Job Order office instead of the WorkCover state that was selected in the Pay/Bill section of the Job Order. | This issue has been resolved. For pay items that are linked to a Job Order, Workcover Super and Salary Sacrifice Rules are now applied based on the WorkCover state that is selected in the Pay/Bill section of the Job Order as expected. For pay items that are not linked to a Job Order (e.g. manual pay items or adjustments), the Workcover Super and Salary Sacrifice Rules are applied based on the state to which the candidate office is linked. |
CY-2145 | 12.23 | Rates & Rules | A user was able to save changes to a Bill Agreement when the Bill Rate Rule did not have a Start Date for Validity. | Now where saving changes to a Bill Agreement, the system will display a hard warning where the Validity Start Date has not been entered for the Bill Rate Rule ‘A value is required for start date.’ |
CY-2142 | 12.23 | Rates & Rules | A user when editing a Bill Agreement where an existing Bill Rate Rule was selected and no changes were made, when the Save action was clicked, a message displayed ‘There are no changes to save.’ | This issue has been rectified. Now when a Bill Agreement is open in edit mode, if a user selects an unchanged Bill Rate Rule then clicks on Save, the Save action still runs and no message is displayed. |
CY-3011 | 12.23 | Recruitment Manager | The system was not allowing attachments that should be accepted where the file type is capitalised ie; .PNG; .JPG | The front office attachments process will now accept acceptable file types where the extension has been capitalised. |
CY-2597 | 12.23 | Recruitment Manager | When editing an email template in Recruitment Manager, the ‘From’ address was defaulting to the logged in user. When the template was applied to an email, that address then defaulted to the email, which made it necessary for the user, who was sending the email, to update the email address. | When creating or editing an email template, the ‘From’ address is not defaulted and remains blank. A column for ‘From’ address has been added to the lists for Email Templates so users can see if this value is populated or not. |
CY-871 | 12.23 | Recruitment Manager | When searching for a Candidate and using the Skills Tab criterion, where the ‘Verified’ option was ticketed, incorrect search results were returned. | Now when searching for a Candidate with a Skill Tab criterion of ‘Verified’, the search results return Candidates who have that skill checked as ‘Verified’. |
CY-872 | 12.23 | Recruitment Manager | A user searched for Candidates using Skills or Position criteria. When more than 10 records were in the results, when using the toggle (at the header of the opened Candidate Record) to view the records, when the user moved to /from every 10th record, the total number of records changed and the Candidate record displayed was not in the original search results. | This issue has been fixed. Now if a user searches for Candidates using Skills or Position criteria and then opens a record from the list and uses the toggle at the header of the screen to view the records, the total number does not change and only Candidates in the result list are available in the toggle action. |
CY-2019 | 12.23 | Recruitment Manager | A Mail Code added in Recruitment Manager > Maintenance > Mail Codes with an ampersand (&) stored in the name displayed incorrectly in the Mail Code list. For example in some cases it displayed twice in the list. | Now where Mail Codes added in Recruitment Manager > Maintenance > Mail Codes have an '&' symbol, they display correctly in the mail lists and do not display twice. |
CY-1979 | 12.23 | Recruitment Manager | A Standard Description was made inactive in Recruitment Manager > Maintenance > Std Description, however the description was still available when adding a Comment to an in Email or SMS. | This item has been fixed. Now where a Standard Description is made inactive in Recruitment Manager > Maintenance > Std Description, the item will not display when adding a Comment to an in Email or SMS. |
CY-2831 | 12.23 | Recruitment Manager | In a Cost Centre Job Template with agreement rates, the Bill Agreement with Cost Centre rates for the same hierarchy as the Job Template, the related bill rates did not display. | Now where a Cost Centre Job Template has agreement rates assigned where the Bill Agreement has Cost Centre rates for the same hierarchy as the Job Template, the related bill rates will display as expected. |
CY-843 | 12.23 | Recruitment Manager | In the Job Templates screen, a user applied a filter to ‘Status’ in the Job Template list to ‘Inactive’ and clicked on ‘Export’. A red Oops error displayed. | This issue has been fixed, now where a user attempts to Export a list of Job Templates from the Job Templates screen, if a filter is applied to ‘Status’, there is no error displayed and the list exports as expected. |
CY-920 | 12.23 | Recruitment Manager | If a Custom Action has been configured to be triggered from the Search Job screen, if a user ticked the Select All option, the Custom Action did not work. | This item has been resolved. Now where a Custom Action is available to be triggered from Search Job, if the users clicks the Select All option, the Custom Action will run where selected. |
CY-2043 | 12.23 | Recruitment Manager | The General Setting ‘Client Credit Check Mandatory before Client Active’ or ‘Cost Centre Credit Check Mandatory before Cost Centre Active’ was not ticked, however the validation was still running where status was being changed in the Client / Cost Centre records. | This validation is now working correctly. If the Credit Check Mandatory before Active setting is not true, then the validation is not being triggered where the status of the related record is changed. |
CY-2204 | 12.23 | Recruitment Manager | A user selected the 'Remember Me Daily (to midnight) setting on the MFA login pop up, however they were then re-prompted to re enter the MFA code later in the day. | Now where the ‘Remember Me Daily (to midnight) setting has been ticked, the system will allow the user to login without MFA until midnight as per the local user’s timezone. |
CY-911 | 12.23 | Recruitment Manager | A job was filled with a Job Schedule and the ‘Use Schedule for Timesheet’ ticked on the Timesheet Workflow. A user then edited one of the shifts (that did not have a break) however the system added a break with a Start & End Time of 00:00. The job was then submitted to timesheet and incorrect Scheduled Hours were calculated. | This defect has been resolved. Now where a Job Schedule is edited on a job, irrespective of whether it is flagged to ‘Use Schedule for Timesheet’, only the edits (changes made) are saved. No breaks are added, unless the user has added the break. |
CY-870 | 12.23 | Recruitment Manager | The Bulk Update - Job process was used to update a job, however the job’s end date was not updated with a message ‘The Job Order’s Purchase Order does not cover the requested date change.' - however the job had a manual purchase order. | Now where the Bulk Update - Job feature is used, if the Job’s end date requires update and the job has a manual Purchase Order, the end date will be updated as expected and there will be no validation message. This validation will only apply to purchase orders applied via the Debtor. |
CY-1592 | 12.23 | Recruitment Manager | Where a Job or Client had a Project Code flagged as the Default, if another Project Code is added or edited and the Default is ticked, the Default tick is removed from the other item, but there was no warning message about this. | This item has been fixed. Now where a user adds or edits a Project Code, a warning displays ‘Another Project Code is set as the default. Do you want to make this the new default?’ The user can then select ‘Yes’ to apply the default or ‘No’ to return the Add Project Code pop up and make changes as required. |
CY-1603 | 12.23 | Recruitment Manager | A user that did not have Security Permission to ‘Maintain Referral Workflow’, tried to move a Candidate from the Filled stage. When this happened an ‘Unauthorised Access’ error displayed. | Now where a user without security permission to ‘Maintain Referral Workflow’, attempts to move a Candidate from the Filled stage, the Candidate is un-filled from the job and moved to the new stage and the Job’s status is changed to Vacant. Note: In order to move Candidate from state to stage in a Referral Workflow, a user must have permission to ‘Job Order > Job Referral’, Edit. |
CY-2497 | 12.23 | Reports | In the Report Module, the Candidate Skill Expiry Report where scheduled, was failing with the message “An item with the same key has already been added”. | This issue has been rectified. Now where the Candidate Skill Expiry Report is scheduled, it runs as per the schedule without the reported error. |
CY-2128 | 12.23 | Reports | The Find Timesheet Reports was showing the timesheet multiple times. | This issue has been resolved. Now the Find Timesheet Report is not showing duplications of the same timesheet. |
CY-932 | 12.23 | Time & Attendance | When creating a Timesheet Import batch, a user selected a Source option in the Batch Wizard screen, and then removed it. The user then selected ‘Next’ and the import process did not move to the next step. | Now when creating a Timesheet Import Batch, in the Batch Wizard screen if a selected Source is then removed, when clicking the Next action the import process proceeds as expected. |
CY-2457 | 12.23 | Time & Attendance | In Mobile Timesheets when adding an attachment if a user attempted to upload a file while another file was still uploading a user was able to Save/Submit the timesheet prior to the file being correctly uploaded. The file still attached however was empty when downloaded. | Now when attempting to upload an attachment in Mobile Timesheets if the user selects to Save/Submit and the attachment(s) have not completed their upload, a message displays “Update in progress, cannot submit/save right now.” Once the file(s) have completed the upload process, the user will be able to Save/Submit the timesheet. |
CY-2456 | 12.23 | Time & Attendance | In Mobile Timesheets a user tried to delete an attachment on a timesheet with multiple attachments, however the system deleted the wrong attachment. | This item has been fixed. Now where a Mobile Timesheet has multiple attachments, where an attachment is selected and deleted, the selected attachment is removed. |
CY-927 | 12.23 | Time & Attendance | In a Timesheet notification template assigned to a Reminder Notification, the Cost Centre Code, Cost Centre Name and Job Location merge tags were added to the message body, however the merge tags did not populate values when sent. | This issue has been fixed. Now where merge tags for Cost Centre Code, Cost Centre Name and Job Location are applied to notification templates that are used for Reminder Notifications, the merge tags will populate the relevant values. |
CY-721 | 12.23 | Time & Attendance | In the Historical Tab, where a Candidate or Client Contact with permission to ‘Expire Restore Delete Timesheet’ expired a timesheet, in the result list the Manage Layout item for ‘Expired by Name’ did not show the name of the Candidate or Client Contact that expired the timesheet. | This issue has been resolved. Now where a Candidate or Client Contact expires a timesheet, in the Historical Tab result list the Manage Layout item for ‘Expired by Name’ displays the Firstname and Surname of the Candidate or Client Contact that expired the timesheet. |
CY-3120 | 12.23 | Time and Attendance | Where a job had a Job Template assigned with Standard Rates, and the rates had been unlinked (the rates were edited on the job), in the corresponding timesheets, a user was unable to select Additional Items for dates that intersect with the previous rate set. For Example: Job with start date 05/08/2024 is linked to template with Standard Rates. A new Rate Set with start date 15/08/2024 is added on the job, unlinking rates from this date. Additional Items could longer be entered for dates 05/08/2024 - 14/08/2024. | This issue has been fixed. Now where a new rate set has been added to a Job using a Job Template’s Standard Rates, Additional Items on the corresponding timesheets are available for selection as per the Job’s Rate set validity period. |
CY-3005 | Time and Attendance | It was not possible to attach a .msg file to a timesheet. | Now where a user tries to attach a .msg file to a timesheet, the attachment is accepted. | |
CY-2472 | 🇦🇺 Payroll | When adding a Pay Company, details added to the Superannuation Tab were not saving even where the Super Fund was selected in the Default Settings. | This process is now working correctly. Now when creating a Pay Company, items added to the Superannuation Tab are saved on save of the record. | |
CY-719 | 🇦🇺 Payroll | An AU Payee Deduction was linked to a Deduction Header of type ‘Child Support’. Where the Child Support Deduction Header had a default rate or projected earnings, rolling deduction settings were able to be applied in the Payee’s deduction. | Now where an AU Payee Deduction is linked to a Deduction Header of type ‘Child Support’, if the Child Support Deduction Header has a default rate or projected earnings, if a user attempts to configure rolling rolling deductions in the Payee’s deduction settings, an error is displayed ‘Deduction header is linked to rolling payee deductions. Rolling deductions cannot have a default rate or protected earnings.’ and the changes will not be saved. | |
CY-3246 Patch 1 | Payroll | A payee deduction had rolling deduction details AND bank account details, the bank account details were cleared when the deduction occurred in a pay batch and the deduction stage was rolled back. Note: this still occurred if the batch was cancelled after the rollback. This prevented the pay batch from being closed - an error displayed “Cannot insert the value NULL into column 'AccountName', table 'DBNAME_FastTrack.rar.EftTransaction'; column does not allow nulls.” | This defect has been fixed. Now where a payee deduction has rolling deduction details and bank account details, the bank account details are not cleared when the deduction is triggered in the pay batch and the deduction stage is then rolled back. | |
CY-3244 Patch 1 | 🇳🇿 Payroll | When a NZ Payday submission included a Payee who’s combined First & Surname was > 50 characters, an error occurred when we previewed the pre submission report. | This item has been resolved. Now where a NZ Payday submission includes a Payee with a combined First & Surname that is greater than 50 characters, the pre submission report displays /2024 - 14/08/2024. | This issue has been fixed. Now where a new rate set has been added to a Job using a Job Template’s Standard Rates, Additional Items on the corresponding timesheets are available for selection as per the Job’s Rate set validity period. |
CY-3005 | 12.23 | Time and Attendance | It was not possible to attach a .msg file to a timesheet. | Now where a user tries to attach a .msg file to a timesheet, the attachment is accepted. |
CY-2472 | 12.23 | 🇦🇺 Payroll | When adding a Pay Company, details added to the Superannuation Tab were not saving even where the Super Fund was selected in the Default Settings. | This process is now working correctly. Now when creating a Pay Company, items added to the Superannuation Tab are saved on save of the record. |
CY-719 | 12.23 | 🇦🇺 Payroll | An AU Payee Deduction was linked to a Deduction Header of type ‘Child Support’. Where the Child Support Deduction Header had a default rate or projected earnings, rolling deduction settings were able to be applied in the Payee’s deduction. | Now where an AU Payee Deduction is linked to a Deduction Header of type ‘Child Support’, if the Child Support Deduction Header has a default rate or projected earnings, if a user attempts to configure rolling rolling deductions in the Payee’s deduction settings, an error is displayed ‘Deduction header is linked to rolling payee deductions. Rolling deductions cannot have a default rate or protected earnings.’ and the changes will not be saved. |
CY-3246 / CY-3240 | 12.23 P1 | Payroll | A payee deduction had rolling deduction details AND bank account details, the bank account details were cleared when the deduction occurred in a pay batch and the deduction stage was rolled back. Note: this still occurred if the batch was cancelled after the rollback. This prevented the pay batch from being closed - an error displayed “Cannot insert the value NULL into column 'AccountName', table 'DBNAME_FastTrack.rar.EftTransaction'; column does not allow nulls.” | This defect has been fixed. Now where a payee deduction has rolling deduction details and bank account details, the bank account details are not cleared when the deduction is triggered in the pay batch and the deduction stage is then rolled back. |
CY-3244 | 12.23 P1 | 🇳🇿 Payroll | When a NZ Payday submission included a Payee who’s combined First & Surname was > 50 characters, an error occurred when we previewed the pre submission report. | This item has been resolved. Now where a NZ Payday submission includes a Payee with a combined First & Surname that is greater than 50 characters, the pre submission report displays as expected. |
CY-3320 | 12.23 P2 | Maintenance | When a user attempted to import a file in Data Import, an error displayed and the file did not import. | This issue has been fixed. Now where a user tries to import a file in Data Import, the file imports as expected and no error occurs. |
CY-3296 | 12.23 P2 | Recruitment Manager | When editing a shift on a Job Order in the Job Schedule, after selecting ‘Ok’ a ‘Shift updated successfully’ message displayed, however the ‘Attendance’ pop up did not close. | This defect has been fixed. Now where a user is editing a shift on a Job’s Job Schedule, on selection of ‘Ok’ the ‘Shift updated successfully’ message displays and the ‘Attendance’ pop up closes. |
CY-3288 | 12.23 P2 | Recruitment Manager | When a Client/Candidate that has security permission to a Custom Section logged into the Portal, the Portal screen did not load. | This item has been fixed. Now where a Client/ Candidate with security permission to a Custom Section logs into the portal, the screen loads as expected. |
CY-3279 | 12.23 P2 | Recruitment Manager | A user opened a Candidate record and clicked on the Quick Access menu to move to the ‘Communication History’. When they selected the ‘Next’ page option nothing showed for page 2. | This problem has been addressed. Now where a user opens a Candidate record’s ‘Communications History’ section via the Quick Access menu, when using ‘Next’ the next page loads without issue. |
CY-3291 / CY-3297 | 12.23 P2 | Recruitment Manager | In Recruitment Manager > Reports > FT Standard Reports > Timesheet, the ‘Find Timesheet’ report, a user clicked on ‘Timesheet Id’ within the report to view the related Timesheet, however the page loaded as blank. | This item has been fixed. Now where a user clicks on ‘Timesheet Id’ within the ‘Find Timesheet’ report in FT Standard Reports, the related timesheet displays. |
CY-3277 / CY-3278 | 12.23 P2 | Time & Attendance | A user was keying a timesheet and attempted to add a Break Time / Project Code to an Attendance Item. The time start / end was keyed in, and the Save button selected, however the pop up remained and the break was not saved. | This issue has been resolved. Now where a user is keying in a timesheet and a Break Time or Project Code is added to an Attendance Item, on Save the item is saved as expected. |
CY-3287 | 12.23 P2 | Time & Attendance | In Time & Attendance, when a Candidate/Client Portal user with ‘PC Experience’ assigned to their User Profile navigated to the Available Tab, the ‘Week Ending Date From’ field in the search header was defaulted to the current week ending date. Unless the user was aware of this and changed or cleared the date that had been defaulted in the ‘Week Ending Date From’ field, they were unable to see any timesheets that belonged to periods that ended prior to the defaulted date. | This issue has been resolved. Now when a Client / Candidate user opens Time & Attendance in the Portal, the ‘Week Ending Date From’ date is not defaulted so that the user can see available timesheets that correspond to any prior period by default. |
CY-3289 | 12.23 P2 | Time & Attendance | A user logged into Mobile Timesheets and the timesheet count showed zero for all statuses when there were timesheets waiting to be actioned. The correct count displayed when the user refreshed or went into a status and then returned to the home page. | This problem has been fixed. Now when a user logs into Mobile Timesheets, the status counts on the home page reflect the number items within each state waiting to be actioned as expected. |
CY-3308 | 12.23 P2 | Payroll | In Payroll > Reports > Payee Payroll Detailed, a user clicked on ‘Export to File’ to export the report, and an error message displayed. | This issue has been resolved. Now where a user clicks ‘Export to File’ for the Payee Payroll Detailed report in Payroll > Reports, the report exports as expected. |