Version 1.119

Version 1.118.1 | General Release
Version 1.120

Version 1.119

No cancel option on the Invoice Template record setup/edit page

A “Cancel” button has now been added to the Visualforce page responsible for maintenance of Invoice Template records to enable users to exit.  This button functions in either set up, or edit mode, without saving any changes.


Ordinary Hours Award can now have Daily Hours Breakpoints defined for Saturday, Sunday and Public Holidays

Optional Setup

Previously Ordinary Hours Award Masters had the following types of breakpoint options for Monday to Friday:

  • Daily time (hours worked outside of the standard start and end time)
  • Daily hours (hours worked over a defined number of hours in 1 day)
  • Weekly hours (hours worked over a defined  number of hours in 1 week)

Saturday, Sunday and Public Holidays however did not have ‘Daily Hours’ breakpoints meaning users did not have the ability to define if a different pay code should be used on Saturday, Sunday or public holidays based on the number of hours worked on that day.

Users now can now define ‘Daily Hours’ Breakpoints on Ordinary Hours Awards for Saturday, Sunday and Public Holidays. Transactions created for Saturday/Sunday and Public Holidays will use Daily Hours logic as set up in the following breakpoints:

“Do you wish to set Saturday/Sunday/Public Holiday Hours Breakpoints”

“Do you wish to set Saturday/Sunday/Public Holiday Overtime Conditions”

The exception to this rule is when Weekly logic from the ‘Do you wish to set Weekly Breakpoints?’ section takes priority. This occurs when the number of hours worked on a timesheet has exceeded ‘Ordinary Weekly Hours’  defined in the ‘Standard Elements’ Breakpoint.

Setup Notes:

Both of the following sections –

“Do you wish to set Saturday/Sunday/Public Holiday Hours Breakpoints”

“Do you wish to set Saturday/Sunday/Public Holiday Overtime Conditions”

will be required to be populated when a new Ordinary Award Master is created or an existing Ordinary Award Master is edited.

No updates will be required for either breakpoint on existing Ordinary Hours Awards Masters (unless they will be edited/updated after version upgrade).


Fee record stamped with incorrect ‘Invoice Date’  

Setup Required

A new field has been created to overcome the issue of fee records being stamped with an Invoice Date that does not match the Date on Consolidated Invoices and the Process Invoice page.

The new field, has a “Date” format: Invoice Date (tc9_ti__Invoice_Date__c).

The new field will replace the existing “Date/Time” field: Invoice Date (tc9_ti__InvoiceDate__c)

To Setup:

Fees > Open a Fee Record > Edit Layout 

Remove  tc9_ti__InvoiceDate__c from page layout and replace with tc9_ti__Invoice_Date__c (both are called ‘Invoice Date’)

Use the following script in Developer Console to transfer Data from  tc9_ti__InvoiceDate__c to new field tc9_ti__Invoice_Date__c :

List<tc9_ti__fee__c> fees = new List<tc9_ti__fee__c>();

for(tc9_ti__Fee__c fee:[select tc9_ti__InvoiceDate__c,tc9_ti__Invoice_Date__c from tc9_ti__fee__c where tc9_ti__InvoiceDate__c!=null and tc9_ti__Invoice_Date__c=null order by createddate desc limit 10000]){
fee.tc9_ti__Invoice_Date__c =;

update fees;


Exporting Transactions generated via “Process Invoice”  defaults to a US based date format

Transactions exported from Consolidated invoices (Client Invoices), previously had a US date format in the .CSV file (ie MM/DD/YYYY)

This has been updated, and the transaction dates exported in the .CSV file will now be based on the logged in users locale. (ie. If the user locale is Australia then the date format will be DD/MM/YYYY)

List index out of bounds: 0 when attempting to re-invoice

When a user selected ‘Create New Transactions and Invoice’ on the Re-Invoice Function, it produced the following error report – “List index out of bounds: 0 error occurs”.

This has now been fixed. There are no modifications required.