Workbench Release Notes

Beta Release 4.6.11.1

Scheduled Release - 03 July 2023

New Features

Jobs

• Job Enquiry, Transactions tab - support Margin and Markup:
  Users want the option to see Margin or Markup and present the values as a % instead of a decimal.
  We added new columns in the Transactions tab and users can choose to hide or enable their preferred columns from Grid Management.

  • New column Markup after Selling column (Selling-Cost)

  • Renamed Margin as Markup% ((Selling-Cost)/ Cost). Format as %

  • New column Margin% column after relabelled Markup% ((Selling-Cost)/ Selling). Format as %

  • New Grid management option for Transactions tab.
    

    

Stock

• Extension Columns are now available for Stock items. They use one unique view called 'Web Portal'.

Plant

Main tab - Redesign

The Main tab has been redesigned to provide a maintenance-centric view that is more operationally relevant rather than the prior static attributes. This is now available for early adopters.

...

S. Go To button accesses other related screens.

Upvise

• PDF attachments:
  We have enhanced the PDF import function beyond Service logs and daysheets to allow PDF form data to sync and attach to the below in Workbench:

  • Equipment (wb Plant): Any form submitted against equipment should import a PDF as an attachment on the plant item.

  • Project (wb jobs): Any project form should import a PDF as an attachment on the Upvise job.

  • Contacts (wb People): Any contact linked form should import a PDF as an attachment on the Person Record in Workbench

Feature Revisions

Jobs

• Budget - Default markup value:
  The default Markup on At Cost Element and At Activity, Work Centre budget types used to be -100% of the Cost, but in a recent fix we changed that behaviour. On this release, we are reverting back to the historical behaviour of defaulting the Markup % to -100%. Most of our clients are used to this behaviour and we want to avoid disruption to their processes wherever we can.
  

  

Purchasing

• Purchase Orders workflow approvals:
  Enhancements have been done to PO workflows to accommodate the below:

  1. Enforce sorting by PurchaseOrderLineID on retrieval of "first PO line" for entity matching to ensure consistent results.

  2. Use the PO Total, not the grid page 1 total for obtaining the list of optional workflow assignees.

• Inwards Goods on Zero Value PO Lines:
  In cases where there is a PO line with Qty > 0 but the rate and value = 0, the PO is not displayed. We have rectified that and the rule for a PO to be displayed in an Inwards Goods is now OutstandingQuantity >0 OR OutstandingCost > 0

• ‘On Hold’ AP Invoice:
  Taking an AP Invoice off ‘On Hold’ now updates back to its AP Voucher if one exists.

Subcontracts

• Subcontract Claim deletion:
  When deleting a subcontract claim, any Work Orders lines that were claimed in it will be reopened and the outstanding values recalculated. Any lines that were Completed will be uncompleted.

• Subcontract Over Certification:
  Positive claims can only be certified to date between zero and the total commitment value unless setting Subcontract Over Certification allows for over-certification.
  The same principle works for negative claims.
  We have enhanced the warning/error message so it makes sense for both positive and negative overclaiming:
  From “The Certified value exceeds the Subcontract Commitment“

  To “The Certified value is not within the Subcontract Commitment“

Datasheets

• Plant Groups on Mobile Datasheets:
  The Plant Groups selection on mobile datasheets linked to Plant items now excludes pricing groups.

Service Desk

• Service Log number on ARinvoice:
  When creating an AR Invoice from a log, the Order Number on the Job Invoice is now populated with the Service Order Number from the Log number. Stored procedure wbrsInvoiceLinesTransactions now includes LogHeaderIDLog’s details.

Month End

• Job Transactions Reallocation:
  The Description from the original transaction is now populated into the Auto Cr transaction to make it easier to identify these transactions on other screens.
  

  

  
  

• Job Adjustment batch - lines outside of batch period:
  Depending on the financial system Workbench integrates with, it may or may not be appropriate to have transactions dated outside of the batch period. To handle these scenarios the system now draws the users' attention to these lines rather than to disallow their entry. When a batch line is dated outside of the batch period, the line is highlighted in red and it is up to the user to act on this warning.
  may require clearing Application Cache
  

  

System Setup

• Workflow - recognising subjobs:
  When matching the Workflow schema’s entities the system now recognises subjobs of those Jobs defined in the Entities tab when searching for a matching workflow for the document when it is submitted.
  
  This means subjobs do not need to be added to the Workflow’s schemas anymore. Adding a parent Job is sufficient.
  

  

General

• Management Reports menu:
  All menus in the site map would freeze after a user with a Job Costing licence tried to access the Management Reports menu. This has been rectified.

Integrations

Upvise

• Timesheets:

  • Use of an Employee’s Default Activity:
    Where there is no activity populated on the Upvise Timeslot, the integration between Upvise and Workbench will fall back on the Default Activity of the employee in Workbench and proceed to generate the timesheet line. 

    The timesheet will not be created if:

    1. the default activity is not an activity on the cost activity group on the job.

    2. there is no default activity on the employee, and no activity populated in Upvise timeslot. 

• Sync Expense Claims as approved - Standard approval only:
  For those using standard approval of Expense Claims, to avoid an Expense requiring to be approved again in Workbench after it has been synced from Upvise, we have introduced a new setting to indicate that the Expense Claims will be synced as approved. Setting: “Upvise Sync Expense Claims Approved”.

• Plant Sub Equipment sync:
  Upvise Parent Equipment now displays in Workbench Parent plant field on the plant job in Workbench.
  Example: For WCA001 I have added Sub Equipment TRA008 in Upvise:
  

  

  After the data sync from Upvise, on TRA008 you can now see the Parent Plant in Workbench plant details tab:

...

• Integration error messages improvements:
  Upvise integration error messages have been enhanced to make them easier to understand to the end user. One specific example is around Plant issues sync where the plant issues form is deleted in Upvise, and plant issues cannot be imported into Workbench. The error message will be more descriptive to explain what Plant item & date this is for.