This package version requires the following mandatory packages in place before installation.

An optimisation improvement in the design around timesheet approval has been brought in to alleviate the problem of Transaction Pay batches and synchronisations within 2c9 Payroll.

Previously existing code logic:

• Skedulo Timesheet Approval was also resulting in 2C9 Payroll system's timesheet to be in the status of "Approved"
• The transaction state (tc9_et__Transaction_Creation_Stage__c) was set to 2 as default within the package

Current Code Logic Fix:

• The enhancement has provided the flexibility to have the 2c9 Payroll System Timesheet set to "Ready" status in order to run some additional synchronisation workflows internal to 2c9 Payroll system prior to formally approving the timesheet.
• The transaction state (tc9_et__Transaction_Creation_Stage__c) is now moved outside the package as a meta data setting, providing flexibility to change the field value.

Instructions:

As an Administrator (SF Administrator):

• The package must be installed
• A new Object Field Mapping configuration needs to be completed for managing the "Transaction creation status (tc9_et__Transaction_Creation_Stage__c) field

Step 1: From the App Launcher (9 dots), Choose Object Mappings

"as an example, OFM-3, 41, 43 have been considered"

Step 2: Navigate to OFM-3 (Object Field Mapping-3)

Step 3: Navigate to the "Related" listing under OFM-3 and create a new mapping, OFM-41

Step 4: Self manage the Default Value field in OFM-43 and OFM-41 Based on the way 2c9 payroll synchronisation workflows need to run

• 1(OFM-41) = Submitted (OFM-43) (the Skedulo timesheet status = Approved, the 2c9 Timesheet Status = Approved, and the 2c9 Transaction Creation status = Ready)

As a Scheduler:

• No changes in the existing process.
• Schedulers will continue to approve the Skedulo timesheets as Normal

As a Payroll Officer

• No changes in the existing process.
• If the Transaction creation status =1, there may be background synchronisation workflows that will be running to create and submit the transactions within 2c9 payroll system

Enhancement 2 - Flexibility in managing Travel Allowances

An improvement in the design around managing travel allowances with adherence to the Australian Taxation office allowance calculation rules

Previously existing code logic:

• Skedulo Timesheet Approval with a Travel allowance was a hard coded logic within the Package design where the relevant 2c9 payroll allowance parameter was required to be "Travel"

Current Code Logic Fix:

• The travel allowance logic calculation has been moved to meta data settings outside of the package thereby providing flexibility around changes based on ATO regulations around Travel Allowance.

Instructions:

As an Administrator (SF Administrator):

• Navigate to Custom Meta Data section in the Settings area

• Select "SAGE Integration Additional Settings Option from the list", click "Manage"

• Configure the Custom Meta Data setting exactly same as defined within the 2c9 Payroll system "Pay Code" object, "ATO Allowance Type Field"
  • Example:
    • If the ATO Allowance Type = "Car" in the "Pay Code Object"
    • Then: The Meta Data Setting should also be set to "Car"

As a Scheduler:

• No changes in the existing process.
• Schedulers will continue to approve the Skedulo timesheets containing Travel, Transport Allowance components as Normal.

As a Mobile Resource (Support Worker):

• No changes in the existing process.
• To continue to use the Travel & Transport form as normal

Enhancement 3 - Leave Events with Project Codes and/or Interpretation Variation

An improvement in the design to include Project codes in the leave events for accurate payment processing to employees.

Previously existing code logic:

• A leave event was being created as part of the Job that had a conflict with an approved unavailability (leave) but the leave event did not replicate the "Project Code" OR/AND "Interpretation Rule" that drives elevated payment rules.

Current Code Logic Fix:

• if a Job was created with a "Project Code: OR/AND "Interpretation Rule" and conflicts with an approved unavailability (leave), then the leave event created will always entail the project code previously associated with the de-allocated job

Instructions:

As an Administrator (SF Administrator):

• Install the Package v1.58
• Amend the Leave event Page layout to include the Project Code custom formula  and Interpretation Rule field

As a Scheduler:

• Schedule a Job with the Project code as normal
• Approve an Unavailability (Leave) request as normal that conflicts with the Job scheduled
• Check if the Leave event is created under the "Related" section of the Resource
• Check that the Leave event has the Project code that was previously existing on the Job
• Approve the Skedulo timesheet as normal
• Check if there an automated 2c9 Payroll system timesheet created based on the existing timesheet integration logic

As a Payroll Officer:

• Check that the 2C9 Timesheet generated has the Leave Shift correctly available with Leave Type, Project Code fields populated
• Process the 2c9 Payroll Timesheet as normal
• Check that the Leave shift timesheet entry is correctly handled with the rates associated to the Leave Rule and the Project Code.

Enhancement 3 - Timesheet Approval error management

Background:

During the process of Skedulo Timesheet approval, there have been instances where the system errors with 101 SOQL error preventing the successful approval and data send to 2c9 payroll smoothly. A manual workaround enhancement has been provided in this release to prevent the error.

Instructions:

As a Salesforce Administrator (one off activity)

1. Log on to the relevant Salesforce environment and open the "Developer Console"

2. Navigate to the "Debug" menu and select "Open Execute Anonymous execute window"

3. Paste the code detailed below and hit "Execute

List<String> timesheetIds = new List<String>{'a453h000000QvbMAAS'}; 2skedsg.skedApproveTimesheetBatch batch = new skedsg.skedApproveTimesheetBatch(timesheetIds); 3Database.executeBatch(batch);