Workbench Release Notes

Note:

Hotfix Release 4.5.45.4

Released - 25 January 2023

• Application Clients - creating new token for Workbench API access:
  Clicking on the Authorize button on the Application Client screen a second time (to generate a new token) was causing an error. This has been rectified.

General Release 4.5.45.3

Scheduled Release - 23 January 2023

Beta Release 4.5.

...

45.1

Version available from 12 December 2022Scheduled Release - 16 January 2023

New

...

Features

Upvise

...

Jobs

• Job Details - new People tab - Visibility of who is involved in each Job (internal and external):
  Often on large projects there are many people involved, internal and external, like client's representatives, tradees, and any other stakeholders like Councils. This is the right space to keep a list of all people involved and add a description of their specific Role for this particular project. The list of people to choose from comes from the People screen. To add new people create them first on the People screen and then add them here.

...

Month End

• Auto-batching of Plant Issues and Disbursements entered via Timesheets/Daysheets/Upvise:
  Currently any plant issue or disbursement transactions entered on Daily Timesheets, Daysheets Timesheets, or imported from Upvise need to be batched manually (from Batch Labour Journal).

  We have made a change to batch these transactions automatically on a System batch, so you don’t need to remember to batch them, and to reduce manual steps on Month End processes. 🤩

Feature Revisions

Jobs

• Job Transactions report:
  added Batch Number to wbJobTransaction001 report

• Job Budget performance:
  Re-engineered Job Budget Detail screen to improve performance when loading a budget with a large number of rows.

• Job Budget markup rounding:
  When applying a markup % on a budget line, the FC Revenue is now calculated in a way that avoids rounding issues: Total Cost + markup,
  rather than Qty * (Cost Rate + markup)
  

• Job Import - new columns:
  Additional columns have been added to our current Job import:

  • Job Group (Category and Code)

  • Client Reference

  • Asset Reference

Purchasing

• Inwards goods access with new licences:
  Users with access to Purchasing Module will have access to the Inwards Goods screen, and no longer require a Stock Management or Advanced Procurement site licence.

Stock

• Stock reports:
  The Stock Item filter on Stock reports has changed from text to picker.

• Repricing of Non- Stock issues on Stock legacy mode:
  When using the Stock module in a legacy mode (Control parameter 'Stock Module Process' = Legacy), the repricing logic has been changed to always use the Cost in the location if it exists, otherwise use the item default rate. This re-pricing is always performed after saving a Stock Issues batch.

Subcontracts

• Subcontract Claims List - improved performance:
  A default filter of Status not equal to ‘Updated’ has been added to this screen and several enhancements have been made to load the claims on this screen faster.

• Manual batching of Subcontract Claims:
  When manually batching subcontract claims, the number of claims included in the batch is now displayed on the green message after successfully saving the batch. It provides an idea of what has been included and the batch can be printed if more details are required:
  

  Image Removed

Month End

• Utilities

  • New utility to Write Off Payroll Transactions:
    Use this utility to write off Job transactions that match the criteria in the filters ( Transaction date and/or Time Code), and any payroll transactions related to those.
    The invoice number on each transaction is set to InvoiceNumber = 99999999 and is flagged as Written off for billing purposes.

Integrations

Upvise

• Punch item Display:
  Introduced an enhancement in our custom punch item display setting to include Custom Columns displayed control for the equipment module in Upvise Equipment display Options.
  

  Image Removed

• Workbench Log Number in Upvise:
  "Get Log number" function has been made available where a user can use the button in a new Job in Upvise, to obtain the Workbench service log number immediately on the web when scheduling a new Job. The "get Log" function has been optimized to be compatible with Project Jobs, Site Jobs and Equipment Jobs.
  

• Plant assignments and Plant Return enhancements:
  New "Plant Return" form which will mark the plant item as "returned" in the Workbench plant assignment.
  In Upvise, this Plant Return form will also unallocate the plant item from the project and change the custom flag on the plant item to "Inspection Required".

  This form also supports Plant Return Charges. This can be used to record the condition of the plant item when it is returned and charge any damages or refuelling costs to the Job in Workbench (the Job the plant was assigned to) to recover those costs from your client. This Subform will use the output schedule on the Workbench Job/ Upvise Project, and the costs will be recorded as Job Outputs.
  

• Upvise Jobs to use numbering from Workbench:
  Enhancements have been made to ensure that the right numbering sequence defined in the Workbench setting is used when creating Upvise Jobs. Regardless of the point of creation of an Upvise job the log sequence will be sourced from the numbering setting.Budget

  • New Job Budget creation from Perform button:
    Creating a new Job Budget from within an existing Job Budget with the Perform button option was not working and this has been rectified.

    Image Added

Service Desk

• Service Logs - ability to Finalise a Log:
  For those scenarios where the charge type on the Log’s job is not Input / Output Based Billing charge type (like Contract Claims charge type) we have added the ability to flag a Log as Finalised, to indicate that the Log has actually been billed and there is no further action required. No further costs can be added once finalised. As there is no direct link between Job transactions/Job outputs and an Invoice (Get Sales is not used to select the transactions to be invoiced), the Finalising of a Log indicates the work is complete, billed and no more transactions/Costs can be added to it.
  
  This adds a fourth Log Workflow status: Entered, Allocated, Completed or Finalised (depending on the Log’s Job charge type).
  
  The user in charge of billing knows the Log has been completed and billed and can proceed to flag it as Finalised. This can be done from:

  • the Log with the new Save and Finalise button

    Image Added

  • from the Invoice with the new Save and Finalise Log button.

    Image Added

  • If it requires to be reopened a Reopen & Unfinalise button will be available which will reset the Log to Allocated.

    Image Added

Month End

• WIP report:
  A specific scenario on the WIP report where duplicate jobs were being displayed has been fixed.

• Utilities:
  A change has been made to wbUtilityRebatchNegativeInvoices utility so that it cannot be run if the 'Batch Negative Claims as Credits'  Control parameter is set to Yes. It can be one or the other, not both. otherwise, we end up with a Credit with negative values which is not correct and it will error when exporting.

Administration

• Impersonate To and Scaffold access:
  These features were not available for a user with the new System Admin licence. This has been rectified.

Integrations

Upvise

• Upvise Jobs - New Get Log button:
  "Get Log No" is a button that will immediately call the Workbench API to generate a log number in Workbench and can only be used from Upvise web application. 

  When the log is generated in Workbench, only simple information is populated such as the project and date. 

• Synch of Leave requests in Upvise to Workbench:
  A change has been made so that when Leave requests are synched from Upvise to Workbench the leave dates (Start and End dates) are validated rather than days and hours.

• Default Plant Items owner in Upvise:
  A change has been made to default the equipment owner to "everyone” once the plant item is synced to Upvise from Workbench.

Xero

• Improved error messages on Payroll exports:
  Although Xero allows duplicate Payroll Calendar names and Earning names, this is not supported in the API integration. To help users troubleshoot these kinds of errors we have added a more specific error message that will read like the message below:
  'There are duplicate Pay Items in Xero with the name xxxx. Regardless of whether them being active or inactive, the Pay Item name must be unique for Workbench Xero integration to work. Edit the name in Xero, make it unique and try again. Example: Tool Allowance vs Tool Allowance OLD, Fortnightly Calendar vs Fortnightly Calendar OLD'