4.7.12 - 14 Apr 2025
Workbench Release Notes
IN PROGRESS
Upcoming Functionality & News
Upvise Purchase Orders - Mandatory PO lines
To enhance accuracy and consistency, all Purchase Orders submitted in Upvise will now require at least one PO line. Users will no longer be able to submit a PO without manually adding at least one line before submission.
New Webinar
Forecasting and preview of new % Complete method
Register here
Unlock the Future of Forecasting with Workbench
This session is essential for anyone looking to refine their forecasting strategies and get the most out of Workbench.
Join us for an exclusive Webinar on Cost-to-Complete Forecasting in Workbench, featuring the new % Complete Forecasting Method.
What You’ll Learn:
How to maximize Workbench’s forecasting capabilities
Managing Balance of Budgets
Utilizing Resource Planning
A deep dive into the new % Complete Forecasting Method
Practical insights to improve forecasting accuracy
Don’t miss this opportunity. Stay on top of your projects with Workbench!
Reserve your spot now.
Introducing % Complete in Contract Forecasting
We will soon be introducing a % Complete measure and the ability to review and update project progress directly from the main forecast screen, which:
greatly reduces the clicks required to review progress,
and simplifies the adjustment calculation.
Seeing where you are at on each area of the job at a glance (% of how much you have completed) makes the exercise of Forecasting much easier.
The method we have chosen to measure the suggested % completed is based on Actual Cost vs Budget, as we consider this applies across the majority of use cases.
Stay tuned.
Upvise Button - Form Quick Links in v4.7.12
In v4.7.12, we are updating Button-Quick Links to make the button code dynamic. To ensure Buttons Work After the Change, each button’s label matches the exact name of the intended form template. Read more
Mandatory email address for Upvise Users
In an upcoming release, the email address will become a required field if a user requires access to Upvise.
New Features
Jobs
Jobs List redesign with clear job level hierarchy
The Jobs list has been redesigned and it now reflects the Job level hierarchy with an indentation (the further to the right, the lower the Job level).
Custom Views have also been added to the Jobs List.
Feature Revisions
Jobs
Adding BOM header in the budget
- Adding BOM header to a Rev line on a Costsheet
Dockets & Daysheets
Timesheets
Resource Scheduler
Administration
Fixes & Technical changes
Upvise
Plant Issues- Import
The integration will now automatically use the employee name (Upvise user) who created the Plant Issue Form in Upvise as the assigned person in the data table upon import.
Upvise Leave Application - Leave Events
Leave events will now display with specific start and end times—rather than as "Multiday"—in both the Planned Schedule of the Timesheet module and in the Jobs module.
The displayed times are based on the “Work Hour Start” and “Daily Work Hours” settings configured in the Timesheet module.
Upvise Framework Changes 1st May 2025
Upvise will implement the following framework changes on 1st May 2025. To ensure ongoing compatibility, Workbench Development team will apply the required updates to all Workbench-related code ahead of this deadline.
For clients managing their own custom code, please review and action the changes outlined below:
Key Change: Map Class Renamed to MapView
To prevent conflicts with the standard JavaScript Map class (introduced in ES6), the Upvise Map class is being renamed to MapView.
What you need to do:
Replace all
Map.XXX()method calls withMapView.XXX().Redeploy your custom Upvise applications.
⚠️ Note: The method signatures and parameters remain unchanged.
Examples:
Map.addItem() => MapView.addItem() Map.show() => MapView.show()
MapViewis available now, so you can make these updates immediately.
The legacyMap.XXX()methods will be removed on 1st May 2025.
Deprecated Private APIs
The following private APIs will also be removed from the Upvise framework on the same date:
Map._parsePoint()– RemovedMap._distance()– RemovedMap.forceRecenter()– Removed
➤ UseMapView.center(geo)instead.HashMap.initDays()– RemovedHashMap.fromArray(array, key)– Removed
➤ Usenew HashMap(array, key)instead.
Forewarning: Update to Button-Quick Links in Upvise (v4.7.12)
What’s Changing?
In v4.7.12, we are updating Button-Quick Links to make the button code dynamic. Instead of being hardcoded to specific form templates, buttons will now use the button label as the identifier for form templates. This means button labels must exactly match the form template name for the button to function correctly. The following improvements will be applied:
Cater for the “disabled” form template status
Pop-up message: An active Forms template 'template name' does not exist.
Cater for the “lock completed jobs” setting when job status is complete
Pop-up message: This job has been completed - please reopen the job to add a new form.
Rework button code to use the button label to specify the form template
Pop-up message: An active Forms template 'template name' does not exist.
Ensure button code works across Jobs, Projects, Equipment, and Contacts
Consider user roles
Pop-up message: You do not have permission to access the '" template name"' form.
Consider button roles
Pop-up message: You do not have permission to access the '" template name "' form.
Prevent form creation via the button if the template is not linked to the master file
Pop-up message: "template name" should be linked to "linked record- e.g. contact"
Why This is Beneficial?
Currently (before v4.7.12), buttons are hard-coded and limited to the following form templates only:
Job Purchase Order (linked to a job)
Daily Diary (linked to a project)
Mechanic Diary (linked to a job)
Training Record (linked to contacts)
Leave Application (linked to contacts)
Equipment Record (linked to equipment)
After v4.7.12:
Buttons will work across Jobs, Projects, Equipment, and Contacts, increasing flexibility.
Reduces the need for custom code changes.
Reduces errors and simplifies maintenance by removing hardcoded template links.
To Ensure Buttons Work After the Change:
Verify Button Labels – Ensure that each button’s label matches the exact name of the intended form template.
Button Label | Form Template Name |
 |  |
Integration
MYOB Acumatica
SAP B1
Xero
Upvise
NEW- Upvise Mobile App
Android version 9.1.1
New Feature: You can now capture and share videos directly within the app.
Improved Syncing: Performance optimisations for smoother and faster data sync.
Conflict Resolution: Better handling of deleted records when syncing across multiple devices.
Smarter Editing: The software keyboard now auto-opens when editing text fields.
Updated Look: Refreshed toolbar icons for a more modern interface.
Security Enhancements: Important updates to keep your data protected.
🤖 Requires Android 9 or later
iOS version 9.1.2 (iPhone & iPad)
New Feature: You can now attach documents directly within the app.
Improved Syncing: Performance optimisations for faster and more reliable data sync.
Conflict Resolution: Better handling of deleted records when syncing across multiple devices.
Updated Look: Refreshed toolbar icons for a cleaner user experience.
Security Enhancements: Important updates to keep your data protected.
Bug Fix: Resolved an issue with the "Signature on Submit" feature.
📱 Requires iOS 12.0 or later
Upvise Purchase Orders - Mandatory PO lines
In v4.7.12, we are introducing an update to improve how Purchase Orders are managed in Upvise.
What’s Changing?
To enhance accuracy and consistency, all Purchase Orders submitted in Upvise will now require at least one PO line. Users will no longer be able to submit a PO without manually adding at least one line before submission.
Why Is This Beneficial?
This update ensures that POs are able to be matched in Workbench invoicing processes, reducing errors and improving efficiency. By requiring PO lines upfront, we eliminate the need to:
Re-open a PO to add missing lines.
Re-approve a PO after adding the required details.
This streamlined process will save time and prevent unnecessary workflow disruptions in Workbench.
Things we are busy working on...
Custom Views on List screens, and exploring the ability to add extension columns to these views. This will expand your reporting ability on the List screens.
Month End Process: controlled and easy to follow.
New status to track whether POs and WOs have been sent to Suppliers/Subcontractors.