Workbench Release Notes

Feature Revisions

Jobs

• Budgets - Adding to an Inactive Procurement List:
  When adding Budget lines to an inactive Procurement list, a warning message is now displayed, and it is up to the user to go ahead or not (depending on their internal processes).
  Warning “The selected Procurement List is set as inactive.”
  

  

• Contracts - Receipt details:
  As part of the Project Trust Account functionality we are developing, we have added a new column in Job Receipts to display the GL account for the bank account the AR Invoice was paid into. This will be used in Workbench to verify, if the Contract has a Project Trust Account (PTA), that the funds were deposited into the PTA as expected, or highlight it if they were not.
  We have to update the integration with the different financial systems APIs for this. MYOB Account Right is the first one to support this new field. We will add other systems shortly.
  

  

Stock

• Standardising field names:
  In the Stock module, we have made a few changes to the field names to make sure they are consistent across all the Stock screens. Also, note that the Stock method in use is underlined:
  

  

Plant

• Plant Maintenance Logs:

  • New Setting to control visible tabs on Plant Maintenance Logs:
    Service Logs and Plant Logs shared a common setting ‘Log Maintenance Tabs’ to control visibility of tabs in the Log. This has been split, and the Plant Maintenance Log has its setting, so changes to one won’t affect the other.
    New setting name: ‘Plant Maintenance Log Tabs’

  • A new ‘Workflow Status’ column was added to the Logs list.
    

• A few enhancements in Plant Items List:

  • In the Service section, we splitted the Status field, and added two separate columns to display the Days due of the Log and the Next metering reading due date:

    • Days Due = Next Service Date - Today

    • Meter Due = Next Service Reading - Latest Reading

  • The existing Status description now shows overdue date.
    

    

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 Regardless of the approval method on Job Invoices (workflow or Standard), Revenue Journals only support Standard . This is because Workflow approval does not really work with $0 amounts.
  Two new control parameters have been added to control the approvals:

• Revenue Journal Approval Process - only Standard supported.

Revenue Journal Approval Process - defaults to Workflow method

approvals and Internal Sales only supports Workflow approvals.

Why?
Workflow approvals don’t work with $0 value invoices (and Revenue Jouranls are a $0 value invoice).
Makes sense to be able to route the approval of an Internal sales based on complex rules that can be configured in a Workflow.


• Who can create and edit Revenue Journals?
  We have introduced a new permission ‘Allow Revenue Journals’, added by default to the 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 makes the creation of a Revenue Journal or Internal Job much easier.
  

  

Quotes

• Import procedure enhancements - wbImportCostSheetScheduleLinesWeb:
  Fixed a bug introduced on the previous release (error message: Error converting data type numeric to numeric.).

• Enhanced Selling calculation on Revenue lines:
  On an At Revenue & Cost lines cost sheet, we have added a field where you can choose how you want the Revenue Selling value to be calculated. So far we had two options, either using Markup % or Sell Rate. We added a third option, Inherit Sell. This helps to understand the selling calculation at a glance.

  • ‘Inherit Sell’ sets the Revenue Sell Rate as the total sell of its cost lines, and auto updates as any cost lines are amended.

  • Markup %,

  • Sell Rate
    

  • 

• Fixed an error when deleting all cost lines (BOM lines) from a Revenue line with a Markup %, where the changes were not saved and the line was back to the original status.
  

Service Desk

• LogNo handling on Voucher and AP Invoice:
  We still had a situation where the Log number was on the AP invoice but was not displaying in the Log. This has been fixed.

System Setup

• Exporting an SSRS report to Word:
  When trying to export an SSRS report as a Word document, with the control parameter Report Server Full Trust mode enabled (=yes), the export failed. This has been rectified.

Administration

• Licence changes:

  • Time Reports have been added to the Standard licence.

  • Plant Reports have been added to the Job Costing licence.

  • Procurement List has been added to Standard licence.

  • System Admin licence access changes:

    • The system now validates that a System Admin licence also has the required Site licences for those modules that require one.

    • This has also been applied to System Admin - Shared Services and System Admin - Tech Support.
      

• Self-Service Licensing - Purchased Licences tab - support for Sharperlight Scheduler licences:
  When a client qualifies for a Sharperlight Scheduler (based on the dollar amount per month), the licence is available to be selectedwill be automatically included.

Upvise

PO line matching when importing Dockets from Upvise

When matching dockets against a docket PO when importing from Upvise, when there are multiple docket POs on the same date, the system now uses the first one for the day (lowest PO number).

Leave Job for Upvise Instances with multiple Fin Cos

Syncing of leave time will now use the correct Leave job for the finco the employee belongs to determined by its Profit Centre.

Forms Application Overwrite function- Deprecated in Upvise

As previously communicated, the utilisation of custom form module overrides has now been deprecated. All workbench code has been moved from the forms module application overwrite and any unsupported functions have been removed.