Version 1.112.2 | General Release

Page Break fixes on Temp v2 and Temp US v2

Version 1.112.2

General Release

Page Break fixes on Temp v2 and Temp US v2

Corrections have been made to the Temp v2 and Temp US v2 invoice layouts so that unnecessary page breaks do not occur on invoice layouts.

Version 1.112.1

Creating new Invoice PDF/Attachment using Compose Invoice Email
Rounding Issue on Re-Invoice

Version 1.112.1

Creating new Invoice PDF/Attachment using Compose Invoice Email

When the ‘Compose Invoice Email’ function is used on a Consolidated Invoice record where there is no existing Invoice PDF/Attachment, then a new PDF/Attachment shall be created as part of this process. This new file will include the .PDF extension.

 

Rounding Issue on Re-Invoice

An issue has been fixed so that totals on the ‘New Bill Qty’ column on Re-Invoice page layouts is shown as rounded to the second decimal at all times.

Version 1.112

Ordinary Hours – Award Re-interpretation where multiple timesheet entries entered for same day.
‘Flag’ Invoices that can be ‘resent’ by email
Setting up Base URL for Client Portal.
Future Date Restriction for ‘Create Payrun’ and ‘Process Invoices’ VisualForce pages.
Processing of Transactions via Timesheet Manager not allowed if a ProcessTimesheet Batch job is running.
Negative Transactions created from a Credit Note, no longer editable on Timesheet Manager.
Prevent ‘double click’ of ‘Create Transactions and Re-Invoice’ button on ‘Re-Invoice’.
Revert Timesheet to ‘New’ Status via Timesheet Manager after transactions created
Timesheet Manager ‘add’ transaction button now copies Tax fields
Exclude adjustment timesheet entries from timesheet extension where daily award has been applied
Re-Invoice where multiple transactions per client are amended now calculating applying adjustments correctly
Changes to the Process Payrun VisualForce page

Version 1.112

Ordinary Hours – Award Re-interpretation where multiple timesheet entries entered for same day.

Setup Required (Optional)

Ordinary Hours Award logic has been modified to account for different project codes across multiple timesheet entries when processing transactions. Ordinary award transactions, when created, will now be based on the project code associated to the timesheet entry (or entries). This will help the customer track time against different time/cost activities within the job order/placement. Previously timesheet entries were merged into one transactions during the award interpretation.

 

Changes to note:

Previous Ordinary Hours Award logic: Ordinary award interpretation previously took into consideration the daily logic calculation, public holiday calculation, weekly logic, saturday and sunday rules for the week-end logic calculation. Previous timesheet entries were retrieved in case of extension of placements as well as weekly logic recalculations.

 

Updated Ordinary Hours Award  Logic: Ordinary Hours will create as many transactions dependent on the number of timesheet entries with different project codes. The weekly cut off will be taken into consideration while the actual hours for the timesheet entries have to undergo a pro rata calculation between the project code first, then the pay code breakpoints assigned to the award.

The final number of transactions and the quantity of the transactions will be dependent on the breakpoints defined in the awards.

 

Functional Impacts:

  1. From a user perspective, changes will only be noticed where a timesheet has multiple project codes and/or additional timesheet entry lines have been added with different project codes. When a timesheet does not consists of multiple project codes and/or no additional timesheet entry lines with multiple project codes, then there will be no impact on transactions
  2. Full timesheet extension functionality remains in place
  3. Users can add timesheet entries to timesheets with existing transactions and transaction logic will handle this

 

To use Ordinary Hours Award Version 2 the following setup is required –

Setup > Custom Settings > Available Awards > Manage > Australia >

Award interpreter Class = AwardBuilderFactoryV2

If you wish to revert Ordinary Hours Award back to version 1 then:

Setup > Custom Settings > Available Awards > Manage > Australia >

Award interpreter Class = AwardBuilderFactory

 

‘Flag’ Invoices that can be ‘resent’ by email

Users can now specify if particular invoices can be sent to a invoice recipient on more than one occasion.  This feature gives greater control to user to ensure Invoices are not ‘accidentally’ sent invoices when unintended.

This new feature applies at two levels.

  1. Send Invoice via Consolidated Invoice Record.

The first time an invoice is sent, the field ‘Last Sent’ will be populated.

If a user attempt to send an invoice by email and the field ‘Last Sent’ is populated then a notification will pop up advising sender that invoice has previously been sent and seeking confirmation that invoice should be resent.

  1. Send Invoice via Consolidated Invoice List View (Sending in bulk)

A new checkbox is available called ‘Enable Bulk Resend’ on the consolidated invoice record. This field will be False by default. All selected invoices that have ‘Enable Bulk Resend’ = True will always be included as part of the invoice list view send process.

Any invoice that has ‘Enable Bulk Resend’ = False will not be sent even if other selected invoices included in the bulk send process have the checkbox as True.

Note: Users will receive an on-page notification advising those invoices that have ‘Enable Invoice Resend’ = False will not be sent. However, users may wish to create a custom list view to identify invoices that cannot be/have not been resent.

To do so, the List View filter conditions will need to be:

  • ‘Enable Bulk Resend’ =  False
    
    ‘Last Sent’ not = Blank  

 

Setting up Base URL for Client Portal.

 Configuration check Required

A Salesforce Issue has made it necessary to ensure all Client Portal Site settings reference ‘http’ as part of the Client Approval Portal Base URL. These changes will ensure Consolidated Invoices don’t result in a blank page and Client Approval Portal pages do not break due to incorrect base URL configuration.

  • Sites
    1. Sites > Select Site URL consisting of URL of Client Portal.
    2. Edit
    3. Update Base URL so it consists of ‘Http’ not ‘Https’

 

  • Remote Site Setting
    1. Setup > Security Controls > Remote Site Setting
    2. Select record containing name of Client Approval Portal
    3. Edit
    4. Update Base URL so it consists of ‘Http’ not ‘Https’

 

Future Date Restriction for ‘Create Payrun’ and ‘Process Invoices’ VisualForce pages.

System Administrators can prevent users logged in without system administration privileges from using filters with a future date when creating a ‘Payrun’ or processing an ‘Invoice’

For Creating a Payrun

When Setup > Custom Setting > Timecards Config > Prevent Future Payrun = True and the user does not have system administration privileges then the field ‘Entry Date’ must be no earlier or equal to todays date when performing a payrun.

System Administrators will be able to use ‘future dates’ regardless of custom settings.

Notes: The on-page notification non-admin users receive when a future date is entered can be customised if desired. This can be found at:

Set up > Create > Custom Labels > Process Payrun  Prevent Future Payrun > New Local Transactions / Overrides

For Processing an Invoice

When Setup > Custom Setting > Timecards Config > Prevent Future Invoices = True and user does not have system administration privileges then the fields ‘Invoice Date’, ‘From Date’, ‘To Date’ must be equal to or before current date.

System Administrator will be able to use ‘future dates’ regardless of custom settings

Notes: The on page notification ‘non admin’ users receive when a future date is entered can be customised if desired. This can be found at:

Set up > Create > Custom Labels > Process Invoice Prevent Future Payrun > New Local Transactions / Overrides

Processing of Transactions via Timesheet Manager not allowed if a ProcessTimesheet Batch job is running.

Users are now prevented from being able to ‘Process Transactions’ via the Timesheet Manager when ProcessTimesheet Batch job is running is the background to create transactions. If a user attempts to create transactions when a batch job is in progress they will receive an on page notification advising them to try later.

This measure has been introduced to protect data integrity. As a timesheet could be using the same data that is being used as part of the batch job.

 

Negative Transactions created from a Credit Note, no longer editable on Timesheet Manager.

Negative Transactions created from a Credit Note will not show in edit mode on matching timesheet. This is because once a timesheet has an Invoice or Payrun associated with it, transactions are no longer editable for a timesheet via ‘Timesheet Manager’.  

This measure has been introduced to protect the integrity of data in transactions.

 

Prevent ‘double click’ of ‘Create Transactions and Re-Invoice’ button on ‘Re-Invoice’.

When a user clicks the ‘Create Transactions and Re-Invoice’ button on the Re-Invoice page the button will ‘grey out’. This is to ensure a user cannot click the button multiple time thus causing potential duplicate Re-Invoices.

Note: If a user removes some transactions for re-invoicing. They will need to refresh the ‘Re-invoice’ page in order to ‘Re-Invoice’ any remaining transactions.

 

Revert Timesheet to ‘New’ Status via Timesheet Manager after transactions created

Timesheets with transactions can be be reverted back to ‘new’ status via ‘Revert to new’ button on Timesheet Manager; where no Invoice or Payrun has been created for that timesheet.

The action of ‘reverting’ a timesheet back to new will delete all existing transactions and allow users to edit timesheet before approving and processing transactions once again.

When reverting a timesheet back to new there a few things to note:

  1. It only takes one transaction from a timesheet with an Invoice associated with it to disable the ability to revert timesheet.
  2. It only takes one transaction from a timesheet with an Payrun record associated with it to disable the ability to revert timesheet.
  3. Where a timesheet has an Invoice or Payrun associated with it, the ‘Revert to new’ button shall disappear.
  4. Extending a timesheet that already had Invoice or Payrun associated with it will not result in ‘Revert to new’ function being available.

Timesheet Manager ‘add’ transaction button now copies Tax fields

Where a timesheet manager is showing transactions and the + button is pressed for a transaction. All existing transaction details will be cloned except for tax details which will apply the tax associated with the market found on the placement related to the timesheet.

If the original transaction has tax record ‘A’ associated with the market and I change the Tax record to ‘B’ and then clone the transaction. Then cloned transaction will apply tax record B.

 

Exclude adjustment timesheet entries from timesheet extension where daily award has been applied

Version 1.111 saw the introduction of a rule to stop timesheet entries being added to a timesheet and processed as a transaction once an Invoice or Payrun Batch is associated with transactions for the timesheet. This causes potential issue if a working day needs to be added to a timesheet after timesheet processing has occurred. For example, if a candidate neglected to submit a day for the week they worked.

Administration (back office) can now add extra timesheet entries to a processed timesheet (with an associated Invoice or Payrun) and mark these timesheet entries using a new field on ‘Timesheet Entry’ called ‘Manual Adjustment’ and successfully process transactions. Timesheet entries where ‘Manual Adjustment’ is checked or true will not be included in transaction processing. Users will be required to manually modify transactions to correctly capture. The purpose of adding timesheet entries is solely so the timesheet accurately reflects time worked.

 

Re-Invoice where multiple transactions per client are amended now calculating applying adjustments correctly

Where multiple transactions exist on the Re-invoice page and multiple transactions are adjusted, manually inconsistent outcomes have been known to occur. This issue has now been corrected and pay, bill adjustment and re-invoice processing will correctly calculate correct results.

 

Changes to the Process Payrun VisualForce page

  1. The Process Payrun VisualForce page has had the ‘Remove’ column removed. Ability to remove has now been replaced with ‘Bulk Remove’ functionality.  This function allow users to exclude payrun records when a payrun batch is processed.
  2. Delete Payrun button on the Process Payrun page has been removed.