Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Workbench Release Notes

General Release 4.5.40.3

Scheduled Release - 24 October 2022

Upvise

  • Enable sync for Stock issues back to Workbench for Stock issues from the Equipment Stock Issues forms.

Hotfix Release 4.5.40.2

Scheduled Release - 19 October 2022

  • Login error:
    Some users were getting an invalid error message when trying to login. This has been rectified.
    Error message below: 'Login code is found, however this login code does not support this type of Authentication'

Beta Release 4.5.40.1

Scheduled Release - 17 October 2022

Feature Revisions

Jobs

  • Job Budget Line sequence in reports:
    Job Budget reports have been enhanced to use the Job Budget Lines sequence, to dictate the order in which those lines show in the reports (wbJobBudget001, wbJobBudget002, and wbJobBudget003).

  • Job Enquiry:

    • Logs tab:
      Export to Excel option has been added on the Logs tab.

    • Financial Summary tab:
      The selection of a period using the pencil (typing a period) rather than selecting from the dropdown was not working before, and this has been rectified.

  • Job Contract - Bonds:
    Bond Number field has been increased to 50 characters for Contracts and Subcontracts Bonds.

  • Contract Forecast - using Cost Category:
    Users can now drill into Uncommitted and Risk Adjustment from the hyperlinked values on each Cost Category. This will display the popup screen where any activity in the cost category can be selected for adjustment, similar to how it works for Work Centres.

Purchasing

  • AP Vouchers:

    • Support the payment of Withholding Tax Payment to the Tax authority:
      In this cases the system will not validate that the line using the Withholding tax Activity is negative. It will only allow the use of the Withholding activity with positive values when all lines in the voucher are WHT activity.

    • AP Voucher - duplicate Stock receipts in This Voucher tab:
      A display issue where Stock receipts were showing duplicated in This Voucher tab has been rectified.

  • Purchase Orders:

    • PO lines remaining quantity and Cost:
      The details on a PO line that reflect the remaining quantity and remaining cost was not taking into consideration Docket entries, so the remaining values were not correct. This has been rectified.

    • New tokens available to be added to PO email templates:

      • Supplier contact first name - $POContactFirstName

      • Job code (first PO line) - $JobCode

      • Job Name (first PO line) - $JobName

      • Site Address Details - $SiteAddress

      • PO purchaser name - $PurchaserName

      • PO purchaser Mobile Phone no - $PurchaserMobilePhone

      • PO purchaser Business Phone no - $PurchaserBusinessPhone

      • PO purchaser Company Postal Phone no - $PurchaserCompanyPhone

      • PO purchaser Home Phone no - $PurchaserHomePhone

      • PO purchaser email - $PurchaserEmail

      • PO purchaser job title - $PurchaserJobTitle

      • PO Number - $PONumber

      • PO Date - $PODate

      • PO required Date - $RequiredDate

      • PO Comments - $POComments

      • PO Reference - $POReference

    • Activity Validation when copying PO Lines:
      The activity validation was done against the Job’s Budget activity group, rather than the Job’s Cost activity group. This has been rectified.

Stock

  • Cost price for Non-Stock items:
    When creating a Stock Issue for a Non-Stock item or when re-costing it, the system now uses Standard cost irrespective of the Stock valuation method defined on the Control Parameter. For non-stock there is no Stock on-hand quantity, so average cost is meaningless.

Subcontracts

  • Subcontract Claims - zero claimed, > 0 certified:
    The system now allows users to save a Subcontract Claim that has a $0 claimed value but has a greater than $0 certified value. There will be a warning on saving but the user can go ahead and save and approve.

  • Work Orders Period:
    If the date on a Work Order is changed, the corresponding period is now also changed as long as it is open for Purchase Orders.

    Previously only worked for new Work Orders.

Plant

  • Plant movement audit data:
    In order to simplify the reporting of changes on Plant items like Driver or Location change, the system now records this information in the EventLog table rather than the Audit table.

    There is a script to initialise the EventLog table with existing Plant movement data from the Audit table:
    It inserts any valid data from Audit to EventLog for Driver Change and Location Change, and only does it once which is when there is no Plant movement data on EventLog at all. It does not delete any data from the Audit table.

Timesheets

  • Notes on a Timesheet line copied to a Plant Issue created from a Timesheet line:
    When a Plant transaction is created from a Time transaction, the Notes on the time transactions are appended to any notes on the Plant transactions.

    This enhancement has been done to support those scenarios where the billing is Cost Plus and the Plant rate is Wet hire, so the actual time transaction is written off, and the Plant transaction is sold and included in the Invoice with all the appropriate details entered by the employee that did the work. This applies to Mobile timesheets as well as Desktop timesheets.

  • EBA Profiles - Allowances:


    A Job column has been added to the Allowances tab on an EBA Profile. This is used to redirect the allowance to a different Job and Activity. Allowances generated in this way will create an additional timesheet line using the designated job and activity, and will only create a new line if both a Job and Activity have been populated here (if only a Job has been designated but no Activity the new allowance line will not be created). Any costs associated with this line will be moved from the original transaction to the newly created line.
    A Job Code in an Allowance line in the Profile is optional.

Billing

  • Contract Claim Job Invoices - Due date earlier than Posting Date?
    In some cases due to a delay in the Approval of the Job Invoice or due to very short payment terms, etc, the Due Date of the Invoice is before the Posting Date. In those cases, the system will use the Posting Date as the Due Date when exporting to the financials. This is applicable for all financial integrations. The Due Date on the Job Invoice itself is not updated.

  • Contract Claim Schedules sequence number on reports:
    The following Contract Claim reports have been updated to support the new Claim Schedule Sequence Number to allow for custom display order of these Schedules.

    • wbContractClaim002

    • wbContractClaim012

    • wbContractClaim005

    • wbContractClaim015

  • Job Invoice Discussion link:
    An email is automatically sent to the message recipient when a message is sent from a Workflow| Messages popup screen. This email has a direct link to the Job Invoice but the link was not working. This has been rectified now:

Month End

  • Processes - Changes to WIP Generation:

    • WIP records will not be created where jobs are finalised.

    • Existing WIP records for the period will be removed even if they are in other batches.

System Setup

  • Jobs:
    New screen to create and maintain Contracts and Subcontract types:

Administration

  • Editing Users data:
    The existing permission 'Edit User Security Data' enables a user to edit all fields in the 'Main', 'Application Access', 'Roles', and 'Settings' tabs. However, Login Type and Reset function were still available if a user did not have these permissions. This has been changed and only users with this permission will be able to update those fields.

General

  • Workflow Schema messages:
    On any screen where there is a Workflow | Messages button, a count will now appear to reflect the number of messages sent using this feature. At a glance, this will indicate to the user there are messages and that there has been some communication about this document.

Integrations

Upvise

  • Timesheet import from Upvise to Workbench:
    Where clients have multiple people with the same name, the integration will now prioritise the employee contact record when importing time into Workbench. This will allow you to maintain supplier contacts with the same name as employees, time will land in Workbench against the employee contact record.

  • Update to the logic used in the matching of Upvise docket POs:
    Where a docket is recorded in Upvise the integration back to Workbench has been enhanced and the matching of this Docket to a Docket PO in Workbench will now use the following logic:
    Dockets recorded in Upvise Daily Diary will match against both the oldest Approved PO for that supplier as well as the Workbench Job (Upvise Project) selected on the docket. The Docket Work Centre will be recorded as it appears on the docket, not on the PO (no change to this logic).

Xero

  • Xero SDK update:
    In order to keep up-to-date with the Xero API Integration, Workbench has updated the Xero SDK version.
    Also some changes have been done on the Payroll integration to export Timesheets which will soon enable us to support Leave requests in Payroll batch exports. This is currently under beta testing.

  • No labels