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 4 Next »

Beta Release 4.4.37.25

Release - 23 Nov 2020

Important Notes

  • Δ Reminder SendGrid Authentication Upgrade - If using our default MailSettings, note that Twilio SendGrid has updated their authentication method, and this must be upgraded by December 9th, 2020 in order to ensure uninterrupted service.
    All AWS Workbench installations will be upgraded as part of our hosting service, However, dealer and on-premise based installations will be the responsibility of the respective party.
    Refer detail in Release Note 4.4.36.

New Features

Purchase Orders Dockets & Upvise

The enhances the formality of using POs with Dockets as introduced in version 4.4.28 with support extended to Upvise Dockets.

A. A field is added to the Upvise Docket form to enter an optional PO Number.

B. The PO Number and Product (Docket Cost Schedule Description) are used to auto resolve the docket link to a PO Line in the Upvise synchronisation process. Should any line fail to be resolved, a sync log warning like 'No Purchase Order Line could be found for PO 800 and Catalogue Line 1233' is recorded.

C. The Dockets with failed PO Lines can be displayed on the Docket List using the filter ‘Unmatched PO Dockets = yes’.

D. Selecting the Docket to display and open the Lines tab that highlights the unmatched lines in RED.

E. The PO Line can then be manually resolved by selecting the required line with the PO Line picker and saving.

Data Extraction - Enhanced supplier configuration

Previously, every time inaccurate OCR extraction was experienced for a supplier, for example Totals are not selectable in the mapping, a ticket had to be raised with support. Now, once the OCR method has been configured by Workbench Support, it can be used on another supplier without support intervention.

There are two enhancements on the supplier’s Lines Config popup:

A. Mode was previously displayed as a ‘Train’ tickbox. It has been tweaked to better indicate the option:

  • Process: The standard processing model for AP invoice extraction i.e. the first 5 invoices require user mapping or confirmation (Image Editor Training Status shows INCOMPLETE), and the subsequent invoices should not require intervention ot just confirmation (Image Editor Training Status shows COMPLETE)

  • In Training: If the supplier is trained (i.e. more than 5 invoices have been processed) but the extraction is incorrect, then use this to put the supplier back into training (Image Editor Training Status shows INCOMPLETE).

  • Manual: The manual mapping of each invoice may be required for non standards line structure due to the use of line narrative (Image Editor Training Status shows MANUAL). This is typically in service type invoices if narratives are used.

B. Previously if the Standard OCR algorithm did not cater correctly for a specific supplier invoice format, such as inability to extract some fields at line level, then support assistance would be required to evaluate the use of alternate OCR algorithms for every supplier.

Note, this still requires Workbench Support to perform the initial configuration prior to use; please raise a FreshDesk ticket for this. Afterwards, this functionality will be available using the OCR list.

  • Standard: This is the default OCR employed and typically successfully extracts the majority of formats.

  • Simple: This is the secondary option and usually handles most cases that Standard OCR does not, the difference it that text is read from the document as an image file instead of a PDF.

  • Enhanced: This is the third option and suited to formats that may include shading that can sometimes interfere with OCR, and if text is non-Latin, for example Arabic, Greek, Cyrillic, Chinese, etc. This is however a much slower process.

Feature Revisions

Timesheets

  • General - The function to Copy a Timesheet has been updated to rectify an issue with periods when copying timesheet lines into a timesheet that straddles a period end.

Purchasing

  • Job Procurement List - Several enhancements have been made to improve the usability.

A. When copying a procurement list, the Job column is now populated with the job on the header where it used to be unspecified.

B. The column order has been amended to lead with Catalogue Line instead of supplier as it is more natural. The supplier will auto populate based on the supplier of the selected catalogue line.

C. When amending the supplier, this will be limited to those including the current item in their catalogue, and will auto populate cost and other fields from the selected supplier. If the item is from the System Catalogue (ie. unmanaged), then any supplier can be selected.

D. A default ‘This’ tickbox has been added which auto populates This for the line based on the Remaining. The default all ‘This’ tickbox will do the same for all lines.

Jobs

  • Job Maintenance -

    • An asset can now be link to the job from the 'References and Dates' tab.

    • Extension columns can now be defined at the Job Work Centre level using the Extension Type ‘JobWorkCentre’ and the ‘Default View’. These are entered on the Extension Columns popup from the Ext. Col. ‘View’ link of the Job Work Centres tab in Job Maintenance.

Transactions

  • Batch (All Types) - The batch Notes field has been increased to 2000 characters. Remember if you do want to see more that what is visible in the default size control, you can use the resize handle to change the control area.

Billing

  • Get Sales, Input/Output, Output Claim - The setting 'Output Quantity Decimal Places' has been applied to the precision of the output or claim quantity value on the respective Get Sales screens.

Administration

  • Utilities - wbUnexportAPARInvoice - This works on subcontract claims, however, it was not defaulting the subcontract claims back to the default batch. This is changed for subcontractor claims.

  • Utilities - wbUtilityGenerateBulkForecastLines - Rectified for an error that was reported when the Job Manager was not specified.

  • No labels