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

« Previous Version 19 Next »

Workbench Release Notes

IN PROGRESS

Beta Release 4.5.42.1

Scheduled Release - 14 November 2022

Feature Revisions

Purchasing

  • Purchase Orders - Foreign Currency rate:
    When approving a PO, the FC rate was reverted to the default value even when ticking Fixed FC. This has been reverted.


Timesheets

  • Inactive Employee Classes on Timesheet Administration:
    On the Timesheet Administration screen, an Admin user could select and change employee class on each line. Inactive Employee Classes and not selectable in this field anymore.
    The selection of the Employee Class has changed from a dropdown to a picker (same as the other fields).

This may require a reset of the Grid on Grid Management for ‘Timesheet Daily Admin’ to have the picker displayed.

Billing

  • Contract Claim - schedules available for selection:
    When searching for available Contract Claim Schedules on a Get Sales screen of a Claim, the schedules shown were not limited to those ones linked to the Job. This has been reverted.

  • Input Jobs - Summary tab:
    Margin % (Sales/Profit) has been added to the Summary Invoice tab, and the order of the existing columns has been re-arranged.


Quotes

  • Repricing Stock item lines using Markup%:
    The repricing functionality on 'At Revenue and Cost Element' quotes has been enhanced so it uses the Markup % on a Quote line to calculate the Sell rate. It uses the Default Cost Rate on the Stock items multiplied by the Markup% defined on the Quote line.

Service Desk

  • Time-out error when opening Logs screen:
    A time-out error "Wait Operation Timed Out" was coming up when opening Logs. This has been rectified.

  • Enhancements to ‘Billed' status:
    There are some cases when the 'Billed’ status was not reflecting the actual status of the Log:

    • the user clicks [Invoice] but abandons the process.

    • the Log is reopened after being billed, and additional costs are added.

To cater for the above scenarios, the Log Status has been split into Progress Status of the Log & the Billing Status of the Log, and they both display together for better visibility.

The example below is a Log that was billed, completed and then reopened, however, no further Costs or Outputs have been added, so it still reflects its Billed status.

Month End

  • Utilities - wbUnexportAPARInvoice:
    This utility has been updated to handle Invoices approved with workflow approvals. Once an Invoice is reset the workflow status is now reset as well.

Integrations

Business Central

  • Workbench Profit Centre added to AR Invoice Header on Exported AR Invoices
    Workbench PC will be saved as an Invoice header dimension in Business Central. An AR Invoice Header Job can belong to a different Profit Centre than the Jobs of the invoice lines.

SAP B1

  • Job Receipts and Payment:
    The process for importing Job receipts and Payments from SAP B1 to Workbench has been updated to ensure all of them come through.

Upvise

  • Training Matrix:
    Tasks generated from Training Records are now assigned to the administrator as well as the employee. Training Record forms now assign the employee as the owner as well as the person submitting the record. This will help with Data security and visibility of records for standard users whilst on a job site if audited.

  • Job Completion Notes on Logs:
    A change has been made to always take the latest completion note on the Upvise Job and replace any existing notes in the log completion. Completion notes will be trimmed to 2000 characters in line with workbench Log completion limitations.

  • New User creation:
    When creating a new user in Workbench that is exported to Upvise, there is a process that validates that the email of the Workbench User does not already exist in Upvise. Some minor changes have been done to this to avoid invalid error messages.

  • Support for Upvise Jobs linked to an Upvise Site:
    For those scenarios where Upvise Jobs are created from an Upvise Site (from the Assets app), the project (Workbench Job) will be coming from the Project on the Site, rather than having a Project populated on the Job.


    Upvise allows having either a Project selected on the Job or a Site, not both. The integration with Workbench now supports this, so the Workbench Job on the Workbench Log is populated from the right source and validated.
    This assumes that the Sites have a custom field called 'Project'

  • No labels