IN PROGRESS
Workbench Release Notes
Upvise
Upvise is releasing updates to enhance performance and security
Before 1st May 2024...
On-premise clients will be required to upgrade to Workbench version 4.6.25 or later. Clients hosted in AWS will be upgraded automatically.
Download latest Upvise mobile app v7.0 (iphone) or v7.0.1 (android)
Bookmark the new Upvise url: https://s3.upvise.com
Re-generate Public Form URLs and PowerBI/Sharperlight export URLs
New Features
Lists
Feature Revisions
Jobs
Management Reports
Purchasing
Subcontracts
Leave Management
Billing
Approval of Revenue Journals & Internal Sales:
The approvals of Revenue Journals are now only done by the Standard method only (where you assign it to a specific user for approval). So regardless of the approval method on Job Invoices (workflow or Standard), Revenue Jouranls only support Standard. This is because Workflow apporval do not really work with $0 amounts.
Two new control parameters have been added to control the apporvals:Revenue Journal Approval Process - only Standard supported.
Revenue Journal Approval Process - defaults to Workflow method.
Who can create and edit Revenue Journals?
We have introduced a new permission ‘Allow Revenue Journals’, added by default to Finance Role.Users that do not have this permission will not see the New Revenue Jornal button, and will not be able to edit existing ones.
New options on New Job Invoice:
The New Invoice button in Job Sales Invoices now has specific options to create either a New Internal Sales invoice or a New Revenue Journal. The selection of the Job selection within the new document will be filtered by the document type selected. This is makes the creation of a Revenue Journal or Internal Job much easier.
Quotes
Import procedure enhancements - wbImportCostSheetScheduleLinesWeb:
Fixed a bug introduced on previous release (error message: Error converting data type numeric to numeric.).
Service Desk
LogNo handling on Voucher and AP Invoice:
We still had situation where Log number was on the AP invoice but was not displaying in the Log. This has been fixed.