> ## Documentation Index > Fetch the complete documentation index at: https://documentation.2cloudnine.com/llms.txt > Use this file to discover all available pages before exploring further. # Banksia Release Upgrade Guide export const InlineImage = ({src, alt = "", height = "1.6em"}) => { return {alt}; }; ### Overview | **Release:** | Banksia ‘21 | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Version:** | v1.160 | | **Release Date:** | 26/07/2021 | | **Packages updated:** | | ## Important Information Only your authorised Salesforce System Administrator or Partner should be actioning any installation, configuration items and tasks. All packages within the release must be installed. There may be compulsory and optional configuration items and tasks that need to be completed pre and post the installation of the packages. These will be highlighted in the below checklists, with further details given within this document. The installer will be responsible for ensuring all these configuration items and tasks are completed within a reasonable timeframe of the packages being installed. Please ensure you have familiarised yourself with all of the requirements PRIOR to installing the packages and ensure you have sufficient time and resources available. Failing to do so can negatively impact the User experience and stability of 2cloudnine Payroll. This guide should always be opened and used via your web browser. This will ensure you are viewing the most recent version of the document. Further, downloading the document and opening it with desktop programs, such as Adobe, has been found to cause errors when copying and using the scripts provided for data updates. These errors do not occur when viewed through a browser. ## Pre-Installation Checklist The following items are highly recommended to be completed prior to commencing the installation and configuration of packages within this release. | | Configuration Item / Task | Requirement? | | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | ------------ | | [New Component Review](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#new-component-review) | | | | | Remove / rename duplicate objects | **Optional** | | | Remove / rename duplicate record types | **Optional** | | | Remove / rename duplicate fields | **Optional** | ## Installation and Configuration Checklist The following items must be completed in the listed order to install and configure the packages within this release. | | Configuration Item / Task | Requirement? | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------- | | Package Installation | | | | | Install 2cloudnine Payroll v1.160 | **Compulsory**Update | | | Install 2cloudnine Payroll Time2Pay Extension v1.99 | **Compulsory**Update | | | Install 2cloudnine Payroll Communities / Experience Extension v1.43 | **Compulsory**Update | | | Install 2cloudnine Payroll Australia Extension v1.60 | **Optional**Update | | [Create and Allocate Work Schedules Efficiently](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#create-and-allocate-work-schedules-efficiently) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Add lightning web components to lightning record page(s) | **Optional** | | [Apply Work Schedule Information to Payroll](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#apply-work-schedule-information-to-payroll) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Create a new picklist value for field(s) | **Optional** | | [Introduction of the Work Schedule Manager](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#introduction-of-the-work-schedule-manager) | | | | | Update profile / permission sets | **Conditionally Compulsory** | | | Update page layouts for new field(s) | **Conditionally Compulsory** | | [Extend Work Schedules to Handle Half Day Leave Events](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#extend-work-schedules-to-handle-half-day-leave-events) | | | | | Update profile / permission sets | **Conditionally Compulsory** | | | Update page layouts for new field(s) | **Conditionally Compulsory** | | | Update Experience (Communities) Page Layouts for New Field(s) | **Optional** | | | Configuration Item / Task | Requirement? | | --- | --- | --- | | [Improvements for Publishing and Unpublishing Work Schedules](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#improvements-for-publishing-and-unpublishing-work-schedules) | | | | | Update page layouts for new button(s) | **Conditionally Compulsory** | | | Update new field(s) on existing records | **Conditionally Compulsory** | | [Populate Default Values on Existing Timesheets From Work Schedules](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#populate-default-values-on-existing-timesheets-from-work-schedules) | | | | | Set new schedule job(s) | **Optional** | | [Meet Stapled Superannuation Legislative Requirements](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#meet-stapled-superannuation-legislative-requirements)New | | | | | Update page layouts for new button(s) | **Conditionally Compulsory** | | [New Deduction Calculation Type](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#new-deduction-calculation-type) | | | | | Create a new picklist value for field(s) | **Compulsory** | | [Customise the Payee Pay Batch’s Total Quantity Calculation](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#customise-the-payee-pay-batchs-total-quantity-calculation) | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | | Update new field(s) on existing records | **Compulsory** | | [Improved Overnight Interpretation Capability](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#improved-overnight-interpretation-capability) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update new field(s) on existing records | **Optional** | | [Define Alternative Pay Code for Saturday Frequency Breakpoints](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#define-alternative-pay-code-for-saturday-frequency-breakpoints) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update new field(s) on existing records | **Optional** | | | Configuration Item / Task | Requirement? | | --- | --- | --- | | [Ability to Override the ATO Income Classification Application](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#ability-to-override-the-ato-income-classification-application)New | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | | Create a new picklist value for field(s) | **Compulsory** | | [Define Opening Balances as Employer Additional Superannuation](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#define-opening-balances-as-employer-additional-superannuation)New | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | [View Key Information Directly From Payee Aggregate Records](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#view-key-information-directly-from-payee-aggregate-records)New | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | [General Updates to the Interpretation Builder Pages and Functionality](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#general-updates-to-the-interpretation-builder-pages-and-functionality) | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | | Confirm / Update New, Edit and Clone Button Configuration | **Compulsory** | | | Update Data for Existing Records | **Compulsory** | | [Custom Set the Owner of Pay Transactions Records](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#custom-set-the-owner-of-pay-transactions-records) | | | | | Update the Time2pay Ext main settings custom setting | **Optional** | | [Update to Timesheet related Pay Transactions for Payee Leave Events](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#update-to-timesheet-related-pay-transactions-for-payee-leave-events)New | | | | | Update new field(s) on existing records | **Compulsory** | | [Provide Greater Detail on Pay Advice Documents](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#provide-greater-detail-on-pay-advice-documents) | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Compulsory** | | | Update new field(s) on existing records | **Compulsory** | | | Configuration Item / Task | Requirement? | | --- | --- | --- | | [Provide Greater Detail on Invoice Documents](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#provide-greater-detail-on-invoice-documents) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update new field(s) on existing records | **Optional** | | [Provide greater detail on a Timesheet’s Invoice Backing Sheet](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#provide-greater-detail-on-a-timesheets-invoice-backing-sheet) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update new field(s) on existing records | **Optional** | | [Enable Bulk Delete of Timesheets](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#enable-bulk-delete-of-timesheets) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update new field(s) on existing records | **Optional** | | [Further Streamline Payee Allowance and Assignment Rate Updates](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#further-streamline-payee-allowance-and-assignment-rate-updates) | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Set New Scheduled job(s) | **Optional** | | [Update to Terminology Customisation of Experience](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#update-to-terminology-customisation-of-experience-communities)Update | | | | | Override / Translate Custom Labels | **Optional** | | [Control if Leave Credits Are Available in Experience (Communities)](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#control-if-leave-credits-are-available-in-experience-communities)New | | | | | Update profile / permission sets | **Compulsory** | | | Update page layouts for new field(s) | **Optional** | | | Update data for existing records | **Optional** | | | Configuration Item / Task | Requirement? | | --- | --- | --- | | [Define Experience (Communities) Access to Future Dated Timesheets](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#define-experience-communities-access-to-future-dated-timesheets)New | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update data for existing records | **Optional** | | [Automatically Update the Primary Payee on the Contact records](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#automatically-update-the-primary-payee-on-the-contact-records)Update | | | | | Update profile / permission sets | **Optional** | | | Update page layouts for new field(s) | **Optional** | | | Update data for existing records | **Optional** | | [General Page Layout Updates to Payment Details and Pay Code](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#general-page-layout-updates-to-payment-details-and-pay-code) | | | | | Update page layouts to remove field(s) | **Compulsory** | | | Update page layouts to add / modify new field(s) | **Optional** | ## Installation Links The installation of the following packages must be completed as part of the Banksia ‘21 release upgrade. | Package | Version | Install Link | | ----------------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------- | | 2cloudnine Payroll | 1.160 Update | [Install package](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t6F000004DJjk) | | 2cloudnine Payroll Time2Pay Extension | 1.99 Update | [Install package](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t0o000002Zvjp) | | 2cloudnine Payroll Communities / Experience Extension | 1.43 Update | [Install package](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t2v000007XA83) | | 2cloudnine Payroll Australia Extension | V1.60 Update | [Install package](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t6F000004HCsk) | ## Pre-Installation Items ### New Component Review The Banksia ’21 release contains a number of new components including Objects, Fields and Buttons. A review of the list of components introduced should be conducted to check for Salesforce limits and duplicates of existing custom components. Please note for the Banksia release, there have been new lookup fields introduced on multiple objects. Full details for the lookup fields included can be found in [Appendix 1](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-1), however, the below table provides a per object summary. | Object | Number Of New Lookup Fields | | ----------------------------------------------------------------------------- | --------------------------- | | Assignment (tc9\_pr\_\_Assignment\_\_c) | 2 | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | 3 | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | 5 | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | 7 | | User (User) | 1 | Upon review of the lookups that already exist on this object in your organisation, if you find that you are going to exceed Salesforce limits, we suggest logging a case with Salesforce to have your organisation’s limit increased. In some instances, where duplicates exist, the installation / upgrade of the package will not be permitted. In these instances, the duplicates must be removed prior to attempting to install it. This could be completed through either deleting the custom component or, where possible, renaming the Name / API Name of the component. In other instances, the package installation / upgrade will be permitted, however, the duplicates could cause user confusion and/or custom automation clashes within the org. In these instances, although it is optional, it is highly recommended to delete / rename the component. When deleting a component, Salesforce does not permanently delete them for 15 days so although they are deleted for the user, they do still exist within the organisation. To remove the component completely, switch to classic view, which shows components that have not been permanently deleted, and delete it from there. A list of all the new components that should be reviewed are outlined in [Appendix 1](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-1) ## Configuration Items ### Create and Allocate Work Schedules Efficiently The functionality to create and allocate work schedules is optional and was released as a beta version in the Lilly Pilly ‘21 release. The non-beta version is now available. If the configuration of the beta version was already complete for the Lilly Pilly ‘21 Release, these items can be skipped The below configuration steps should be completed if the functionality is required: 1. Update profile / permission sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Add Lightning Web Components to lightning record page(s) (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 2](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-2) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) > Page Layouts 3. Select any page layout that is used for the Assignment Schedule object 4. Add the following field(s) to the layout * View Work Schedule Calendar (View\_Work\_Schedule\_Calendar\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Assignment Schedule object ### Add Lightning Web Components to lightning record page(s) Optional With the Work Schedule functionality, a new Lighting Web Component showing the Work Schedule Calendar, on a per Assignment basis has been provided. This can be added to Assignment Lightning Record pages as required. If not required, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Assignment (tc9\_pr\_\_Assignment\_\_c) > Lightning Record Pages 3. Select the required page layout 4. Click in the Clone / Edit button 5. Move the following Lightning Web Component onto the page * Assignment Work Schedule Calendar (tc9\_pr.Assignment\_Work\_Schedule\_Calendar) 6. Apply any component visibility settings / filters required 7. Click Save 8. Repeat steps 2 to 7 for all Lightning Record Pages on the Assignment object required ### Apply Work Schedule Information to Payroll The functionality to apply work schedule information to payroll is optional and was released as a beta version in the Lilly Pilly ‘21 release. The non-beta version is now available. If the configuration of the beta version was already complete for the Lilly Pilly ‘21 Release, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Create a new picklist value for field(s) (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 3](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-3) must be made available for use either via profiles or custom permission sets. Note: This functionality builds on the Create and Allocate Work Schedules Efficiently. To function correctly, the Update Profile / Permission Sets items within that section must also be completed. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) > Page Layouts 3. Select any page layout that is used for the Remuneration record type 4. Add the following field(s) to the layout * Auto Pay Calculation Basis (tc9\_pr\_\_Auto\_Pay\_Calculation\_Basis\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Remuneration record type 7. Return to the Object Manager 8. Select Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) > Page Layouts 9. Select any page layout that is used for the Payment or Allowance record types 10. Add the following field(s) to the layout * Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) 11. Click Save 12. Repeat steps 8 to 11 for all page layouts that are used for the Payment and Allowance record types 13. Return to the Object Manager 14. Select Timesheet Entry (tc9\_et\_\_Timesheet\_Entry\_\_c) > Page Layouts 15. Select any page layout that is used for the Timesheet Entry object 16. Add the following field(s) to the layout * Work Schedule Item (tc9\_pr\_\_Work\_Schedule\_Item\_\_c) 17. Click Save 18. Repeat steps 14 to 17 for all page layouts that are used for the Timesheet Entry object ### Create a New Picklist Value for Fields (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) > Fields & Relationships 3. Select the Pro Rata Method field (tc9\_pr\_\_Pro\_Rata\_Method\_\_c) 4. In the values section, click the New button 5. On the displayed page add the new value ‘Work Schedule’ and apply it only for the Remuneration record type (See Figure 1) 6. Click Save Screenshot from 2cloudnine Payroll v1.153 Banksia Release Upgrade Guide ### Introduction of the Work Schedule Manager The functionality to use the Work Schedule Manager is optional, however, if the optional Work Schedules functionality introduced in the Lilly Pilly ‘21 release is in use, the below configuration steps must be completed: 1. Update profile / permission Sets (Conditionally Compulsory) 2. Update page layouts for new field(s) (Conditionally Compulsory) ### Update Profile / Permission Sets (Conditionally Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 4](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-4) must be made available for use either via profiles or custom permission sets. Note: This functionality builds on Create and Allocate Work Schedules Efficiently. To function correctly, the Update Profile / Permission Sets items within that section must also be completed. ### Update Page Layouts for New Field(s) (Conditionally Compulsory) This requirement needs to be completed regardless of whether the option to use the functionality is taken. 1. Go to Setup > Object Manager 2. Select Schedule (tc9\_pr\_\_Schedule\_\_c) > Page Layouts 3. Select any page layout that is used for the Work Schedule record type\* 4. Add the following field(s) to the layout: * Work Schedule Manager (tc9\_pr\_\_Work\_Schedule\_Manager\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Work Schedule record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. In addition to the above, the Work Schedule Manager (launch) field can be added to the list view and related lists as required. ### Extend Work Schedules to Handle Half Day Leave Events The functionality to allow work schedules to handle half day leave events is optional, however, if the optional Work Schedules functionality introduced in the Lilly Pilly ‘21 release is in use, the below configuration steps must be completed: 1. Update profile / permission Sets (Conditionally Compulsory) 2. Update page layouts for new field(s) (Conditionally Compulsory) 3. Update Experience(Communities) page layouts for new field(s) (Optional) ### Update Profile / Permission Sets (Conditionally Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 5](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-5) must be made available for use either via profiles or custom permission sets. Note: This functionality builds on Create and Allocate Work Schedules Efficiently and Apply Work Schedule Information to Payroll. To function correctly, the Update Profile / Permission Sets items within these sections must also be completed. ### Update Page Layouts for New Field(s) (Conditionally Compulsory) This requirement needs to be completed regardless of whether the option to use the functionality is taken. 1. Go to Setup > Object Manager 2. Select Payee Leave Event (tc9\_pr\_\_Payee\_Leave\_Event\_\_c) > Page Layouts 3. Select any page layout that is used for the Leave Take record type\* 4. Add the following field(s) to the layout: * Part Day Override (tc9\_pr\_\_Part\_Day\_Override\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Leave Take record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update Experience (Communities) Page Layouts for New Field(s) (optional) Making the below field available on the Employee and Approver Experience / Communities is optional. This requirement only needs to be completed if the option is taken to make the functionality available to Experience (Communities) users. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Payee Leave Event (tc9\_pr\_\_Payee\_Leave\_Event\_\_c) > Page Layouts 3. Select any page layout that is used by the Community Profile for the Leave Take record type 4. Add the following field(s) to the layout: * Part Day Override (tc9\_pr\_\_Part\_Day\_Override\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used by the Community Profile for the Leave Take record type ### Improvements for Publishing and Unpublishing Work Schedules The functionality to enable users to Publish and Unpublish Work Schedule records is optional, however, if the optional Work Schedules functionality introduced in the Lilly Pilly ‘21 release is in use, the below configuration steps must be completed: 1. Update page layouts for new button(s) (Conditionally Compulsory) 2. Update new field(s) on existing records (Conditionally Compulsory) ### Update Page Layouts for New Button(s) (Conditionally Compulsory) This requirement needs to be completed if the optional Work Schedules functionality introduced in the Lilly Pilly ‘21 release is in use. 1. Go to Setup > Object Manager 2. Select Schedule (tc9\_pr\_\_Schedule\_\_c) > Page Layouts 3. Select any page layout that is used for the Work Schedule record type\* 4. Add the following button(s) to the layout * Unpublish (tc9\_pr.Unpublish\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Work Schedule record type. \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update new field(s) on existing records (Conditionally Compulsory) To prevent validation errors while publishing Work Schedules and processing payroll, the Work Schedule Publish From (tc9\_pr\_\_Work\_Schedule\_Published\_From\_\_c) cannot be earlier than the Work Schedule Start Date (tc9\_pr\_\_Work\_Schedule\_Start\_Date\_\_c). Existing Work Schedule records will need to be updated to ensure they meet these validation requirements. ### Populate Default Values on Existing Timesheets From Work Schedules The functionality to update existing Timesheets with the values held on Work Schedules is optional, however, if the optional Work Schedules functionality introduced in the Lilly Pilly ‘21 release is in use for Timesheet generation, the below configuration steps must be completed: 1. Set new schedule job(s) (Optional) ### Set New Scheduled Job(s) (Optional) Confirm that there are existing scheduled jobs to Generate Timesheets. If not, run Script 1 defined below through the Developer Console Execute Anonymous Window to set the required scheduled jobs. ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Schedule Generate Timesheet Schedule Job System.schedule('ScheduleGenerateTimesheetsBatch 05', '0 05 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); System.schedule('ScheduleGenerateTimesheetsBatch 15', '0 15 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); System.schedule('ScheduleGenerateTimesheetsBatch 25', '0 25 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); System.schedule('ScheduleGenerateTimesheetsBatch 35', '0 35 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); System.schedule('ScheduleGenerateTimesheetsBatch 45', '0 45 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); System.schedule('ScheduleGenerateTimesheetsBatch 55', '0 55 * * * ?', new tc9_et.ScheduleGenerateTimesheetsBatch()); ``` ### Meet Stapled Superannuation Legislative Requirements New Although the requirement to meet Stapled Super requirements is legislative, the use of the Stapled Super functionality provided within 2cloudnine Payroll is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. 1. Update page layouts for new button(s)(Optional) ### Update Page Layouts for New Button(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Payee (tc9\_pr\_\_Payee\_\_c) > Page Layouts 3. Select any page layout that is used for the Payee record type\* 4. Add the following button(s) to the layout * Stapling Super (tc9\_eau\_Super\_Stapling\_\_c) - this button can be found in the Mobile & Lightning Actions section 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payee record type. * Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### New Deduction Calculation Type The functionality to utilise extended deduction rate type calculations is compulsory, and all the below configuration steps must be completed: 1. Create a new picklist value for field (Compulsory) ### Create a New Picklist Value For Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Object Manager 2. Select Payee Deduction Template (tc9\_pr\_\_Payee\_Deduction\_Template\_\_c) > Fields & Relationships 3. Select the Deduction Rate Type field (tc9\_pr\_\_Deduction\_Rate\_Type\_\_c) 4. In the values section, click the New button 5. On the displayed page add the new value ‘Percentage of Taxable Gross’ 6. Click Save 7. Return to Object Manager 8. Select Payee Deduction Record (tc9\_pr\_\_Payee\_Deduction\_Record\_\_c) > Fields & Relationships 9. Select the Deduction Rate Type field (tc9\_pr\_\_Deduction\_Rate\_Type\_\_c) 10. In the values section, click the New button 11. On the displayed page add the new value ‘Percentage of Taxable Gross’ and apply it for all available deduction record types (See Figure 1) 12. Click Save Screenshot from 2cloudnine Payroll v1.153 Banksia Release Upgrade Guide ### Customise the Payee Pay Batch’s Total Quantity Calculation The functionality to customise the Payee Pay Batch’s Total Quantity calculations is compulsory and all the below configuration steps must be completed: 1. Update profile / permission Sets (Compulsory) 2. Update page layouts for new field(s) (Compulsory) 3. Update new field(s) on existing records (Compulsory) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 6](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-6) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Compulsory) This requirement must be completed: 1. Go to Setup > Object Manager 2. Select Pay Code (tc9\_pr\_\_Pay\_Code\_\_c) > Page Layouts 3. Select any page layout that is used for the Payment, Allowance, Expense, ETP or Lump Sum record types\* 4. Add the following field(s) to the layout * Contributes to Total Quantity (tc9\_pr\_\_Contributes\_to\_Total\_Quantity\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payment, Allowance, Expense, ETP and Lump Sum record types \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Compulsory) To prevent validation errors while creating / editing Pay Codes and processing payroll, the new Contributes to Total Quantity (tc9\_pr\_\_Contributes\_to\_Total\_Quantity\_\_c) must be populated on all current Pay Codes. To update the field the following steps should be followed: 1. Run Script 1 defined below through the Developer Console Execute Anonymous Window to automatically populate the Contributes to Total Quantity field on all Payment Pay Codes to be True (checked) 2. Manually edit any Payment Pay Codes that require different values than those set by the script. Manually edit any Allowance, Expense FBT and Lump Sum Pay Codes that should be included in the Total Quantity to be True (checked) ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Pay Code - Contributes to Total Quantity List payCodes = [ Select Id, tc9_pr\_\_Contributes_to_Total_Quantity\_\_c from tc9_pr\_\_Pay_Code\_\_c WHERE RecordType.DeveloperName = 'Payment' ]; for (tc9_pr\_\_Pay_Code\_\_c payCode : payCodes) { payCode.tc9_pr\_\_Contributes_to_Total_Quantity\_\_c = true; } update payCodes; ``` ### Improved Overnight Interpretation Capability The functionality to allow improved interpretation logic for overnight shifts is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission Sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 7](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-7) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) > Page Layouts 3. Select any page layout that is used for the Shift Start Time, Shift End Time or Interpretation Variation Rule record types\* 4. Add the following field(s) to the layout * Overnight Based on Shift Start Range (tc9\_et\_\_Overnight\_Based\_on\_Shift\_Start\_Range\_\_c) * Overnight Based on Majority of Shift? (tc9\_et\_\_Overnight\_Based\_on\_Majority\_of\_Shift\_\_c) * Overnight Weekday Shift Starting from (tc9\_et\_\_Overnight\_Weekday\_Shift\_Starting\_from\_\_c) * Overnight Monday Shift Starting from (tc9\_et\_\_Overnight\_Monday\_Shift\_Starting\_from\_\_c) * Overnight Tuesday Shift Starting from (tc9\_et\_\_Overnight\_Tuesday\_Shift\_Starting\_from\_\_c) * Overnight Wednesday Shift Starting from (tc9\_et\_\_Overnight\_Wednesday\_Shift\_Starting\_from\_\_c) * Overnight Thursday Shift Starting from (tc9\_et\_\_Overnight\_Thursday\_Shift\_Starting\_from\_\_c) * Overnight Friday Shift Starting from (tc9\_et\_\_Overnight\_Friday\_Shift\_Starting\_from\_\_c) * Overnight Saturday Shift Starting from (tc9\_et\_\_Overnight\_Saturday\_Shift\_Starting\_from\_\_c) * Overnight Sunday Shift Starting from (tc9\_et\_\_Overnight\_Sunday\_Shift\_Starting\_from\_\_c) * Overnight PH Shift Starting from (tc9\_et\_\_Overnight\_Public\_Holiday\_Shift\_Starting\_from\_\_c) * Apply Overnight Majority Weekday (tc9\_et\_\_Apply\_Overnight\_Majority\_Weekday\_\_c) * Apply Overnight Majority Monday (tc9\_et\_\_Apply\_Overnight\_Majority\_Monday\_\_c) * Apply Overnight Majority Tuesday (tc9\_et\_\_Apply\_Overnight\_Majority\_Tuesday\_\_c) * Apply Overnight Majority Wednesday (tc9\_et\_\_Apply\_Overnight\_Majority\_Wednesday\_\_c) * Apply Overnight Majority Thursday (tc9\_et\_\_Apply\_Overnight\_Majority\_Thursday\_\_c) * Apply Overnight Majority Friday (tc9\_et\_\_Apply\_Overnight\_Majority\_Friday\_\_c) * Apply Overnight Majority Saturday (tc9\_et\_\_Apply\_Overnight\_Majority\_Saturday\_\_c) * Apply Overnight Majority Sunday (tc9\_et\_\_Apply\_Overnight\_Majority\_Sunday\_\_c) * Apply Overnight Majority Public Holiday (tc9\_et\_\_Apply\_Overnight\_Majority\_Public\_Holiday\_\_c) * Higher Rate Weekday (tc9\_et\_\_Higher\_Rate\_Weekday\_\_c) * Higher Rate Monday (tc9\_et\_\_Higher\_Rate\_Monday\_\_c) * Higher Rate Tuesday (tc9\_et\_\_Higher\_Rate\_Tuesday\_\_c) * Higher Rate Wednesday (tc9\_et\_\_Higher\_Rate\_Wednesday\_\_c) * Higher Rate Thursday (tc9\_et\_\_Higher\_Rate\_Thursday\_\_c) * Higher Rate Friday (tc9\_et\_\_Higher\_Rate\_Friday\_\_c) * Higher Rate Saturday (tc9\_et\_\_Higher\_Rate\_Saturday\_\_c) * Higher Rate Sunday (tc9\_et\_\_Higher\_Rate\_Sunday\_\_c) * Higher Rate Public Holiday (tc9\_et\_\_Higher\_Rate\_Public\_Holiday\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Shift Start Time, Shift End Time and Interpretation Variation Rule record types \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Optional) During timesheet interpretation, if you wish to utilise the new overnight functionality to define if an overnight shift should be paid at the following day’s rate based on when the shift starts, or if it will be paid based on the breakpoint that the majority of the hours fall within, you will need to update the relevant Interpretation Rules, via the Interpretation Builder, to provide the required information. ### Define Alternative Pay Code for Saturday Frequency Breakpoints The functionality to allow users to define alternate pay codes for Saturday frequency breakpoints is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission Sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 8](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-8) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) > Page Layouts 3. Select any page layout that is used for the Frequency Hours Breakpoint record type\* 4. Add the following field(s) to the layout * Saturday Pay Code (tc9\_et\_\_Saturday\_Pay\_Code\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Frequency Hours Breakpoint record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Optional) During timesheet interpretation, if you wish to utilise the new functionality and define a different rate to be paid for Saturdays when the actual hours are extended beyond normal frequency hours, you will need to update the relevant Interpretation Rules, via the Interpretation Builder, to add a Saturday Pay Code. ### Ability to Override the ATO Income Classification Application New The functionality to allow users to override the ATO Income Classification at an Opening Balance and Pay Transaction level is compulsory and all the below configuration steps must be completed: The below configuration steps will be completed by a 2cloudine Payroll consultant as scheduled: 1. Update profile / permission Sets (Compulsory) 2. Update page layouts for new field(s) (Compulsory) 3. Create a new picklist value for field(s) (Compulsory) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 9](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-9) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Object Manager 2. Select Payee Opening Balance (tc9\_pr\_\_Payee\_Opening\_Balance\_\_c) > Page Layouts 3. Select any page layout that is used for the Payee Opening Balance object\* 4. Add the following field(s) to the layout * ATO Income Classification (tc9\_pr\_\_ATO\_Income\_Classification\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payee Opening Balance object 7. Return to the Object Manager 8. Select Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) > Page Layouts 9. Select any page layout that is used for the Payment, Allowance, Expense, ETP or Lump Sum record types\* 10. Add the following field(s) to the layout * Override ATO Income Classification (tc9\_pr\_\_Override\_ATO\_Income\_Classification\_\_c) 11. Click Save 12. Repeat steps 9 to 11 Select for all page layout that is used for the Payment, Allowance, Expense, ETP or Lump Sum record types * Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Create a New Picklist Value for Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Objects and Fields > Picklist Value Sets 2. Select ATO Income Classification 3. Click the New button in the Values section 4. On the displayed page, add the new value Not Reportable 5. Check the “Add new picklist value sets to all record types that use this global value set” checkbox 6. Click Save ### Define Opening Balances as Employer Additional Superannuation New The functionality to allow users to define Opening Balances as Employer Additional Superannuation is compulsory and all the below configuration steps must be completed: The below configuration steps will be completed by a 2cloudine Payroll consultant as scheduled 1. Update profile / permission Sets (Compulsory) 2. Update page layouts for new field(s) (Compulsory) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 10](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-10) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Object Manager 2. Select Payee Opening Balance (tc9\_pr\_\_Payee\_Opening\_Balance\_\_c) > Page Layouts 3. Select any page layout that is used for the Withholding - Superannuation record type\* 4. Add the following field(s) to the layout * Employer Additional Super (tc9\_pr\_\_Employer\_Additional\_Super\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Withholding - Superannuation record type * Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### View Key Information Directly From Payee Aggregate Records New The functionality to allow users to view key information directly from the Payee Aggregate records is compulsory and all the below configuration steps must be completed: The below configuration steps will be completed by a 2cloudine Payroll consultant as scheduled 1. Update profile / permission Sets (Compulsory) 2. Update page layouts for new field(s) (Compulsory) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 11](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-11) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Object Manager 2. Select Payee Aggregate (tc9\_pr\_\_Payee\_Aggregate\_\_c) > Page Layouts 3. Select any page layout that is used for the Payee Aggregate object\* 4. Add the following field(s) to the layout * Employee (tc9\_pr\_\_Employee\_Name\_\_c) * Payment Entity (tc9\_pr\_\_Payment\_Entity\_\_c) * Pay Schedule (tc9\_pr\_\_Pay\_Schedule\_\_c) * Finalise Calendar Period (tc9\_pr\_\_Finalise\_Calendar\_Period\_\_c) * Pay Batch Type (tc9\_pr\_\_Pay\_Batch\_Type\_\_c) * Payment Date (tc9\_pr\_\_Payment\_Date\_\_c) * Maximum Payroll Date (tc9\_pr\_\_Maximum\_Payroll\_Date\_\_c) * Calculation Version (tc9\_pr\_\_Calculation\_Version\_\_c) * Leave Rule (tc9\_pr\_\_Leave\_Rule\_\_c) * Leave Type (tc9\_pr\_\_Leave\_Type\_\_c) * Date Time Finalised (tc9\_pr\_\_Date\_Time\_Finalised\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payee Aggregate object * Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### General Updates to the Interpretation Builder Pages and Functionality The general improvements to the Interpretation Builder pages and functionality are compulsory and all the below configuration steps must be completed: 1. Update profile / permission Sets (Compulsory) 2. Update page layouts for new field(s) (Compulsory) 3. Confirm / update new, edit and clone button configuration (Compulsory) 4. Update Data for Existing Records (Compulsory) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 12](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-12) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Compulsory) This requirement must be completed: 1. Go to Setup > Object Manager 2. Select Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) > Page Layouts 3. Select any page layout that is used for the Leave Breakpoint record type\* 4. Add the following field(s) to the layout 1. Leave Header (tc9\_et\_\_Leave\_Header\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Leave Breakpoint record type 7. Return to the Object Manager 8. Select Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) > Page Layouts 9. Select any page layout that is used for the Interpretation Rule object\* 10. Add the following field(s) to the layout 1. Variation Record Type (tc9\_et\_\_Variation\_Record\_Type\_\_c) 11. Click Save 12. Repeat steps 8 to 11 for all page layouts that are used for the Interpretation Rule object \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Confirm / Update New, Edit and Clone Button Configuration (Compulsory) The New, Edit and Clone buttons used on the Interpretation Rule object are configured to open the Interpretation Builder. Follow the below instructions to ensure the correct configuration is applied: 1. Go to Setup> Object Manager 2. Select Interpretation Rule (tc9\_et\_\_Interpretation\_ Rule\_\_c) > Buttons, Links and Actions 3. Navigate to the New button and select Edit 4. Ensure that the following values are defined * Salesforce Classic Override = No override (use default) * Lightning Experience Override = Lighting Component tc9\_et:AwardBuilder * Mobile Override = Lighting Component tc9\_et:AwardBuilder * Skip record type selection page = False 5. Click the Save button 6. Navigate to the Edit button and select Edit 7. Ensure that the following values are defined * Salesforce Classic Override = No override (use default) * Lightning Experience Override = Lighting Component tc9\_et:AwardBuilder * Mobile Override = Lighting Component tc9\_et:AwardBuilder 8. Click the Save button 9. Navigate to the Clone button and select Edit 10. Ensure that the following values are defined * Salesforce Classic Override = Visualforce page CloneInterpretation \[tc9\_et\_\_CloneInterpretation] 11. Click the Save button ### Update Data for Existing Records (Compulsory) Along with the improvements introduced with the Interpretation Builder, the updates included a change to how Leave Breakpoints are stored by the Interpretation Builders. Now, the Leave Header Breakpoint is stored in the relevant Leave Breakpoint via a lookup field. Although this update does not change the functionality for the user, to prevent errors occurring whilst modifying existing Interpretation Rules and/or during Timesheet Interpretation, the existing Interpretation Rules must have the correct Leave Header identified on the Leave Breakpoints. To check and update the data on existing records the following steps should be followed: 1. Run Script 1 defined below through the Developer Console Execute Anonymous Window to create any required Leave Header Interpretation Breakpoints 2. Run Script 2 defined below through the Developer Console Query Editor to confirm that there are no Leave Breakpoints that do not have an assigned Leave Header Breakpoint. 1. If the query returns no results, all records are updated. No further steps need to be completed 2. If the query returns 1 or more results, the records identified will need to be updated manually. Proceed to step 3 3. For each Interpretation Rule identified in Step 2, manually update by completing the following 1. Go to the Interpretation Rule > Leave Breakpoints 2. Identify the 2 Leave Breakpoints that match the following criteria 1. Record Type = Leave Breakpoint 2. Breakpoint Type = Leave Header 3. Leave Rule > Record Type = Annual Leave 3. Rename the identified records with a name that will make them easy to select in a lookup field 4. Return to the Interpretation Rule > Leave Breakpoints 5. Identify the Leave Breakpoints that match the following criteria 1. Record Type = Leave Breakpoint 2. Breakpoint Type contains Standard Leave 3. Leave Rule > Record Type = Annual Leave 6. Populate the Leave Header lookup field with a Leave Header identified in step b. All Standard Leave Breakpoints must be allocated to the same Leave Header 7. Return to the Interpretation Rule > Leave Breakpoints 8. Identify the Leave Breakpoints that match the following criteria 9. Record Type = Leave Breakpoint 1. Breakpoint Type contains Shift Leave 2. Leave Rule > Record Type = Annual Leave 3. Populate the Leave Header lookup field with the other Leave Header identified in step b. All Shift Leave Breakpoint must be allocated to the same Leave Header 4. Run Script 2 defined below through the Developer Console Query Editor again to confirm that all the required manual updates are complete. The query should return no results. If results are returned, repeat step 3 until there are no results returned ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Leave Header Interpretation Breakpoints Insert Map leaveRuleToLeaveHeaderMap = new Map(); for (tc9_et\_\_Interpretation_Breakpoint\_\_c leaveHeader : [ Select Id, tc9_et\_\_Leave_Rule\_\_c, tc9_et\_\_Interpretation_Rule\_\_c, tc9_et\_\_Interpretation_Variation_Rule\_\_c FROM tc9_et\_\_Interpretation_Breakpoint\_\_c WHERE tc9_et\_\_Breakpoint_Type\_\_c = 'Leave Header' ]) { leaveRuleToLeaveHeaderMap.put( leaveHeader.tc9_et\_\_Leave_Rule\_\_c + '-' + leaveHeader.tc9_et\_\_Interpretation_Rule\_\_c + '-' + leaveHeader.tc9_et\_\_Interpretation_Variation_Rule\_\_c, leaveHeader.Id ); } List leaveBreakpointsToUpdate = new List(); for (tc9_et\_\_Interpretation_Breakpoint\_\_c leaveBreakpoint : [ Select Id, tc9_et\_\_Leave_Rule\_\_c, tc9_et\_\_Interpretation_Rule\_\_c, tc9_et\_\_Interpretation_Variation_Rule\_\_c, tc9_et\_\_Leave_Header\_\_c FROM tc9_et\_\_Interpretation_Breakpoint\_\_c WHERE tc9_et\_\_Breakpoint_Type\_\_c != 'Leave Header' AND RecordType.DeveloperName = 'Leave_Breakpoint' AND tc9_et\_\_Leave_Header\_\_c = null ]) { String leaveHeaderKey = leaveBreakpoint.tc9_et\_\_Leave_Rule\_\_c + '-' + leaveBreakpoint.tc9_et\_\_Interpretation_Rule\_\_c + '-' + leaveBreakpoint.tc9_et\_\_Interpretation_Variation_Rule\_\_c; if (leaveRuleToLeaveHeaderMap.containsKey(leaveHeaderKey)) { leaveBreakpoint.tc9_et\_\_Leave_Header\_\_c = leaveRuleToLeaveHeaderMap.get(leaveHeaderKey); leaveBreakpointsToUpdate.add(leaveBreakpoint); } } if (!leaveBreakpointsToUpdate.isEmpty()) { update leaveBreakpointsToUpdate; } ``` ```sql Script 2 theme={null} SELECT Id, tc9_et\_\_Leave_Rule\_\_c, tc9_et\_\_Interpretation_Rule\_\_c, tc9_et\_\_Interpretation_Variation_Rule\_\_c, tc9_et\_\_Leave_Header\_\_c FROM tc9_et\_\_Interpretation_Breakpoint\_\_c WHERE tc9_et\_\_Breakpoint_Type\_\_c != 'Leave Header' AND RecordType.DeveloperName = 'Leave_Breakpoint' AND tc9_et\_\_Leave_Header\_\_c = null ``` ### Custom Set the Owner of Pay Transactions Records The functionality to assign specific users as Pay Transaction record Owners is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update the Time2pay Ext Main Settings custom setting (Optional) ### Update the Time2pay Ext Main Settings Custom Setting (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Custom Setting 2. Locate the Time2pay Ext Main Settings custom setting and click on the Manage link alongside it 3. Click the Edit button 4. Populate the Record Owner by choosing one of the following 3 values: * Default When set to Default or the custom setting is left blank, the default Owner is set as the user who created the Pay Transaction records. * Client When set to Client, the Owner is set as the Account Owner of the Client record that is related to the Assignment. If the Client record Account Owner is blank, then the Default Owner defined above will apply. * Assignment When set to an Assignment, the Owner is set as the Owner of the Assignment record. If the Assignment record Owner is blank, then the Default Owner defined above will apply. 5. Click Save ### Update to Timesheet related Pay Transactions for Payee Leave Events New The feature of populating the Payee Leave Event field on the Pay Transaction with the value on the related Timesheet Entry is compulsory and all the below configuration steps must be completed: 1. Update new field(s) on existing records (Compulsory) ### Update New Field(s) on Existing Records (Compulsory) To populate the Payee Leave Event field on existing Pay Transactions with the values defined in the related Timesheet Entry record, you will need to run the below script as mentioned. The update provided to populate the Payee Leave Event field on the Pay Transactions record will occur as they are created. Existing Pay Transaction records will need to be updated to ensure there is no missing data in the future. To update the field, the following steps should be followed: 1. Run Script 1 defined below through the Developer Console Execute Anonymous Window to automatically update the *Payee Leave Event* on the *Pay Transaction* from the *Timesheet Entry* ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Pay Transactions - Payee Leave Event List paytrans = [ Select Id, tc9_pr\_\_Payee_Leave_Event\_\_c, tc9_pr\_\_Payee_Leave_Rule\_\_c, tc9_et\_\_Timesheet_Entry\_\_c, tc9_et\_\_Timesheet_Entry\_\_r.tc9_et\_\_Payee_Leave_Event\_\_c from tc9_pr\_\_Pay_Transaction\_\_c where tc9_et\_\_X2cloudnine_Time2Pay_Generated\_\_c = true and tc9_pr\_\_Payee_Leave_Rule\_\_c != null and tc9_pr\_\_Status\_\_c = 'New' ]; for (tc9_pr\_\_Pay_Transaction\_\_c paytran : paytrans) { if (paytran.tc9_pr\_\_Payee_Leave_Event\_\_c != null) { paytran.tc9_pr\_\_Payee_Leave_Event\_\_c = paytran.tc9_et\_\_Timesheet_Entry\_\_r.tc9_et\_\_Payee_Leave_Event\_\_c; paytran.tc9_pr\_\_Payee_Leave_Rule\_\_c = null; } } update paytrans; ``` ### Provide Greater Detail on Pay Advice Documents The feature of enabling users to split casual loading and penalty loading Pay Transactions separately on Pay Advice records is optional, however, there is a required configuration regardless of if the function is used. The below configuration steps must be completed: 1. Update profile / permission sets (Compulsory) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Compulsory) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access If the packaged permission sets are not used within the organisation, the access outlined in [Appendix 13](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-13) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts For New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality, or the functionality to Provide Greater Detail on Invoice Documents, is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) > Page Layouts 3. Select any page layout that is used for the Hourly Rates, Shift Start Time, Shift End Time or Interpretation Variation Rule record types\* 4. Add the following fields to the layout * Apply Casual Loading (Apply\_Casual\_Loading\_\_c) * Apply Penalty Loading (Apply\_Penalty\_Loading\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Hourly Rates, Shift Start Time, Shift End Time and Interpretation Variation Rule record types 7. Return to the Object Manager 8. Select Interpretation Breakpoints (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) > Page Layouts 9. Select any page layout that is used for the Interpretation Breakpoints object excluding those used for the Allowance and Pay Code Cap record types\* 10. Add the following fields to the layout * Casual Loading Pay Code (tc9\_et\_\_Casual\_Loading\_Pay\_Code\_\_c) * Penalty Loading Pay Code (tc9\_et\_\_Penalty\_Loading\_Pay\_Code\_\_c) 11. Click Save 12. Repeat steps 9 to 11 for all page layouts that are used for the Interpretation Breakpoint object excluding those used for the Allowance and Pay Code Cap record types \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Compulsory) With the introduction of the functionality to display casual loading, penalty loading and/or leave loading as separate lines on a Pay Advice, a change was made to where leave loading information is stored by the Interpretation Builders. Previously, this was stored on leave loading breakpoints. Now, leave loading information will be stored on the standard leave breakpoints. Although this update does not change the functionality for the user, to prevent errors occurring during timesheet interpretation, the existing Interpretation Rules must have the leave loading updated to be held on the correct breakpoints. Furthermore, to use the functionality, any relevant Interpretation Rules will need to be updated via the Interpretation Builder to define the additional pay codes required for the casual loading and/or penalty loading pay transactions. To update the fields, the following steps should be followed: 1. Run Script 1 defined below through the Developer Console Execute Anonymous Window to automatically transfer the Leave Loading information from the Leave Loading Breakpoint to the Leave Breakpoint, and delete the existing Leave Loading Breakpoints 2. Manually edit any Interpretation Rules, via the Interpretation Builder, to define the additional pay codes required for the casual loading, penalty loading and/or leave loading pay transactions ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Interpretation Rule - Leave Loading Breakpoints List lstStdLeaveBps = new List(); List lstStdLeaveLoadingBps = [ Select Id, tc9_et\_\_Interpretation_Rule\_\_c, tc9_et\_\_Interpretation_Variation_Rule\_\_c, tc9_et\_\_Leave_Rule\_\_c, tc9_et\_\_Breakpoint_Type\_\_c, tc9_et\_\_Pay_Code\_\_c FROM tc9_et\_\_Interpretation_Breakpoint\_\_c WHERE tc9_et\_\_Breakpoint_Type\_\_c LIKE '%Leave Standard Loading%' ]; Map leaveLoadingMap = new Map(); if (lstStdLeaveLoadingBps != null && lstStdLeaveLoadingBps.size() > 0) { for (tc9_et\_\_Interpretation_Breakpoint\_\_c stdLeaveLoadingBp : lstStdLeaveLoadingBps) { String leaveKey = stdLeaveLoadingBp.tc9_et\_\_Breakpoint_Type\_\_c .replace('Leave Standard Loading', 'Leave Standard Leave') + '-' + stdLeaveLoadingBp.tc9_et\_\_Interpretation_Rule\_\_c + '-' + stdLeaveLoadingBp.tc9_et\_\_Interpretation_Variation_Rule\_\_c + '-' + stdLeaveLoadingBp.tc9_et\_\_Leave_Rule\_\_c; leaveLoadingMap.put(leaveKey, stdLeaveLoadingBp.tc9_et\_\_Pay_Code\_\_c); } for (tc9_et\_\_Interpretation_Breakpoint\_\_c stdLeaveBp : [ Select Id, tc9_et\_\_Interpretation_Rule\_\_c, tc9_et\_\_Interpretation_Variation_Rule\_\_c, tc9_et\_\_Leave_Rule\_\_c, tc9_et\_\_Breakpoint_Type\_\_c, tc9_et\_\_Pay_Code\_\_c, tc9_et\_\_Leave_Loading_Pay_Code\_\_c FROM tc9_et\_\_Interpretation_Breakpoint\_\_c WHERE tc9_et\_\_Breakpoint_Type\_\_c LIKE '%Leave Standard Leave%' ]) { String leaveKey = stdLeaveBp.tc9_et\_\_Breakpoint_Type\_\_c + '-' + stdLeaveBp.tc9_et\_\_Interpretation_Rule\_\_c + '-' + stdLeaveBp.tc9_et\_\_Interpretation_Variation_Rule\_\_c + '-' + stdLeaveBp.tc9_et\_\_Leave_Rule\_\_c; if (leaveLoadingMap.containsKey(leaveKey)) { stdLeaveBp.tc9_et\_\_Leave_Loading_Pay_Code\_\_c = leaveLoadingMap.get(leaveKey); lstStdLeaveBps.add(stdLeaveBp); } } if (!lstStdLeaveBps.isEmpty()) { update lstStdLeaveBps; } delete lstStdLeaveLoadingBps; } ``` ### Provide Greater Detail on Invoice Documents The feature of enabling users to split casual loading and penalty loading pay transactions separately on Invoice records is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Optional) Please note this item builds on the configuration specified in the Provide Greater Detail on Pay Advice Documents section above. Configuration for these items must also be completed should the option to use this functionality be required. ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 14](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-14) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts For New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Invoice Setting (tc9\_et\_\_Invoice\_Setting\_\_c) > Page Layouts 3. Select any page layout that is used for the Payroll Items record type\* 4. Add the following fields to the layout * Split Loading Pay Transactions (tc9\_et\_\_Split\_Loading\_Pay\_Transactions\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payroll Items record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Optional) For users to utilise this option to display casual loading or penalty loading as separate lines on the client invoice documents, the relevant Invoice Settings will need to have the new Split Loading Pay Transactions field (tc9\_et\_\_Split\_Loading\_Pay\_Transactions\_\_c) set to ‘Yes’. ### Provide Greater Detail on a Timesheet’s Invoice Backing Sheet The functionality to allow greater details on a Timesheet’s invoice backing sheet is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission Sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access * 2cloudnine Time2Pay Standard Online Invoice permission set To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 15](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-15) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Invoice Setting (tc9\_et\_\_Invoice\_Setting\_\_c) > Page Layouts 3. Select any page layout that is used for the Payroll Items record type\* 4. Add the following field(s) to the layout * Enable Full Approval History (tc9\_et\_\_Enable\_Full\_Approval\_history\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payroll Items record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Optional) To display the entire history of the Timesheet entry record, the Enable Full Approval History field must be set to “Yes” in the Invoice Settings record. Any Invoice Setting that requires this should be updated directly via the standard record page. ### Enable Bulk Delete of Timesheets The functionality to allow employees to bulk delete Timesheets and their related records from the *Assignment* record is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission Sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update new field(s) on existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 16](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-16) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Assignment (tc9\_pr\_\_Assignment\_\_c) > Page Layouts 3. Select any page layout that is used for the Assignment object excluding those used for the Employee, Perm and Temp to Perm record types 4. Add the following fields to the layout * Allow Delete Approved Timesheets (tc9\_et\_\_Allow\_Delete\_Approved\_Timesheets\_\_c) * Allow Delete Submitted Timesheets (tc9\_et\_\_Allow\_Delete\_Submitted\_Timesheets\_\_c) 5. Add the following Action (under the Mobile & Lightning Action options) to the layout * Bulk Delete Timesheets and Related Records (tc9\_et.Bulk\_Delete\_Timesheets\_and\_Related\_Records) 6. Click Save 7. Repeat steps 3 to 6 for all page layouts that are used for the Assignment object excluding those used for the Employee, Perm and Temp to Perm record types \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update New Field(s) on Existing Records (Optional) To utilise bulk delete functionality to delete Submitted or Approved timesheets and their related records, the Allow Delete Submitted Timesheets and/or Allow Delete Approved Timesheets fields (tc9\_et\_\_Allow\_Delete\_Submitted\_Timesheets\_\_c and tc9\_et\_\_Allow\_Delete\_Approved\_Timesheets\_\_c respectively) on the related Assignment must be set as “Yes”. Existing Assignment records can be updated to have these fields set to “Yes". However, it is recommended that they are left blank or as “No” and the fields are populated on a case by case basis at the time a bulk delete is required, to prevent submitted and approved timesheets from being deleted in error. ### Further Streamline Payee Allowance and Assignment Rate Updates The functionality to use the extended version of Payee Allowance, Assignment Rate and Minimum Pay Rate Automation is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission Sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Set up new scheduled job(s) (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 17](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-17) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Minimum Pay Rate (tc9\_et\_\_Minimum\_Pay\_Rate\_\_c) > Page Layouts 3. Select any page layout that is used on the Minimum Pay Rate object 4. Add the following field(s) to the layout 1. Has Pending Assignment to be Processed (tc9\_et\_\_Has\_Pending\_Assignment\_to\_be\_processed\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Minimum Pay Rate object 7. Return to the Object Manager 8. Select Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) > Page Layouts 9. Select any page layout that is used on the Assignment Rate object\* 10. Add the following field(s) to the layout 1. Has Pending Assignment to be Processed (tc9\_et\_\_Has\_Pending\_Assignment\_to\_be\_processed\_\_c) 11. Click Save 12. Repeat steps 8 to 11 for all page layouts that are used for the Assignment Rate object 13. Return to the Object Manager 14. Select Assignment (tc9\_pr\_\_Assignment\_\_c) > Page Layouts 15. Select any page layout that is used for the Temp record type\* 16. Add the following field(s) to the layout 1. Has Pending Assignment Rate Temp Group (tc9\_et\_\_Has\_Pending\_Assignment\_Rate\_Temp\_Group\_\_c) 2. Has Pending Min Pay Rate (tc9\_et\_\_Has\_Pending\_Min\_Pay\_Rate\_\_c) 3. Has Pending Payee Allowance Temp Group (tc9\_et\_\_Has\_Pending\_Payee\_Allowance\_Temp\_Group\_\_c) 17. Add the following button(s) to the layout * Assignment Rate Automation (tc9\_et.Assignment\_Rate\_Automation) 18. Click Save 19. Repeat steps 15 to 18 for all page layouts that are used for the Temp record types Further to the above, a related list button has been introduced that can be added to any Assignment related list on the page layout that is required. 1. Go to Setup > Object Manager 2. Select the required Object (that is related to an Assignment (tc9\_pr\_\_Assignment\_\_c)) > Page Layouts 3. Select the required page layout\* 4. Add the following button(s) to the Assignment related list on the layout 1. Assignment Rate Automation (tc9\_et.Assignment\_Rate\_Automation\_List) 5. Click Save 6. Repeat steps 2 to 5 for all page layouts that require the related list button added. \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Set New Scheduled Job(s) (Optional) 1. Run Script 1 defined below through the Developer Console Execute Anonymous Window to set up a scheduled job for the Minimum Pay Rate Automation process ```java Script 1 theme={null} //Payroll post-install script for Banksia Release - Setting up the scheduled job for MPR Automation System.schedule('ScheduleMPRAutomation 01', '0 00 * * * ?', new tc9_et.ScheduleMPRAutomation()); System.schedule('ScheduleMPRAutomation 02', '0 10 * * * ?', new tc9_et.ScheduleMPRAutomation()); System.schedule('ScheduleMPRAutomation 03', '0 20 * * * ?', new tc9_et.ScheduleMPRAutomation()); System.schedule('ScheduleMPRAutomation 04', '0 30 * * * ?', new tc9_et.ScheduleMPRAutomation()); System.schedule('ScheduleMPRAutomation 05', '0 40 * * * ?', new tc9_et.ScheduleMPRAutomation()); System.schedule('ScheduleMPRAutomation 06', '0 50 * * * ?', new tc9_et.ScheduleMPRAutomation()); ``` ### Update to Terminology Customisation of Experience (Communities) The functionality to customise terminology used within Experience (Communities) is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Override / translate custom labels (Optional) ### Override / Translate Custom Labels (Optional) Update This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > User Interface > Custom Labels 2. On the displayed page, navigate to the Custom Label that needs to be overridden 3. Click on the Edit link along side the Custom Label 4. On the page that opens, scroll to the Local Translations / Overrides section and click on the New Local Translation button 5. Populate the required fields 6. Click Save 7. Repeat steps 2 to 6 until all overrides / translations required are completed The new / updated Custom Labels this release are as follows | Out of the Box Terminology | Associated Custom Label | | ---------------------------------------------- | ----------------------- | | BreakMin | CommBreak2Min | | Hours (used with Timesheet references) | commHours | | Hours (used with Payee Leave Event references) | commLeaveHours | | Total Hours | CommTotalHours | ### Control if Leave Credits Are Available in Experience (Communities) New The functionality to define if leave credits are available in Experience (Communities) is compulsory and all the below configuration steps must be completed: 1. Update profile / permission sets (Compulsory) 2. Update page layouts for new fields (Optional) 3. Update Data for Existing records (Optional) ### Update Profile / Permission Sets (Compulsory) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin (internal users) * 2cloudnine Time2Pay All Access (internal users) * Approver User Permission Set (approver users) To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 18](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-18) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Fields (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Leave Rule (tc9\_pr\_\_Leave\_Rule\_\_c) > Page Layouts 3. Select any page layout that is used for the Leave Rule object\* 4. Add the following field to the layout * Credit Available In Portal (tc9\_pr\_\_Credit\_Available\_in\_Portal\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Leave Rule object \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update Data for Existing Records (Optional) By default, where the value of the Credit Available In Portal field is not populated, it will be treated as if the value is “No” and therefore access to the functionality will not be granted to employees and approvers via Experience (Communities). However, if there are existing Leave Rules where the functionality is required, these should be edited via the standard Salesforce page. ### Define Experience (Communities) Access to Future Dated Timesheets New The functionality to define if future dated Timesheets are visible via Experience (Communities) is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 1. Update profile / permission sets (Optional) 2. Update page layouts for new field(s) (Optional) 3. Update data for existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 19](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-19) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Calendar (tc9\_pr\_\_Calendar\_\_c) > Page Layouts 3. Select a page layout that is used for any Timesheet Calendar record type\* 4. Add the following field(s) to the layout * No\_Days\_Future\_Timesheets\_Visible (tc9\_et\_\_No\_Days\_Future\_Timesheets\_Visible\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used by the Timesheet Calendar record type * Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update Data for Existing Records (Optional) If the functionality to provide access to future dated timesheets is required, existing Timesheet Calendars should have their No. Days Future Timesheets Visible (tc9\_et\_\_No\_Days\_Future\_Timesheets\_Visible\_\_c) field updated as required. ### Automatically Update the Primary Payee on the Contact Records The functionality to automatically populate the Primary Payee lookup on the Contact is standard functionality and will always apply. The use of the populated field is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 4. Update profile / permission sets (Optional) 5. Update page layouts for new field(s) (Optional) 6. Update data for existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 20](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-20) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 7. Go to Setup > Object Manager 8. Select Contact (tc9\_pr\_\_Contact\_\_c) > Page Layouts 9. Select a page layout that is used for any Employee record type\* 10. Add the following field(s) to the layout * Primary Payee Record (tc9\_pr\_\_Primary\_Payee\_Record\_\_c) 11. Click Save 12. Repeat steps 3 to 5 for all page layouts that are used by the Employee record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update Data for Existing Records (Optional) Update The update provided to populate the Primary Payee lookup field on the Contact record will occur when the Primary Payee field on a Payee record related to the Contact is populated / updated. Although it is not compulsory, we recommend updating the data on existing Contact records to ensure there is no missing data in the future. ### Automatically Update the Primary Payee on the Contact Records The functionality to automatically populate the Primary Payee lookup on the Contact is standard functionality and will always apply. The use of the populated field is optional. This requirement only needs to be completed if the option to use the functionality is taken. If not, these items can be skipped. The below configuration steps should be completed if the functionality is required: 7. Update profile / permission sets (Optional) 8. Update page layouts for new field(s) (Optional) 9. Update data for existing records (Optional) ### Update Profile / Permission Sets (Optional) The fields associated with this item have had read / edit access added to the following permission sets provided with the package. Where these are in use, the permissions required will be automatically provisioned. * 2cloudnine Payroll Admin * 2cloudnine Time2Pay All Access To use this optional functionality, if the packaged permission sets are not used within the organisation, the access outlined in [Appendix 19](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-19) must be made available for use either via profiles or custom permission sets. ### Update Page Layouts for New Field(s) (Optional) This requirement only needs to be completed if the option to use the functionality is taken. If not, this item can be skipped. 13. Go to Setup > Object Manager 14. Select Contact (tc9\_pr\_\_Contact\_\_c) > Page Layouts 15. Select a page layout that is used for any Employee record type\* 16. Add the following field(s) to the layout * Primary Payee Record (tc9\_pr\_\_Primary\_Payee\_Record\_\_c) 17. Click Save 18. Repeat steps 3 to 5 for all page layouts that are used by the Employee record type \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. ### Update Data for Existing Records (Optional) The update provided to populate the Primary Payee lookup field on the Contact record will occur when the Primary Payee field on a Payee record related to the Contact is populated / updated. Although it is not compulsory, we recommend updating the data on existing Contact records to ensure there is no missing data in the future. To update the data on existing records the following steps should be followed: 1. Run Script 1 defined below through the Developer Console Query Editor to establish how many records need to be updated. The number of rows returned is the number of records requiring the update. Note: There is a limit of 10,000 rows so if the query returns 10,000 rows then there is likely a higher number. 2. Run Script 2 defined below through the Developer Console Execute Anonymous Window to populate the Primary Payee lookup on the Contact record. Note: The script is limited to updating 1000 records at a time in order to avoid hitting Salesforce governor limits, therefore, the script may have to be run multiple times until all relevant Contacts are updated. The number of records identified in Step 1 can be used to determine how many times the script must be executed. 3. Run Script 1 defined below through the Developer Console Query Editor again to confirm that there are no records remaining that need to be updated. If the data is correct the query should return no results. ```sql Script 1 theme={null} SELECT Id, tc9_pr\_\_Primary_Record\_\_c, tc9_pr\_\_Employee\_\_c, tc9_pr\_\_Employee\_\_r.tc9_pr\_\_Primary_Payee_Record\_\_c FROM tc9_pr\_\_Payee\_\_c WHERE tc9_pr\_\_Primary_Record\_\_c = TRUE AND tc9_pr\_\_Employee\_\_r.tc9_pr\_\_Primary_Payee_Record\_\_c = null ``` ```java Script 2 theme={null} //Payroll post-install script for Banksia Release - Contact - Primary Payee List listOfEmployees = new List(); List payees = [ Select Id, tc9_pr\_\_Primary_Record\_\_c, tc9_pr\_\_Employee\_\_c, tc9_pr\_\_Employee\_\_r.tc9_pr\_\_Primary_Payee_Record\_\_c from tc9_pr\_\_Payee\_\_c WHERE tc9_pr\_\_Primary_Record\_\_c = TRUE AND tc9_pr\_\_Employee\_\_r.tc9_pr\_\_Primary_Payee_Record\_\_c = null Limit 1000 ]; for (tc9_pr\_\_Payee\_\_c payee : payees) { Contact employeeRec = new Contact(); employeeRec.Id = payee.tc9_pr\_\_Employee\_\_c; employeeRec.tc9_pr\_\_Primary_Payee_Record\_\_c = payee.Id; listOfEmployees.add(employeeRec); } update listOfEmployees; ``` ### General Page Layout Updates to Payment Details and Pay Code The updates to the Payment Details page layout is compulsory and all the below configuration steps must be completed: 1. Update existing layouts to remove field(s) (Compulsory) 2. Update existing layouts to add / modify existing field(s) (Optional) ### Update Page Layouts to Remove Field(s) (Compulsory) This requirement must be completed. 1. Go to Setup > Object Manager 2. Select Payment Detail (tc9\_pr\_\_Payment\_Detail\_\_c) > Page Layouts 3. Select any page layout that is used for the Payment Detail object\* 4. Remove the following field(s) from the layout * Payment Method (tc9\_pr\_\_Payment \_Method\_\_c) 5. Click Save 6. Repeat steps 3 to 5 for all page layouts that are used for the Payment Details object. ### Update Page Layouts to Add / Modify Field(s) (Optional) This requirement only needs to be completed if Pay Codes are created or modified using Bulk Data Creation. If not, this item can be skipped. 1. Go to Setup > Object Manager 2. Select Pay Code (tc9\_pr\_\_Pay Code\_\_c) > Page Layouts 3. Select any page layout that is used for the Payment, Allowance, Deduction or Expenses record types\* 4. Add the following field(s) to the layout * Pay Advice Description (tc9\_pr\_\_Pay \_Advice\_Description\_\_c) * Pay Advice Sort Order (tc9\_pr\_\_Pay\_Advice\_Sort\_Order\_\_c) 5. Update the field settings so the following fields are no longer required fields * Invoice Taxable (tc9\_et\_\_Invoice \_Taxable\_\_c) * ATO Income Classification (tc9\_et\_ATO\_Income\_Classification\_\_c) 6. Click Save 7. Repeat steps 3 to 6 for all page layouts that are used for the Payment, Allowance, Deduction or Expenses record types \*Page layouts used by external users, such as those used for Employee Experience (Communities) and Approver (Communities) do not need to be included in the above update. If a change to one of these layouts is required, it will be listed as a separate configuration item. # Appendix 1 Below is a list of new components included within the Banksia ‘21 Release ***Object*** | Label | Name | | --------------- | -------------------------------- | | Assignment Cost | tc9\_pr\_\_Assignment\_Cost\_\_c | ***Object Fields*** | Object | Label | Name | Type | | ----------------------------------------------------------------------------- | ------------------------------------------ | ------------------------------------------------------- | ---------------- | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Allow Delete Approved Timesheets | Allow\_Delete\_Approved\_Timesheets\_\_c | Picklist | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Allow Delete Submitted Timesheets | Allow\_Delete\_Submitted\_Timesheets\_\_c | Picklist | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Annualised Assignment | tc9\_pr\_\_Annualised\_Assignment\_\_c | Lookup | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Back Pay Calculation Status | tc9\_et\_\_Back\_Pay\_Calculation\_Status\_\_c | Picklist | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Employment Cost Template Group | tc9\_pr\_\_Employment\_Cost\_Template\_Gro up\_\_c | Lookup | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Has Pending Assignment to be Processed | Has\_Pending\_Assignment\_Rate\_Temp\_Gr oup\_\_c | Checkbox | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Has Pending Minimum Pay Rate | Has\_Pending\_Min\_Pay\_Rate\_\_c | Checkbox | | Object | Label | Name | Type | | --- | --- | --- | --- | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Has Pending Payee Allowance Template Group | Has\_Pending\_Payee\_Allowance\_Temp\_Gr oup\_\_c | Checkbox | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Assignment | tc9\_pr\_\_Assignment\_\_c | Lookup | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Effective Date | tc9\_pr\_\_Effective\_Date\_\_c | Date | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Employment Cost | tc9\_pr\_\_Employment\_Cost\_\_c | Lookup | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Expiry Date | tc9\_pr\_\_Expiry\_Date\_\_c | Date | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Status | tc9\_pr\_\_Status\_\_c | Picklist | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Template Group | tc9\_pr\_\_Template\_Group\_\_c | Lookup | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Back Pay Action | tc9\_et\_\_Back\_Pay\_Action\_\_c | Picklist | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Back Pay Calculation Status | tc9\_et\_\_Back\_Pay\_Calculation\_Status\_\_c | Picklist | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Back Pay End Date | tc9\_et\_\_Back\_Pay\_End\_Date\_\_c | Date | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Back Pay Start Date | tc9\_et\_\_Back\_Pay\_Start\_Date\_\_c | Date | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Back Pay To Be Invoiced? | tc9\_et\_\_Back\_Pay\_To\_Be\_Invoiced\_\_c | Picklist | | Object | Label | Name | Type | | --- | --- | --- | --- | | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | Has Pending Assignment to be Processed | Has\_Pending\_Assignment\_to\_be\_process ed\_\_c | Checkbox | | Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) | View Work Schedule Calendar | View\_Work\_Schedule\_Calendar\_\_c | Formula | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | Casual Loading Pay Code | Casual\_Loading\_Pay\_Code\_\_c | Lookup | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | Leave Header | tc9\_et\_\_Leave\_Header\_\_c | Lookup | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | Leave Loading Pay Code | Leave\_Loading\_Pay\_Code\_\_c | Lookup | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | Penalty Loading Pay Code | Penalty\_Loading\_Pay\_Code\_\_c | Lookup | | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | Saturday Pay Code | Saturday\_Pay\_Code\_\_c | Lookup | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Casual Loading | tc9\_et\_\_Apply\_Casual\_Loading\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Friday | Apply\_Overnight\_Majority\_Friday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Monday | Apply\_Overnight\_Majority\_Monday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Public Holiday | Apply\_Overnight\_Majority\_Public\_Holiday \_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Saturday | Apply\_Overnight\_Majority\_Saturday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Sunday | Apply\_Overnight\_Majority\_Sunday\_\_c | Picklist | | Object | Label | Name | Type | | --- | --- | --- | --- | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Thursday | Apply\_Overnight\_Majority\_Thursday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Tuesday | Apply\_Overnight\_Majority\_Tuesday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Wednesday | Apply\_Overnight\_Majority\_Wednesday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Overnight Majority Weekday | Apply\_Overnight\_Majority\_Weekday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Apply Penalty Loading | tc9\_et\_\_Apply\_Penalty\_Loading\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Friday | Higher\_Rate\_Friday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Monday | Higher\_Rate\_Monday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Public Holiday | Higher\_Rate\_Public\_Holiday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Saturday | Higher\_Rate\_Saturday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Sunday | Higher\_Rate\_Sunday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Thursday | Higher\_Rate\_Thursday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Tuesday | Higher\_Rate\_Tuesday\_\_c | Picklist | | Object | Label | Name | Type | | --- | --- | --- | --- | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Wednesday | Higher\_Rate\_Wednesday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Higher Rate Weekday | Higher\_Rate\_Weekday\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Based on Majority of Shift? | Overnight\_Based\_on\_Majority\_of\_Shift\_\_c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Based on Shift Start Range | Overnight\_Based\_on\_Shift\_Start\_Range\_\_ c | Picklist | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Friday Shift Starting from | Overnight\_Friday\_Shift\_Starting\_from\_\_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Monday Shift Starting from | *Overnight\_Monday\_Shift\_Starting\_from* \_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight PH Shift Starting from | Overnight\_Public\_Holiday\_Shift\_Starting\_f rom\_\_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Saturday Shift Starting from | Overnight\_Saturday\_Shift\_Starting\_from\_ \_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Sunday Shift Starting from | Overnight\_Sunday\_Shift\_Starting\_from\_\_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Thursday Shift Starting from | Overnight\_Thursday\_Shift\_Starting\_from\_ \_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Tuesday Shift Starting from | Overnight\_Tuesday\_Shift\_Starting\_from\_\_ c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Wednesday Shift Starting from | Overnight\_Wednesday\_Shift\_Starting\_fro m\_\_c | Time | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Overnight Weekday Shift Starting from | Overnight\_Weekday\_Shift\_Starting\_from\_ \_c | Time | | Object | Label | Name | Type | | --- | --- | --- | --- | | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | Variation Record Type | tc9\_et\_\_Variation\_Type\_\_c | Picklist | | Invoice Setting (tc9\_et\_\_Invoice\_Setting\_\_c) | Enable Full Approval History | Enable\_Full\_Approval\_history\_\_c | Picklist | | Invoice Setting (tc9\_et\_\_Invoice\_Setting\_\_c) | Split Loading Pay Transactions | Split\_Loading\_Pay\_Transactions\_\_c | Picklist | | Minimum Pay Rate (tc9\_et\_\_Minimum\_Pay\_Rate\_\_c) | Has Pending Assignment to be Processed | Has\_Pending\_Assignment\_to\_be\_process ed\_\_c | Checkbox | | Pay Code (tc9\_pr\_\_Pay\_Code\_\_c) | Contributes to Total Quantity | Contributes\_to\_Total\_Quantity\_\_c | Checkbox | | Pay Code (tc9\_pr\_\_Pay\_Code\_\_c) | WorkCover Reportable | tc9\_pr\_\_WorkCover\_Reportable\_\_c | Checkbox | | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | Interpretation Category | tc9\_et\_\_Interpretation\_Category\_\_c | Picklist | | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | Payee Leave Rule Id | tc9\_et\_\_Payee\_Leave\_Rule\_Id\_\_c | Text | | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | Source | tc9\_et\_\_Source\_\_c | Formula | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | AU Payroll Oncosts | tc9\_pr\_\_AU\_Payroll\_Oncosts\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Assignment Cost | tc9\_pr\_\_Custom\_Assignment\_Cost\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Emp Cost Item | tc9\_pr\_\_Custom\_Emp\_Cost\_Item\_\_c | Lookup | | Object | Label | Name | Type | | --- | --- | --- | --- | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Rate | tc9\_pr\_\_Custom\_Rate\_\_c | Number | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Total Cost | tc9\_pr\_\_Custom\_Total\_Cost\_\_c | Number | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax Assignment Cost | tc9\_pr\_\_Payroll\_Tax\_Assignment\_Cost\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax Emp Cost Item | tc9\_pr\_\_Payroll\_Tax\_Emp\_Cost\_Item\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax on Earnings | tc9\_pr\_\_Payroll\_Tax\_on\_Earnings\_\_c | Formula (number) | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax on Super | tc9\_pr\_\_Payroll\_Tax\_on\_Super\_\_c | Formula (number) | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax Rate | tc9\_pr\_\_Payroll\_Tax\_Rate\_\_c | Number | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Payroll Tax Total Cost | tc9\_pr\_\_Payroll\_Tax\_Total\_Cost\_\_c | Number | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Total Payroll Tax | tc9\_pr\_\_Payroll\_Tax\_Total\_\_c | Formula (number) | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Total WorkCover | tc9\_pr\_\_WorkCover\_Total\_\_c | Formula (number) | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover Assignment Cost | tc9\_pr\_\_WorkCover\_Assignment\_Cost\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover Emp Cost Item | tc9\_pr\_\_WorkCover\_Emp\_Cost\_Item\_\_c | Lookup | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover on Earnings | tc9\_pr\_\_WorkCover\_on\_Earnings\_\_c | Formula (number) | | Object | Label | Name | Type | | --- | --- | --- | --- | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover on Super | tc9\_pr\_\_WorkCover\_on\_Super\_\_c | Formula (number) | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover Rate | tc9\_pr\_\_WorkCover\_Rate\_\_c | Number | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | WorkCover Total Cost | tc9\_pr\_\_WorkCover\_Total\_Cost\_\_c | Number | | Payee Leave Event (tc9\_pr\_\_Payee\_Leave\_Event\_\_c) | Part Day Override | tc9\_pr\_\_Part\_Day\_Override\_\_c | Picklist | | Schedule (tc9\_pr\_\_Schedule\_\_c) | Work Schedule Manager | tc9\_pr\_\_Work\_Schedule\_Manager\_\_c | Formula | | User (User) | Contact Id | tc9\_ec\_\_Contact\_Id\_\_c | Lookup | | ***Object Record Types*** | | | | | Object | Label | Name | | ----------------------------------------------------------------------------- | ------------------------ | ---------------------------------- | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Assignment Level | tc9\_pr.Assignment\_Level | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_c) | Employment Cost Template | tc9\_pr.Employment\_Cost\_Template | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | AU Payroll Costs | tc9\_pr.AU\_Payroll\_Costs | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Cost 1 | tc9\_pr.Custom\_Cost\_1 | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Cost 2 | tc9\_pr.Custom\_Cost\_2 | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Cost 3 | tc9\_pr.Custom\_Cost\_3 | | Pay Transaction Distribution (tc9\_pr\_\_Pay\_Transaction\_Distribution\_\_c) | Custom Cost 4 | tc9\_pr.Custom\_Cost\_4 | | Template Group (tc9\_pr\_\_Template\_Group\_\_c) | Employment Cost | tc9\_pr.Employment\_Cost | | ***Custom Setting Fields*** | | | | Custom Setting | Label | Name | | ----------------------------------------------------------------------- | ----------------------------------- | -------------------------------------------------------- | | Override TC9P Validation (tc9\_pr\_\_Override\_TC9P\_Validation\_\_c) | Override Assignment Cost | tc9\_pr\_\_OV\_Assignment\_Cost\_\_c | | Override TC9P Validation (tc9\_pr\_\_Override\_TC9P\_Validation\_\_c) | Override Invoice Setting | tc9\_et\_\_OV\_Invoice\_Setting\_\_c | | Time2Pay Batch Size Overrides (tc9\_et\_\_TCS\_Variable\_Settings\_\_c) | Batch size for back pay calculation | tc9\_et\_\_Batch\_size\_for\_back\_pay\_calculation\_\_c | | Time2Pay Batch Size Overrides (tc9\_et\_\_TCS\_Variable\_Settings\_\_c) | Batch size for back pay deletion | tc9\_et\_\_Batch\_size\_for\_back\_pay\_deletion\_\_c | | Time2pay Extension Main Settings (tc9\_et\_\_ExtMainSettings\_\_c) | Record Owner | tc9\_et\_\_Record\_Owner\_\_c | ***Page Layout*** | Object | Name | | ------------------------------------------------- | ---------------------- | | Assignment Cost (tc9\_pr\_\_Assignment\_Cost\_\_) | Assignment Cost Layout | ### Lightning Pages | Type | Label | Name | | ----------- | ----------------------------------- | --------------------------------------- | | Record Page | Template Group Lighting Record Page | Template\_Group\_Lighting\_Record\_Page | ### Global Value Sets | Label | Name | | ------------------------------------ | --------------------------------------- | | Back Pay Action | Back\_Pay\_Action | | Back Pay Calculation Status | Back\_Pay\_Calculation\_Status | | Interpretation Categories | Interpretation\_Categories | | Interpretation Higher Rate Picklists | Interpretation\_Higher\_Rate\_Picklists | ### Tabs | Type | Label | Name | | ------------------ | ---------------- | ---- | | Custom Object Tabs | Assignment Costs | N/A | ***Action*** | Object | Label | Name | | --------------------------------------- | ------------------------------------------ | ----------------------------------------------------------- | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Bulk Delete Timesheets and Related Records | tc9\_et\_\_Bulk\_Delete\_Timesheets\_and\_Related\_Rec ords | | Payee (tc9\_pr\_\_Payee\_\_c) | Super Stapling | tc9\_eau\_\_Super\_Stapling | | ***Buttons and Links*** | | | | Object | Label | Name | | --------------------------------------- | ------------------------------------------ | ------------------------------------------ | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Assignment Rate Automation (Detail Button) | tc9\_et.Assignment\_Rate\_Automation | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Assignment Rate Automation (List Button) | tc9\_et.Assignment\_Rate\_Automation\_List | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Calculate Back Pay (Detail Button) | tc9\_et.Calculate\_Back\_Pay | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Calculate Back Pay (List Button) | tc9\_et.Calculate\_Back\_Pay\_List | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Delete\_Back\_Pay (Detail Button) | tc9\_et.Delete\_Back\_Pay | | Assignment (tc9\_pr\_\_Assignment\_\_c) | Delete\_Back\_Pay (List Button) | tc9\_et.Delete\_Back\_Pay\_List | | Schedule (tc9\_pr\_\_Schedule\_\_c) | Unpublish | tc9\_pr.unpublish | ### List Views | Object | Label | Name | | ------------------------------------------------ | ----- | ---- | | Template Group (tc9\_pr\_\_Template\_Group\_\_c) | All | All | ### Custom Notifications | Label | Name | | ------------------------------------- | ----------------------------------------- | | Deletion of Timesheet Entries | Deletion\_of\_Timesheet\_Entries | | MPR Automation Failed For Assignments | MPR\_Automation\_Failed\_For\_Assignments | | MPR Scheduled Job Running | MPR\_Scheduled\_Job\_Running | # Appendix 2 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to create and allocate work schedules. | Users Key | | | --------- | ----------------------------------------------------- | | User 1 | Users who will create / edit Work Schedules | | User 2 | Users who will allocate work schedules to assignments | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ----------- | ------------------------------------------------------------------------------------ | ------ | ------ | ------ | ------ | | Object | Schedule (tc9\_pr\_\_Schedule\_\_c) | R/C/E | R | | | | Record Type | Work Schedule (tc9\_pr.Work\_Schedule) | A | A | | | | Field | Auto Create Shift Allocations (tc9\_pr\_\_Auto\_Create\_Shift\_Allocations\_\_c) | R/E | R | | | | Field | Break Time Format (tc9\_pr\_\_Break\_Time\_Format\_\_c) | R/E | R | | | | Field | Shift Time Format (tc9\_pr\_\_Shift\_Time\_Format\_\_c) | R/E | R | | | | Field | Work Schedule First Day (tc9\_pr\_\_Work\_Schedule\_First\_Day\_\_c) | R/E | R | | | | Field | Work Schedule Generation Status (tc9\_pr\_\_Work\_Schedule\_Generation\_Status\_\_c) | R/E | R | | | | Field | Work Schedule Hours (tc9\_pr\_\_Work\_Schedule\_Hours\_\_c) | R/E | R | | | | Field | Work Schedule Minutes (tc9\_pr\_\_Work\_Schedule\_Minutes\_\_c) | R/E | R | | | | Field | Work Schedule Number of Weeks (tc9\_pr\_\_Work\_Schedule\_Number\_of\_Weeks\_\_c) | R/E | R | | | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Work Schedule Paid Breaks (tc9\_pr\_\_Work\_Schedule\_Paid\_Breaks\_\_c) | R/E | R | | | | Field | Work Schedule Published From (tc9\_pr\_\_Work\_Schedule\_Published\_From\_\_c) | R/E | R | | | | Field | Work Schedule Published To (tc9\_pr\_\_Work\_Schedule\_Published\_To\_\_c) | R/E | R | | | | Field | Work Schedule Start Date (tc9\_pr\_\_Work\_Schedule\_Start\_Date\_\_c) | R/E | R | | | | Field | Work Schedule Start Day (tc9\_pr\_\_Work\_Schedule\_Start\_Day\_\_c) | R/E | R | | | | Field | Work Schedule Total Breaks (tc9\_pr\_\_Work\_Schedule\_Total\_Breaks\_\_c) | R/E | R | | | | Field | Work Schedule Total Time (tc9\_pr\_\_Work\_Schedule\_Total\_Time\_\_c) | R/E | R | | | | Field | Work Schedule Unpaid Breaks (tc9\_pr\_\_Work\_Schedule\_Unpaid\_Breaks\_\_c) | R/E | R | | | | Object | Schedule Item (tc9\_pr\_\_Schedule\_Item\_\_c) | R/C/E | R | | | | Record Type | Shift (tc9\_pr.Shift) | A | A | | | | Record Type | Shift Allocation (tc9\_pr.Shift\_Allocation) | A | A | | | | Record Type | Work Schedule Entry (tc9\_pr.Work\_Schedule\_Entry) | A | A | | | | Field | Break 1 End Time (tc9\_pr\_\_Break\_1\_End\_Time\_\_c) | R/E | R | | | | Field | Break 1 Paid (tc9\_pr\_\_Break\_1\_Paid\_\_c) | R/E | R | | | | Field | Break 1 Start Time (tc9\_pr\_\_Break\_1\_Start\_Time\_\_c) | R/E | R | | | | Field | Break 1 Total Time (tc9\_pr\_\_Break\_1\_Total\_Time\_\_c) | R/E | R | | | | Field | Break 2 End Time (tc9\_pr\_\_Break\_2\_End\_Time\_\_c) | R/E | R | | | | Field | Break 2 Paid (tc9\_pr\_\_Break\_2\_Paid\_\_c) | R/E | R | | | | Field | Break 2 Start Time (tc9\_pr\_\_Break\_2\_Start\_Time\_\_c) | R/E | R | | | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Break 2 Total Time (tc9\_pr\_\_Break\_2\_Total\_Time\_\_c) | R/E | R | | | | Field | Break Time Format (tc9\_pr\_\_Break\_Time\_Format\_\_c) | R/E | R | | | | Field | Day Number (tc9\_pr\_\_Day\_Number\_\_c) | R/E | R | | | | Field | Day of the Week (tc9\_pr\_\_Day\_of\_the\_Week\_\_c) | R/E | R | | | | Field | Day Off (tc9\_pr\_\_Day\_Off\_\_c) | R/E | R | | | | Field | Entry Date (tc9\_pr\_\_Entry\_Date\_\_c) | R/E | R | | | | Field | External Id (tc9\_pr\_\_External\_Id\_\_c) | R/E | R | | | | Field | Shift Allocation Record (tc9\_pr\_\_Shift\_Allocation\_Record\_\_c) | R/E | R | | | | Field | Shift End Time (tc9\_pr\_\_Shift\_End\_Time\_\_c) | R/E | R | | | | Field | Shift Number (tc9\_pr\_\_Shift\_Number\_\_c) | R/E | R | | | | Field | Shift Paid Breaks (tc9\_pr\_\_Shift\_Paid\_Breaks\_\_c) | R/E | R | | | | Field | Shift Record (tc9\_pr\_\_Shift\_Record\_\_c) | R/E | R | | | | Field | Shift Start Time (tc9\_pr\_\_Shift\_Start\_Time\_\_c) | R/E | R | | | | Field | Shift Time Format (tc9\_pr\_\_Shift\_Time\_Format\_\_c) | R/E | R | | | | Field | Shift Total Breaks (tc9\_pr\_\_Shift\_Total\_Breaks\_\_c) | R/E | R | | | | Field | Shift Total Hours (tc9\_pr\_\_Shift\_Total\_Hours\_\_c) | R/E | R | | | | Field | Shift Total Minutes (tc9\_pr\_\_Shift\_Total\_Minutes\_\_c) | R/E | R | | | | Field | Shift Total Time (tc9\_pr\_\_Shift\_Total\_Time\_\_c) | R/E | R | | | | Field | Shift Unpaid Breaks (tc9\_pr\_\_Shift\_Unpaid\_Breaks\_\_c) | R/E | R | | | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Sort Order (tc9\_pr\_\_Sort\_Order\_\_c) | R/E | R | | | | Field | Week Number (tc9\_pr\_\_Week\_Number\_\_c) | R/E | R | | | | Field | Work Schedule (tc9\_pr\_\_Work\_Schedule\_\_c) | R/E | R | | | | Object | Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) | | R/C/E | | | | Record Type | Work Schedule (tc9\_pr.Work\_Schedule) | | A | | | | Record Type | Substitution (tc9\_pr.Substitution) | | A | | | | Field | Assignment (tc9\_pr\_\_Assignment\_\_c) | | R/E | | | | Field | Effective Date (tc9\_pr\_\_Effective\_Date\_\_c) | | R/E | | | | Field | Employee (tc9\_pr\_\_Employee\_\_c) | | R/E | | | | Field | Exclude From Auto Update (tc9\_pr\_\_Exclude\_From\_Auto\_Update\_\_c) | | R/E | | | | Field | Expiry Date (tc9\_pr\_\_Expiry\_Date\_\_c) | | R/E | | | | Field | External Id (tc9\_pr\_\_External\_Id\_\_c) | R/E | | | | | Field | Payee (tc9\_pr\_\_Payee\_\_c) | R/E | | | | | Field | Public Holiday Calendar (tc9\_pr\_\_Public\_Holiday\_Calendar\_\_c) | R/E | | | | | Field | Status (tc9\_pr\_\_Status\_\_c) | R/E | | | | | Field | View Work Schedule Calendar (View\_Work\_Schedule\_Calendar\_\_c) | | R | | | | Field | Work Schedule (tc9\_pr\_\_Work\_Schedule\_\_c) | R/E | | | | # Appendix 3 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to apply work schedule information to payroll. | Users Key | | | --------- | -------------------------------------------------------------------- | | User 1 | Users that create / update Assignment Rates | | User 2 | Users who generate Timesheets | | User 3 | Users who will be processing Timesheets through Interpretation Rules | | User 4 | Users who will process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ----------- | ------------------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | R/C/E | R | R | R | | Field | Auto Pay Calculation Basis (tc9\_pr\_\_Auto\_Pay\_Calculation\_Basis\_\_c) | R/E | | | R | | Object | Schedule (tc9\_pr\_\_Schedule\_\_c) | | R | | R | | Record Type | Work Schedule (tc9\_pr.Work\_Schedule) | | A | | A | | Field | Auto Create Shift Allocations (tc9\_pr\_\_Auto\_Create\_Shift\_Allocations\_\_c) | | R | | R | | Field | Auto Pay Public Holiday Pay Code (tc9\_pr\_\_Auto\_Pay\_Public\_Holiday\_Pay\_Code\_\_c) | | R | | R | | Field | Break Time Format (tc9\_pr\_\_Break\_Time\_Format\_\_c) | | R | | R | | Field | Default Auto Pay Calculation Basis (tc9\_pr\_\_Default\_Auto\_Pay\_Calculation\_Basis\_\_c) | | R | | R | | Field | Shift Time Format (tc9\_pr\_\_Shift\_Time\_Format\_\_c) | | R | | R | | Field | Work Schedule First Day (tc9\_pr\_\_Work\_Schedule\_First\_Day\_\_c) | | R | | R | | Field | Work Schedule Generation Status (tc9\_pr\_\_Work\_Schedule\_Generation\_Status\_\_c) | | R | | R | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Work Schedule Hours (tc9\_pr\_\_Work\_Schedule\_Hours\_\_c) | | R | | R | | Field | Work Schedule Minutes (tc9\_pr\_\_Work\_Schedule\_Minutes\_\_c) | | R | | R | | Field | Work Schedule Number of Weeks (tc9\_pr\_\_Work\_Schedule\_Number\_of\_Weeks\_\_c) | | R | | R | | Field | Work Schedule Paid Breaks (tc9\_pr\_\_Work\_Schedule\_Paid\_Breaks\_\_c) | | R | | R | | Field | Work Schedule Published From (tc9\_pr\_\_Work\_Schedule\_Published\_From\_\_c) | | R | | R | | Field | Work Schedule Published To (tc9\_pr\_\_Work\_Schedule\_Published\_To\_\_c) | | R | | R | | Field | Work Schedule Start Date (tc9\_pr\_\_Work\_Schedule\_Start\_Date\_\_c) | | R | | R | | Field | Work Schedule Start Day (tc9\_pr\_\_Work\_Schedule\_Start\_Day\_\_c) | | R | | R | | Field | Work Schedule Total Breaks (tc9\_pr\_\_Work\_Schedule\_Total\_Breaks\_\_c) | | R | | R | | Field | Work Schedule Total Time (tc9\_pr\_\_Work\_Schedule\_Total\_Time\_\_c) | | R | | R | | Field | Work Schedule Unpaid Breaks (tc9\_pr\_\_Work\_Schedule\_Unpaid\_Breaks\_\_c) | | R | | R | | Object | Schedule Item (tc9\_pr\_\_Schedule\_Item\_\_c) | | R | R | R | | Record Type | Shift (tc9\_pr.Shift) | | A | | A | | Record Type | Shift Allocation (tc9\_pr.Shift\_Allocation) | | A | | A | | Record Type | Work Schedule Entry (tc9\_pr.Work\_Schedule\_Entry) | | A | | A | | Field | Break 1 End Time (tc9\_pr\_\_Break\_1\_End\_Time\_\_c) | | R | | R | | Field | Break 1 Paid (tc9\_pr\_\_Break\_1\_Paid\_\_c) | | R | | R | | Field | Break 1 Start Time (tc9\_pr\_\_Break\_1\_Start\_Time\_\_c) | | R | | R | | Field | Break 1 Total Time (tc9\_pr\_\_Break\_1\_Total\_Time\_\_c) | | R | | R | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Break 2 End Time (tc9\_pr\_\_Break\_2\_End\_Time\_\_c) | | R | | R | | Field | Break 2 Paid (tc9\_pr\_\_Break\_2\_Paid\_\_c) | | R | | R | | Field | Break 2 Start Time (tc9\_pr\_\_Break\_2\_Start\_Time\_\_c) | | R | | R | | Field | Break 2 Total Time (tc9\_pr\_\_Break\_2\_Total\_Time\_\_c) | | R | | R | | Field | Break Time Format (tc9\_pr\_\_Break\_Time\_Format\_\_c) | | R | | R | | Field | Day Number (tc9\_pr\_\_Day\_Number\_\_c) | | R | | R | | Field | Day of the Week (tc9\_pr\_\_Day\_of\_the\_Week\_\_c) | | R | | R | | Field | Day Off (tc9\_pr\_\_Day\_Off\_\_c) | | R | | R | | Field | Entry Date (tc9\_pr\_\_Entry\_Date\_\_c) | | R | | R | | Field | External Id (tc9\_pr\_\_External\_Id\_\_c) | | R | | R | | Field | Shift Allocation Record (tc9\_pr\_\_Shift\_Allocation\_Record\_\_c) | | R | | R | | Field | Shift End Time (tc9\_pr\_\_Shift\_End\_Time\_\_c) | | R | | R | | Field | Shift Number (tc9\_pr\_\_Shift\_Number\_\_c) | | R | | R | | Field | Shift Paid Breaks (tc9\_pr\_\_Shift\_Paid\_Breaks\_\_c) | | R | | R | | Field | Shift Record (tc9\_pr\_\_Shift\_Record\_\_c) | | R | | R | | Field | Shift Start Time (tc9\_pr\_\_Shift\_Start\_Time\_\_c) | | R | | R | | Field | Shift Time Format (tc9\_pr\_\_Shift\_Time\_Format\_\_c) | | R | | R | | Field | Shift Total Breaks (tc9\_pr\_\_Shift\_Total\_Breaks\_\_c) | | R | | R | | Field | Shift Total Hours (tc9\_pr\_\_Shift\_Total\_Hours\_\_c) | | R | | R | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Shift Total Minutes (tc9\_pr\_\_Shift\_Total\_Minutes\_\_c) | | R | | R | | Field | Shift Total Time (tc9\_pr\_\_Shift\_Total\_Time\_\_c) | | R | | R | | Field | Shift Unpaid Breaks (tc9\_pr\_\_Shift\_Unpaid\_Breaks\_\_c) | | R | | R | | Field | Sort Order (tc9\_pr\_\_Sort\_Order\_\_c) | | R | | R | | Field | Week Number (tc9\_pr\_\_Week\_Number\_\_c) | | R | | R | | Field | Work Schedule (tc9\_pr\_\_Work\_Schedule\_\_c) | | R | | R | | Object | Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) | | R | R | R | | Record Type | Work Schedule (tc9\_pr.Work\_Schedule) | | A | A | A | | Record Type | Substitution (tc9\_pr.Substitution) | | A | A | A | | Field | Assignment (tc9\_pr\_\_Assignment\_\_c) | | R | R | R | | Field | Effective Date (tc9\_pr\_\_Effective\_Date\_\_c) | | R | R | R | | Field | Employee (tc9\_pr\_\_Employee\_\_c) | | R | R | R | | Field | Exclude From Auto Update (tc9\_pr\_\_Exclude\_From\_Auto\_Update\_\_c) | | R | R | R | | Field | Expiry Date (tc9\_pr\_\_Expiry\_Date\_\_c) | | R | R | R | | Field | External Id (tc9\_pr\_\_External\_Id\_\_c) | | R | R | R | | Field | Payee (tc9\_pr\_\_Payee\_\_c) | | R | R | R | | Field | Public Holiday Calendar (tc9\_pr\_\_Public\_Holiday\_Calendar\_\_c) | | R | R | R | | Field | Status (tc9\_pr\_\_Status\_\_c) | | R | R | R | | Field | Work Schedule (tc9\_pr\_\_Work\_Schedule\_\_c) | | R | R | R | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Object | Timesheet Entry (tc9\_et\_\_Timesheet\_Entry\_\_c) | | R/C/E | R | R | | Field | Work Schedule Item (tc9\_pr\_\_Work\_Schedule\_Item\_\_c) | | R/E | R | R | | Object | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | | | R | R | | Field | Assignment Schedule (tc9\_pr\_\_Assignment\_Schedule\_\_c) | | | R | R | # Appendix 4 The below table defines the access that must be granted to Internal Users for new components introduced for the Work Schedule Manager functionality. | Users Key | | | --------- | --------------------------------------------- | | User 1 | Users who will create / update Work Schedules | | User 2 | Users who will process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | --------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Work Schedule (tc9\_pr\_\_Work\_Schedule\_\_c) | R/C/E | R | | | | Field | Work Schedule Manager (tc9\_pr\_\_Work\_Schedule\_Manager\_\_c) | R/E | R | | | # Appendix 5 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to extend work schedules to handle part day leave events | Users Key | | | --------- | ------------------------------------------------- | | User 1 | Users who will create / update Payee Leave Events | | User 2 | Users who will process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Payee Leave Event (tc9\_pr\_\_Payee\_Leave\_Event\_\_c) | R/C/E | R | | | | Field | Part Day Override (tc9\_pr\_\_Part\_Day\_Override\_\_c) | R/E | R | | | # Appendix 6 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to customise the payee pay batch’s total quantity calculations | Users Key | | | --------- | --------------------------------------- | | User 1 | Users who will create / update Pay Code | | User 2 | Users who process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | -------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Pay Code (tc9\_pr\_\_Pay\_Code\_\_c) | R/C/E | R | | | | Field | Contributes to Total Quantity (tc9\_pr\_\_Contributes\_to\_Total\_Quantity\_\_c) | R/E | R | | | # Appendix 7 The below table defines the access that must be granted to Internal Users for new components introduced to improve the overnight interpretation processing capabilities. | Users Key | | | --------- | -------------------------------------------------------------------- | | User 1 | Users who will create / update Interpretation Rules | | User 2 | Users who will be processing Timesheets through Interpretation Rules | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | R/C/E | R | | | | Field | Overnight Based on Shift Start Range (tc9\_et\_\_Overnight\_Based\_on\_Majority\_of\_Shift\_\_c) | R/E | R | | | | Field | Overnight Based on Majority of Shift (tc9\_et\_\_Overnight\_Based\_on\_Shift\_Start\_Range\_\_c) | R/E | R | | | | Field | Overnight Based on Majority of overnightShift? (tc9\_et\_\_Overnight\_Based\_on\_Majority\_of\_Shift\_\_c) | R/E | R | | | | Field | Overnight Weekday Shift Starting from (tc9\_et\_\_Overnight\_Weekday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Monday Shift Starting from (tc9\_et\_\_Overnight\_Monday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Tuesday Shift Starting from (tc9\_et\_\_Overnight\_Tuesday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Wednesday Shift Starting from (tc9\_et\_\_Overnight\_Wednesday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Thursday Shift Starting from (tc9\_et\_\_Overnight\_Thursday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Friday Shift Starting from (tc9\_et\_\_Overnight\_Friday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Overnight Saturday Shift Starting from (tc9\_et\_\_Overnight\_Saturday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Overnight Sunday Shift Starting from (tc9\_et\_\_Overnight\_Sunday\_Shift\_Starting\_fro | R/E | R | | | | Field | Overnight PH Shift Starting from (tc9\_et\_\_Overnight\_Public\_Holiday\_Shift\_Starting\_from\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Weekday (tc9\_et\_\_Apply\_Overnight\_Majority\_Weekday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Monday (tc9\_et\_\_Apply\_Overnight\_Majority\_Monday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Tuesday (tc9\_et\_\_Apply\_Overnight\_Majority\_Tuesday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Wednesday (tc9\_et\_\_Apply\_Overnight\_Majority\_Wednesday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Thursday (tc9\_et\_\_Apply\_Overnight\_Majority\_Thursday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Friday (tc9\_et\_\_Apply\_Overnight\_Majority\_Friday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Saturday (tc9\_et\_\_Apply\_Overnight\_Majority\_Saturday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Sunday (tc9\_et\_\_Apply\_Overnight\_Majority\_Sunday\_\_c) | R/E | R | | | | Field | Apply Overnight Majority Public Holiday (tc9\_et\_\_Apply\_Overnight\_Majority\_Public\_Holiday\_\_c) | R/E | R | | | | Field | Higher Rate Weekday (tc9\_et\_\_Higher\_Rate\_Weekday\_\_c) | R/E | R | | | | Field | Higher Rate Monday (tc9\_et\_\_Higher\_Rate\_Monday\_\_c) | R/E | R | | | | Field | Higher Rate Tuesday (tc9\_et\_\_Higher\_Rate\_Tuesday\_\_c) | R/E | R | | | | Field | Higher Rate Wednesday (tc9\_et\_\_Higher\_Rate\_Wednesday\_\_c) | R/E | R | | | | Field | Higher Rate Thursday (tc9\_et\_\_Higher\_Rate\_Thursday\_\_c) | R/E | R | | | | Field | Higher Rate Friday (tc9\_et\_\_Higher\_Rate\_Friday\_\_c) | R/E | R | | | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --- | --- | --- | --- | --- | --- | | Field | Higher Rate Saturday (tc9\_et\_\_Higher\_Rate\_Saturday\_\_c) | R/E | R | | | | Field | Higher Rate Sunday (tc9\_et\_\_Higher\_Rate\_Sunday\_\_c) | R/E | R | | | | Field | Higher Rate Public Holiday (tc9\_et\_\_Higher\_Rate\_Public\_Holiday\_\_c) | R/E | R | | | # Appendix 8 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to define an alternative pay code for Saturday frequency breakpoints. | Users Key | | | --------- | -------------------------------------------------------------------- | | User 1 | Users who will create / update Interpretation Rules | | User 2 | Users who will be processing Timesheets through Interpretation Rules | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | R/C/E | R | | | | Field | Saturday Pay Code (tc9\_et\_\_Saturday\_Pay\_Code\_\_c) | R/E | R | | | # Appendix 9 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to allow users to override the ATO Income Classification at an Opening Balance and Pay Transaction level. | Users Key | | | --------- | ----------------------------------------------------- | | User 1 | Users who will create / update Payee Opening Balances | | User 2 | Users who will create / update Pay Transactions | | User 3 | Users who process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | --------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Payee Opening Balance (tc9\_pr\_\_Payee\_Opening\_Balance\_\_c) | R | | R/C/E | | | Field | Override ATO Income Classification | R/E | | R | | | Object | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | | R | R/C/E | | | Field | Override ATO Income Classification | | R/E | R | | # Appendix 10 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to define Opening Balances as Employer Additional Superannuation. | Users Key | | | --------- | ----------------------------------------------------- | | User 1 | Users who will create / update Payee Opening Balances | | User 2 | Users who process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ----------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Payee Opening Balance (tc9\_pr\_\_Payee\_Opening\_Balance\_\_c) | R/C/E | R | | | | Field | Employer Additional Super (tc9\_pr\_\_Employer\_Additional\_Super\_\_c) | R/E | R | | | # Appendix 11 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to view key information directly from Payee Aggregate Records | Users Key | | | --------- | ------------------------- | | User 1 | Users who process payroll | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Payee Aggregate (tc9\_pr\_\_Pay\_Aggregate\_\_c) | R/C/E | | | | | Field | Employee (tc9\_pr\_\_Employee\_Name\_\_c) | R | | | | | Field | Payment Entity (tc9\_pr\_\_Payment\_Entity\_\_c) | R | | | | | Field | Pay Schedule (tc9\_pr\_\_Pay\_Schedule\_\_c) | R | | | | | Field | Finalise Calendar Period (tc9\_pr\_\_Finalise\_Calendar\_Period\_\_c) | R | | | | | Field | Pay Batch Type (tc9\_pr\_\_Pay\_Batch\_Type\_\_c) | R | | | | | Field | Payment Date (tc9\_pr\_\_Payment\_Date\_\_c) | R | | | | | Field | Maximum Payroll Date (tc9\_pr\_\_Maximum\_Payroll\_Date\_\_c) | R | | | | | Field | Calculation Version (tc9\_pr\_\_Calculation\_Version\_\_c) | R | | | | | Field | Leave Rule (tc9\_pr\_\_Leave\_Rule\_\_c) | R | | | | | Field | Leave Type (tc9\_pr\_\_Leave\_Type\_\_c) | R | | | | | Field | Date Time Finalised (tc9\_pr\_\_Date\_Time\_Finalised\_\_c) | R | | | | | Screenshot from 2cloudnine Payroll v1.153 Banksia Release Upgrade Guide | | | | | | # Appendix 12 The below table defines the access that must be granted to Internal Users for new components introduced for the updated to the Interpretation Builders and their functionality | Users Key | | | --------- | -------------------------------------------------------------------- | | User 1 | Users who will create / update Interpretation Rules | | User 2 | Users who will be processing Timesheets through Interpretation Rules | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | R/C/E | R | | | | Field | Leave Header (tc9\_et\_\_Leave\_Header\_\_c) | R/E | R | | | | Object | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | R/C/E | R | | | | Field | Variation Record Type (tc9\_et\_\_Variation\_Type\_\_c) | R/E | R | | | # Appendix 13 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to provide greater detail on Pay Advice documents. | Users Key | | | --------- | -------------------------------------------------------------------- | | User 1 | Users who will create / update Interpretation Rules | | User 2 | Users who will be processing Timesheets through Interpretation Rules | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Interpretation Rule (tc9\_et\_\_Interpretation\_Rule\_\_c) | R/C/E | R | | | | Field | Apply Casual Loading (Apply\_Casual\_Loading\_\_c) | R/E | R | | | | Field | Apply Penalty Loading (Apply\_Penalty\_Loading\_\_c) | R/E | R | | | | Object | Interpretation Breakpoint (tc9\_et\_\_Interpretation\_Breakpoint\_\_c) | R/C/E | R | | | | Field | Casual Loading Pay Code (tc9\_et\_\_Casual\_Loading\_Pay\_Code\_\_c) | R/E | R | | | | Field | Penalty Loading Pay Code (tc9\_et\_\_Penalty\_Loading\_Pay\_Code\_\_c) | R/E | R | | | | Field | Leave Loading Pay Code (tc9\_et\_\_Leave\_Loading\_Pay\_Code\_\_c) | R/E | R | | | # Appendix 14 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to provide greater detail on Invoice documents. Note: This functionality builds on the functionality to provide greater detail on Pay Advice documents, therefore the access outlined in [Appendix 13](/upgrade-guides/2cloudnine-payroll-v1-153-banksia-release-upgrade-guide#appendix-13) must also be granted. | Users Key | | | --------- | ----------------------------------------------- | | User 1 | Users who will create / update Invoice Settings | | User 2 | Users who will create / update Invoices | | User 3 | Users who will send invoice emails | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Invoice Setting (tc9\_et\_\_Invoice\_setting\_\_c) | R/C/E | R | R | | | Field | Split loading pay transactions (tc9\_et\_\_Split\_Loading\_Pay\_Transactions\_\_c) | R/E | R | R | | # Appendix 15 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to provide greater detail on invoice backing sheets | Users Key | | | --------- | ----------------------------------------------- | | User 1 | Users who will create / update Invoice Settings | | User 2 | Users who will create / update Invoices | | User 3 | Users who will send invoice emails | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ------------------------------------------------------------------------------ | ------ | ------ | ------ | ------ | | Object | Invoice Setting (tc9\_et\_\_Invoice\_Setting\_\_c) | R/C/E | R | R | | | Field | Enable Full Approval History (tc9\_et\_\_Enable\_Full\_Approval\_history\_\_c) | R/E | R | R | | # Appendix 16 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to enable bulk delete of timesheets | Users Key | | | --------- | ------------------------------------------ | | User 1 | Users who will create / update Assignments | | User 2 | Users who will delete Timesheets | | Minimum Access Key | | | ------------------ | ------ | | R | Read | | C | Create | | E | Edit | | D | Delete | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ---------------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Timesheet (tc9\_et\_\_Timesheet\_\_c) | | D | | | | Object | Timesheet Entry (tc9\_et\_\_Timesheet\_Entry\_\_c) | | D | | | | Object | Payee Leave Event (tc9\_pr\_\_Payee\_Leave\_Event\_\_c) | | D | | | | Object | Timesheet Items (tc9\_et\_\_Timesheet\_Item\_\_c) | | D | | | | Object | Expense (tc9\_et\_\_Expense\_\_c) | | D | | | | Object | Assignment (tc9\_pr\_\_Assignment\_\_c) | R/C/E | R | | | | Field | Allow Delete Approved Timesheets (tc9\_et\_\_Allow\_Delete\_Approved\_Timesheets\_\_c) | R/E | R | | | | Field | Allow Delete Submitted Timesheets (tc9\_et\_\_Allow\_Delete\_Submitted\_Timesheets\_\_c) | R/E | R | | | # Appendix 17 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to define and use minimum pay rates. | Users Key | | | --------- | ------------------------------------------------ | | User 1 | Users who will create / update Minimum Pay Rates | | User 2 | Users who will create / update Assignments | | User 3 | Users who will create / update Assignment Rates | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | -------------------------------------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Minimum Pay Rate (tc9\_et\_\_Minimum\_Pay\_Rate\_\_c) | R/C/E | R | R | | | Field | Has Pending Assignment to be Processed (tc9\_et\_\_Has\_Pending\_Assignment\_to\_be\_processed\_\_c) | R/E | R | R | | | Object | Assignment (tc9\_pr\_\_Assignment\_\_c) | R | R/C/E | R | | | Field | Has Pending Assignment to be Processed (tc9\_pr\_\_Has\_Pending\_Assignment\_Rate\_Temp\_Group\_\_c) | R | R/E | R | | | | Has Pending Minimum Pay Rate (tc9\_pr\_\_Has\_Pending\_Min\_Pay\_Rate\_\_c) | R | R/E | R | | | | Has Pending Payee Allowance Template Group (tc9\_pr\_\_Has\_Pending\_Payee\_Allowance\_Temp\_Group\_\_c) | R | R/E | R | | | Object | Assignment Rate (tc9\_pr\_\_Assignment\_Rate\_\_c) | R | R | R/C/E | | | Field | Has Pending Assignment to be Processed (tc9\_et\_\_Has\_Pending\_Assignment\_to\_be\_processed\_\_c) | R | R | R/E | | # Appendix 18 The below table defines the access that must be granted to Internal Users and External Approver Users for new components introduced for the functionality to control if Leave credits are available in Experience (Communities) | Users Key | | | --------- | --------------------------------------------------------- | | User 1 | Users who will create / update Leave Rules | | User 2 | External Approver Users who view and approve/reject Leave | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | --------------------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Leave Rule (tc9\_pr\_\_Leave\_Rule\_\_c) | R/C/E | R | | | | Field | Credit Available in Portal? (tc9\_pr\_\_Credit\_Available\_in\_Portal\_\_c) | R/E | R | | | | Object | Pay Transaction (tc9\_pr\_\_Pay\_Transaction\_\_c) | | R/C/E | | | # Appendix 19 The below table defines the access that must be granted to Internal and External Users for new components introduced for the functionality to define if future dated timesheets can be accessed through Experience (Communities). | Users Key | | | --------- | ----------------------------------------------------------- | | User 1 | Users who will create / edit Timesheet Calendars | | User 2 | Users who will access the Employee Experience (Communities) | | User 3 | Users who will access the Approver Experience (Communities) | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ------------------------------------------------------------------------------------------ | ------ | ------ | ------ | ------ | | Object | Calendar (tc9\_pr\_\_Calendar\_\_c) | R/C/E | R | R | | | Field | No. Days Future Timesheets Visible (tc9\_et\_\_No\_Days\_Future\_Timesheets\_Visible\_\_c) | R/E | R | R | | # Appendix 20 The below table defines the access that must be granted to Internal Users for new components introduced for the functionality to populate a Payee Primary Record lookup field on the Contact. | Users Key | | | --------- | -------------------------------------------- | | User 1 | Users who will create / edit Payee records | | User 2 | Users who will create / edit Contact records | | Minimum Access Key | | | ------------------ | -------- | | R | Read | | C | Create | | E | Edit | | A | Assigned | | Type | Name | User 1 | User 2 | User 3 | User 4 | | ------ | ------------------------------------------------------------- | ------ | ------ | ------ | ------ | | Object | Contact | R/C/E | R | | | | Field | Primary Payee Record (tc9\_pr\_\_Primary\_Payee\_Record\_\_c) | E | R | | |