Version 1.99.1 | General Release

Fees – Purchase Order Number

Version 1.99.1

General Release

Fees – Purchase Order Number

When using Fees within Job Order, users can now assign a Purchase Order Number to the Fee. When a Purchase Order Number is added to the Fee, Invoices with the same Job Order will be grouped by Purchase Order Number.

Version 1.99

Define Payrun Batch Size through Custom Settings
Define Timesheet Transaction Batch Size through Custom Settings
Buttons available on Timesheet Manager
Timesheet Entry attachment description on Approval Portal

 

Version 1.99

Define Payrun Batch Size through Custom Settings

Users can now define their preferred Payrun Batch Size through Setup>Develop>Custom Settings>Timecards Config >Create Payrun Batch Size. 

When the “Create Payrun Batch Size” field in Custom Settings is Blank, Null (0) or greater than 2000  then default Payrun Batch Size will be 2000 transactions per batch. If “Create Payrun Batch Size” is between 1 and 1999 then Payrun Batch Size shall be the number entered in Custom Settings.

Users may wish to consider lowering the batch size below 2000 where org performance is affected by high CPU. High CPU tends to occur when an org has high levels of custom code or large amount of data processing in addition to the Timecards System.

Define Timesheet Transaction Batch Size through Custom Settings

Users can now define their preferred Timesheet Processing Batch Size through Setup>Develop>Custom Settings>Timecards Config >Timesheets In ProcessTimesheetsBatch. 

When the “Timesheets In ProcessTimesheetsBatch” field in Custom Settings is Blank, Null (0) or greater than 50 then default Timesheet Processing Batch Size will be 50 transactions per batch. If “Timesheets In ProcessTimesheetsBatch” is between 1 and 49 then batch size shall be the number entered in Custom Settings.

Users may wish to consider lowering the batch size below 50 where org performance is affected by high CPU. High CPU tends to occur when an org has high levels of custom code or large amount of data processing in addition to the Timecards System.

 

Buttons available on Timesheet Manager

Available Buttons on Timesheet Manager has been reworked so only needed buttons are available for use by users according to the timesheet status.

Where Status = New then available buttons are New, Submit

Where Status = Submitted then available buttons are Approve on Behalf, Revert to New

Where Status = Approved (and no transactions created) then available buttons are Process Transactions, Revert to New

Where Status = Approved (and transactions created) then there will be no available buttons

Where Status = Approved and Transactions Status = 4 (Failed) then Update Failed Ready Button will be available.

Where Status = Rejected then available buttons are Save and Submitted.

 

Timesheet Entry attachment description on Approval Portal

Where attachments have been added by Candidate via Timesheet Entry Portal then these attachments will include a description describing the type of attachment on the Candidate Approval Portal. Types of attachments will typically be Expenses, Timesheets or Invoices.

Version 1.98 | General Release

Timesheet Entry Portal error #1
Timesheet Entry Portal error #2
Approver page displaying approved timesheets
Manually created Timesheets not being automatically processed
Cannot load attachment in Timesheet Entry Portal
Home Button not working within Approver Portal
Timesheet headers with no timesheet entries
Invoices not being created and emailed

Version 1.98

General Release

Timesheet Entry Portal error #1

When using 12 hour format in Timesheet Entry Portal and a break of 60 minutes is entered then the total for the timesheet entry line will be -1 not total time less 60 minutes. When the timesheet is saved, submitted or approved the timesheet entry line will update from -1 to the correct time. This is a pagination issue and has now been fixed so the total time is always correctly shown on the timesheet entry line.

 

Timesheet Entry Portal error #2

When using 24 hour format in Timesheet Entry Portal and a break of 60 minutes is entered then the total for the timesheet entry line should be total time less 60 minutes however this does not update in real time. Only when the timesheet is saved, submitted or approved the timesheet entry line will update with the break point time factored in. This is a pagination issue and has now been fixed so the total time is always correctly shown on the timesheet entry line.

 

Approver page displaying approved timesheets

When a timesheet is approved, the approved timesheet will disappear as an option from the approval page, however when the page is refreshed the approved timesheet reappears for approval. This is caused due to the approval page catching the old URL. This issue has been fixed so when Approval Page is refreshed, the new URL is caught with correct Approval data showing.

Manually created Timesheets not being automatically processed

When using Daily Award Master and an extra Timesheet Entry Line is manually added to an existing timesheet, when the Timesheet is processed, this manually added Timesheet Entry Line is not being marked as processed. This is has been corrected and all timesheets entry lines will be marked as processed.

Note: Despite not being marked as processed – Timesheet and Invoice details are correctly calculated. There is no impact on data.

 

Cannot load attachment in Timesheet Entry Portal

Case sensitivity when setting accepted attachment format extension in Setup>Develop>Custom Settings>Timecards Config > Attachments and Attachments in Timesheet Portal has been removed. 

This means .pdf or .png in Custom Settings can now be labelled .Png or .PDF in Timesheet Portal and vice versa.

 

Home Button not working within Approver Portal

Home Button on Approver Details Page when pressed will now correctly lead users back to the home page of the Approval Portal

 

Timesheet headers with no timesheet entries

If a Placement period starts or ends in the middle of the week, it is possible there may be no actual working days for this week (i.e.Placement begins on a Saturday and working days are Mon-Fri). Previously a TImesheet would be created with no working days. This has been changed and no Timesheet will be created where there are no applicable timesheet entries.

 

Invoices not being created and emailed

When sending bulk invoices by email, no Attachment was being included in the email being sent and no record of the attachment was being stored in the Activity History. This issue has now been corrected and multiple invoices can be selected at one time and sent by email.

Version 1.97

Customise Client Approver Page Logo
Printing Consolidated Invoices – Limit Removed

Version 1.97

Customise Client Approver Page Logo

There is a now a new field in the Timecards Config custom settings to allow the logo on the approver page 2 to be customised.  To do this follow the below steps.

Part 1 – Create the Static Resource

  1. Go to Setup>Develop>Static Resources
  2. Click on New to create a new Static Resource - give it a name and make a note of it, you will need the exact name to assign it - the name cannot have spaces, use a underscore instead e.g. 2Cloudnine_Logo
  3. Enter the Name and choose the correct file e.g. logo (Logo images should be in png or jpg format.  The maximum image height and width is 150x150px.  Rectangular logos can be used provided the larger side does not exceed 100px.  Logo size must not exceed 1MB).

Part 2 – Assign the Logo in Custom Settings

  1. Go to Setup>Develop>Custom Settings>Timecards Config
  2. Click Manage and then Edit to make amendments to the config
  3. Enter the name of the static resource you have just created, it needs to be the exact name that was created before

If there is a custom logo in custom settings and it meets the criteria it will be used, alternatively the default, 2Cloudnine logo will be used.

 

Printing Consolidated Invoices – Limit Removed

When selecting a large number of consolidated invoices and clicking on Print Invoice an error was occurring advising that limits had been exceeded.  This has now been fixed by separating the PDF window (iFrame) into smaller sections.