Consolidated Invoice Email CC Validation
The validation on the Invoice Email CC field on the Consolidated Invoice object has been updated to allow the additional characters of underscores (_) and hyphens (-). In addition the validation will now allow non-ordinary domain names such as email addresses that don’t contain ‘.com’ or ‘.net’.
Consolidated Invoices List View Send By Email functionality update
Updates have been applied to the Consolidated Invoice’s Send By Email list view button to accommodate when records selected from the list view includes both invoice and credit note record types. This update ensures that the correct invoice template is used for all records selected.
Daily Awards Set Up to include leave accruals
Previously the Daily Awards did not have the ability to define Leave Rates. This functionality has been added via a Daily Award that operates in the same way as the Ordinary Hours, Regular and Shift awards.
To define Leave Types on Award Masters the following setup is required:
Setup the Leave types that will be available for use:
The Leave types that are listed on the Award Master for use are pulled from the picklist values defined in the Leave Type field on the Timesheet Entry. To add/modify the leave types listed, the picklist values must be created/modified: Setup > Create > Object > Timesheet Entry > Leave Types > Values > New > add as leave types as required
Purchase Order Number display on Perm Invoices/Perm Invoice Template
A new column has been added to the package Perm Invoice Templates to display the related purchase order number. The value displayed within this column is taken from the related Invoice’s Purchase Order Number field.
This change has been made to the following invoice templates
The following setup is required (only required if using packaged invoice templates):
The column label is defaulted as “PO No” however this can optionally be changed by adding a transaction to the Invoice PO custom label Setup > Create > Custom labels > Invoice PO > Translations > New
Ensure the Purchase Order Number field on the Invoice object is enabled to be visible to the Guest Site User profile.
Filtering Allowance Paycode Picklist
Previously when adding an Allowance to a Timesheet in the Allowances section of the Timesheet Manager, Users were presented with a list of Pay Codes that included all the pay codes created within the organisation. This can cause confusion when the same pay code name was used for different pay code record types. Now a filter has been applied to the picklist to ensure that only pay codes with the Record Type of Allowance are listed.
To ensure the picklist continues to list allowance pay codes, ensure that the pay codes have the correct record type assigned.
Record Limit Error when Scheduled job to Create Invoice Attachments Processes
An issue was reported that when an Organisation has a high number of Consolidated Invoices that have not had PDF attachments created, a system limit error can occur when the Scheduled job to Create Invoice Attachments (ScheduleCreateInvoiceAttachments) runs.
A limit of 4000 Consolidated Invoices per scheduled job has now been applied to ensure this error no longer occurs. Where the organisation has more than 4000 Consolidated Invoices without PDFs generated, those above 4000 will be left not generated until the next time the scheduled job runs.
Invoice Totals not populated on Fee Consolidated Invoice
An issue was reported that Invoice Total Fields are no longer populating on Consolidated Invoices which are derived from Fees. This issue has now been resolved.
TimeCards Batch Size custom setting
Previously fields for holding batch size overrides were located within several custom settings. These have now been moved to a central Timecards Variable Settings custom setting.
The following setup is required:
Run the below script in the Developer Console to ensure that the existing batch size overrides within the organisation are maintained Set up > Developer Console > Debug > Open Execute Anonymous Window Then insert the following script tc9_ti__ToCloudNineConfig__c old_config = tc9_ti__ToCloudNineConfig__c.getOrgDefaults(); tc9_ti__TCS_Variable_Settings__c new_config = tc9_ti__TCS_Variable_Settings__c.getOrgDefaults(); new_config.tc9_ti__Create_Payrun_Batch_Size__c = old_config.tc9_ti__Create_Payrun_Batch_Size__c; new_config.tc9_ti__Generate_Timesheet_Batch_Size__c = old_config.tc9_ti__Generate_Timesheet_Batch_Size__c; new_config.tc9_ti__Merge_Invoice_Emails_Batch_Size__c = old_config.tc9_ti__Batch_Limit_MergeInvoiceMails__c; new_config.tc9_ti__Process_Timesheets_Batch_Size__c = old_config.tc9_ti__Timesheets_in_ProcessTimesheetsBatch__c; upsert new_config;
Adding Credit Reason when creating Credit Notes
New functionality has been added to the credit note process to force the User to select a predefined credit reason before they can create a credit note. This functionality is optional and is switched on via the ‘Enforce Credit Note Reason’ field within the TimeCards Config custom setting.
When Enforce Credit Note Reason = TRUE (ticked), if the User clicks the ‘Create Credit Note’ button on the Consolidated Invoice record, they will be presented with a page asking for the credit reason before they can continue to create the credit note. When Enforce Credit Note Reason = False (unticked) the credit note will be created when the ‘Create Credit Note’ button is clicked as normal.
To use this functionality the following setup is required:
Define the Credit reasons available for the User to select. These are defined as values on the Credit Reason field on the Consolidated invoice Object. Setup > Create > Object > Consolidated invoice > Credit Reason > Values > New > add as credit reasons as required
Ensure the Users have profile access to the Credit Reason field on the Consolidated Invoice object. Turn the Enforce Credit Note Reason functionality on via the custom setting Setup > Custom Setting > TimeCards Config > Enforce Credit Note Reason = True (ticked)
Re-invoice for fee invoices
Previously the Credit / Re-Invoice functionality only accommodated the credit / re-invoice of transaction based invoices. This functionality has now been extended to accommodate Fee based invoices. Users will be able to Re-Invoice Fee Credit Notes, adjust the line descriptions, Ex Tax Amount and Tax Amount as well as totally remove a line from the invoice if required.
Credit Invoice and Rebill Tracking
New functionality has been introduced to enable easier tracking of Re-Invoiced Consolidated Invoices related to the original Credit Note. Now if a Consolidated Invoice has been created via the Re-Invoice functionality the Re-Billed field on the Consolidated Invoice will be set as True (ticked) and the Original Credit Note field will be populated with the related Credit Note.
This coupled with the existing functionality that links a Credit Note to the Original Invoice will enable Users to easily track their Consolidated Invoices to Credit Notes and then to Credit Notes and vice versa.
Inclusion of a Link to Re-Invoiced Consolidated Invoices when created
Previously, when a Consolidated Invoice is successfully created using the Re-Invoice functionality an on screen message is displayed to advise the User that the invoice was successfully created however it did not provide a link to the newly created Consolidated invoice. Users had to go back to their Consolidated Invoice list views to open/view the new invoice. Now the onscreen success message will include a link to the new Consolidated Invoice.
Fees with 0 or negative Invoice Tracking
In TimeCards version 1.113, Tracking of Transactions not included in Invoices due to 0 value, we introduced the new “Not Required” value for the transactions “Invoiced?” field to identify if a transaction has not been invoiced due to the Enable 0 and Negative Invoices setting = False. This functionality did not extend to Fee based invoices. The functionality has now been updated for Fee based invoices.
To extend this functionality to Fees the following setup is required
Add new picklist value to Fee Invoiced? Field Setup > Create > Object > Fee > Invoiced? > Values > New > “Not Required”
Revert to New – exclude flagged transactions
Previously, when the Revert to New functionality is used within the Timesheet Manager, it deletes the transactions that have been created and resets the Timesheet. Some organisations have reported that they have transactions that they do not wish to have deleted as part of the revert to new functionality.
These transactions include:
- Manually created Transactions that have been added in the Transaction section of the Timesheet Manager
- Transactions that have been loaded via external systems (ie data loaded)
Transactions created manually in the Transaction section of the Timesheet Manager will now have the Manual Entry field on the Transaction set to True (ticked) when they are created. Transactions with this field set as true will no longer be deleted as part of the Revert to New process.
Further, a new “Data Loaded Transaction” field has been added to the Transaction Object to identify Transactions that have been loaded externally. When Users are loading Transactions via external means they should set this field to True (Ticked) as part of the data load. Transactions with this field set as true will no longer be deleted as part of the Revert to New process.
The setup required is to ensure that any external methods used for loading Transactions data are updated to include the population of the Data Loaded Transaction field to be True.
General bug fixes and improvements
General bug fixes and improvements have been applied to the following:
- Debug log reporting and error messages
- Process invoice page validations
- Award Master page validations