Version 1.94.3

Refresh Button on Client Timesheet Approver page
Link Missing in Error Message

Version 1.94.3

Refresh Button on Client Timesheet Approver page

When opening the Client Approval portal in Chrome the expenses and notes section was not aligned correctly, this was fixed when refreshing by using the URL to refresh, however, when using the Refresh button it was continuing to happen.  This has now been fixed.

Link Missing in Error Message

When running creating two deductions at the same time the error message that occurs was missing the link to the dashboard with the errors. This has now been amended to include the link.

Version 1.94 | General Release

Client Approval Portal Upgrade
Cloning Placement – “IsTimesheet Created?” field is checked, should not be
Allow Invoices with total = 0 and Negative values
Update all TCS Report types to include new fields
Leave Column not Show on Client Portal
Debug Error when I try to create transactions on extended placement
Credit Note Issue
Payrun Batch Create but no Transactions allocated to it

Version 1.94

General Release

Client Approval Portal Upgrade

The Client Approval Site has been upgraded. The new Client Approval Site format is designed to be consistent with the format used for the recently introduced enhanced Timesheet Entry Site.

All existing features in Client Portal remains however the user experience has been improved.

Features include

  1. Ability to Approve and Reject Timesheets
  2. Ability to Approve multiple Timesheets at once
  3. Presentation of Timesheet grouped by Placement
  4. Ability to review each individually submitted Timesheet along with details such as Job Order, Placement, Client.
  5. Improved management and separation of Timesheets based on status by use of Tabs. ie. Current Timesheet Awaiting Approval, History of Approved Timesheets.
  6. Ability to review uploaded Attachments for Expenses, Invoices, Timesheets.
  7. Function to customise Labels throughout the Portal (i.e. can rename headers)
  8. Add Comments to the Timesheet being approved (such as reason timesheet is rejected)

 

To Set up the new portal the following steps are required:

1 ) Setup > Develop > Sites > Talent Portal
Change Active Sites Home Page to tc9_ti.Communities_LandingPage_v2
Change InActive Sites Home Page to tc9_ti.Communities_LandingPage_v2
Change Site Template to: tc9_ti.CommunityPortalTemplate

Note: these steps might vary in Orgs. Speak to your Salesforce Consultant if assistance is needed

2) Setup > Develop > Sites > ClientPortal (in SiteLabel) > Public Access Settings > Enabled VisualForce Page Access - 
Make the following Pages visible:
ApproveTimeSheet_v2
ApproverDetailPage

3) In Custom Settings users can select if they wish to use the existing approval site or the new enhanced approval site.

To select your preferred Approval Portal:

Custom Setting > Timecards Config Edit. > A new setting has been introduced called ‘Approver Page Version’. To use previous existing version set the field as 1. To use new version set the field as 2.

Note: These changes will not update existing Token Links / Approval Pages. To update token link with preferred Timesheet Approval Format.. Set your custom setting and then implement step 4.

4) To change the Token Expiry

Change the Token Expiry Date to a Date and Time to earlier than current Date and Time.

A new token will then be created

Alternately, follow the above steps and delete the token link in both primary approver and second and in the placement selected “Second Approver”.

 

Cloning Placement –  “IsTimesheet Created?” field is checked, should not be

When I clone an existing Placement and the field on the original Placement  “Is Timesheet created?” is checked, then this field will become unchecked on the newly created Placement

 

Allow Invoices with total = 0 and Negative values

A new checkbox field has been added to Setup > Custom Setting > TimeCard Config  called “Enable 0 and Negative Invoices”. 

When checked, invoices will be allowed to be 0 or negative.

 

Update all TCS Report types to include new fields

All fields included as part of Timecards System will now be available in Report Types. This will assist users when creating reports to access desired data.

 

Leave Column not Show on Client Portal

The Leave column was previously not available in the Client Approval Portal. This has now been added to the portal and Approvers can view the type of leave applied for by contractors.

 

Debug Error when I try to create transactions on extended placement

A regression defect resulting in issues when a user tries to extend a placement has been fixed.

 

Credit Note Issue

Regression issues resulting from changes to Bridging Triggers was preventing Credit Notes from being created. This issue has now been rectified and Credit Notes will successfully work regardless of status of Bridging code.

 

Payrun Batch Create but no Transactions allocated to it

Previously a fix has been done so no Pay Transaction are created when transaction type = Perm. However, whilst no Pay Transaction are created, a Pay Batch is created (with no transactions). This issue has been fixed and no Pay Batch or Pay Transactions will be created in the event transaction type = Perm.

Version 1.93.2

New Page layout for TEMP invoice Backing Sheet
Placement setting to not create portal user

Version 1.93.2

New Page layout for TEMP invoice Backing Sheet

Issue fixed: a new backing page layout has been introduced. This layout is known as version 2 or v2. As part of our solution, a user can choose if they wish to continue to use the existing backing sheet layout (version 1) or the new version (version 2) via:

 Custom Setting > Timecards Config Edit.

A new setting has been introduced called ‘Backing Sheet Version’. To use version 1, set the field as 1. To use version 2, set the field as 2.

 

Placement setting to not create portal user

Issue fixed: Not all contacts require a Candidate timesheet entry portal to be created even though timesheets have been created for their placement. To resolve this, we have introduced a new field on Placement called “Does Not Use Online Timesheets”. When this field is enabled and the contact does not have a timesheet portal created then no candidate portal will be created for that contact via the placement being used.

Version 1.93.1

New Invoice Pages not showing on Invoice Templates

Version 1.93.1

New Invoice Pages not showing on Invoice Templates

Issue fixed: New Invoice VF Pages known as _v2 for Perm, Temp, Credit Perm, Credit Temp, Fee, Credit Fee are not showing available in Invoice Templates under Pages. Code has been modified so these will show.

To select these pages go to Invoice Templates > Invoice Template Record > Pages Picklist (select desired page) 

Version 1.93

Timesheet Processing: Send email at end of process
Create Payrun: Send email at end of process
Invoice by Batch: Send email at end of process
Invoice by Batch: One debug header per process
Add Process field to Batch Log object
Exception To Not Send Timesheet Approver Email IF Timesheets = 0
New Page Layout for Perm, Temp, Credit Perm, Credit Temp, Fee, Fee Credit
Sidebar to ProcessInvoice Page
When Timesheet fails, Timesheet Record ID to be captured in debug log
New field added to transactions called “Pay Transaction Flag” (used for Bridging)
New field added to transactions called “Enable Bridging” (used for Bridging)
Verify_Conversion_Fee validation on non perm placements
Remove Image/Logo from Timesheet Manager Approval Popup
Paycode ID not created when transactions processed via Timesheet Manager
Expense plus Tax exceeds Total Pay / Bill field length
If Group By Project Codes is enabled in Account and transaction has a project code, it does not show on Invoice

Version 1.93

Timesheet Processing: Send email at end of process

Issue fixed: No email is sent at end of Transaction processing if an error occurs. We have changed our product so that when a debug log is created as a result of Transaction processing, an email will be sent to notify the relevant contact. If no debug is created, no email shall be sent.

 

Create Payrun: Send email at end of process

Issue fixed: No email is sent at end of Payrun processing if an error occurs. We have changed our product so that when a debug log is created as a result of Payrun processing, an email will be sent to notify the relevant contact. If no debug is created, no email shall be sent.

 

Invoice by Batch: Send email at end of process

Issue fixed: No email is sent at end of Invoice processing if an error occurs. We have changed our product so that when a debug log is created as a result of Invoice processing, an email will be sent to notify relevant contact. If no debug is created, no email shall be sent.

 

Invoice by Batch: One debug header per process

Issue fixed: Multiple debug headers are created for the invoice process when multiple exceptions are raised for a single process. We have now changed this so that how debug header are created. If more than one exception is raised for a single process then all debug logs will be created under the one debug header.

 

Add Process field to Batch Log object

Issue fixed: A picklist field called “Process type” has been added to the Batch_Log__c. This field will list the type of process that was run for the Apex Job.

 

Exception To Not Send Timesheet Approver Email IF Timesheets = 0

issue fixed: Users have been receiving email notification in event that timesheets have been submitted where the Week Actual Hours = 0 AND there is no related Expense. Some client do not require emails to be sent in this scenario therefore a setting has been introduced to:

 Custom Setting > Timecards Config Edit, called No Approver Emails On 0 Timesheets. 


When this is checked, no email will be sent where the Week Actual Hours = 0 AND there is no related Expense.

 

New Page Layout for Perm, Temp, Credit Perm, Credit Temp, Fee, Fee Credit

Layout for Temp, Perm, Credit Perm, Credit Temp, Fee and Fee Credit invoices have been updated and improved to better capture typical invoice requirements and presentation of Invoice. This includes  better alignment of fields and margins which in addition to making information easier to digest will make invoices more print friendly. No new fields or information have been added to invoices.

Setup

  1. If you want to keep using existing invoice format then no changes are required.
  2. To upgrade to new invoice format the following steps are required:

Pages need to be made available in Client Site.

Setup > Develop > Sites > ClientPortal (in SiteLabel) > Public Access Settings > Enabled VisualForce Page Access - Make the following Pages visible

Credit_TempInvoice_v2
Credit_PermInvoice_v2
PermInvoice_v2
FeeInvoice_v2
CreditFeeInvoice_v2
TempInvoice_v2

3) Pages on Invoice Templates will need to be updated for each Invoice Record Type.

Invoice Templates / Select the Template and Record type / Assign the Correct Page to Invoice Template

Pages on Invoice Templates will need to be updated for each Invoice Record Type created

Note: These changes will not update previously created invoices. To update existing invoices go to Consolidated Objects – select the desired Invoice Record and delete the following fields:

-Link Token

-Online Url

and then press Preview or Send Invoice button to create a new Invoice

 

Sidebar to ProcessInvoice Page

Issue fixed: On Process Invoices Page, there is no sidebar so users can leave Process Invoices Page and access other areas of the org. To help improve navigability of the org, a sidebar with links has been added to the page.

 

When Timesheet fails, Timesheet Record ID to be captured in debug log

Issue fixed: Debug Log captures all needed information to identify the issue however can be difficult to find the needed debug log at a later point in time. To solve this, Debug Log now captures the Timesheet Record ID and users can search for the needed Debug Log by adding the timesheet record ID to the SF Global Search function.

 

New field added to transactions called “Pay Transaction Flag” (used for Bridging)

Issue fixed: A new field has been added to transactions called “Pay Transaction Flag”. When Bridging has inserted transactions into pay transactions, this flag will be updated to True. This is to determine successful bridging integration.

 

New field added to transactions called “Enable Bridging” (used for Bridging)

Issue fixed: If an Org has bridging installed, there may be a need to disable bridging functions from time to time. Similarly if bridging is not being used, then bridging component should be disabled. A field has been added to:

 Custom Setting > Timecard Config Edit called “Enable Bridging”. 

When disabled, all bridging components will no longer operate.

 

Verify_Conversion_Fee validation on non perm placements

Issued fixed: The placement validation Verify_Conversion_Fee is firing on non-perm placements. Thus leading to issues during data migration if any perm placement fields are populated. This was fixed by introducing a criteria to the validation rule to only action if the Placement record type equals Perm.

 

Remove Image/Logo from Timesheet Manager Approval Popup

Issue fixed: When Timesheet are approved via Timesheet Manager, a popup occurs where users place the reason for approval. This popup has an empty logo. This logo has been removed.

 

Paycode ID not created when transactions processed via Timesheet Manager

Issue fixed: When timesheets are transacted via Timesheet Manager, no Paycode ID is assigned to the transaction. This function however works when transactions are created via Batch Scheduler. We fixed this and now Paycode ID will be assigned to transactions regardless of method used for creation.

 

Expense plus Tax exceeds Total Pay / Bill field length

Issue fixed: When entering expenses with Tax in Timesheet Manager, it is possible for the total Expense plus Tax to exceed to allowable length stored on the transaction. To resolve this the field TotalBillIncTax found on Transaction has been increased to Currency(12,2).  This will ensure, that the sum of Expense and Tax cannot exceed the allowable limit.

 

If Group By Project Codes is enabled in Account and transaction has a project code, it does not show on Invoice

Issue fixed: If ‘Group by Project Code’ is enabled in the account. Any transactions with project code do not show on the Invoice. To fix this we changed the mapping so all transactions regardless if they have project code or not, will correctly show on invoice when required to group by project code.