Workbench Release Notes
Note:
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This version will not be released to any instances hosted in AWS. Next upgrade will be done on the new year. |
Beta Release 4.5.44.1
Version available from 12 December 2022
New Feature
Upvise
Equipment Service History:
Introduced an Equipment "Service History" utility available on each equipment item. Workbench's standard Servicing Forms are compatible with this feature. This will allow users to extract a "Service History" summary report via PDF for each equipment item. Please engage your consultant or support to arrange for this enhancement to be deployed.
Feature Revisions
Jobs
Job Transactions report:
added Batch Number to wbJobTransaction001 reportJob 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 license.
Stock
Stock reports:
The Stock Item criteria filter on Stock reports has chnaged 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 ahen after saving a Stock Issue sbatchIssues 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:
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 an dand/or Time Code), and any payroll transactions related to those.
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.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 in 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 Outputs 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 un-allocate unallocate the plant item from the project and change the custom flag on the plant item to "Inspection Required".This form also supports Plant Outputs. The Output Subform will use the output schedule on the workbench Job/ Upvise Project. This can be used to record the condition of the plant item when it is returned and charge any damages or refueling refuelling costs to the job in workbench Workbench to recover those costs from your client.
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.