Users: Locked-Out vs Disabled Status 

Historically, a user could be disabled for two reasons: they either left the business and would not be allowed to enter the system again, or they exceeded the number of times permissible for incorrect password entries. The Skill Matrix Report was affected as it included both users locked out due to incorrect password violations and those who permanently left the organization. It was challenging to determine the cause of the disabled status. 

In 8.7.0, a 'Locked Out' status was introduced for those who violated the incorrect password entry limit. The 'disabled' status now only applies to users permanently removed from the system. A locked-out user can be unlocked and can then access the system using the correct password. This change enhances reporting accuracy by allowing the exclusion of permanently disabled users from reports. 

Prohibit Splitting a Batch with an Open Check Results Set 

In the past, if a check results set is not closed before partially completing a batch, it becomes difficult to track which items have been checked, leading to confusion in case of failures.  

For example, if you have 100 items at Op 10, and you check 50 of them, and then partially complete and split without closing the check results set, it’s hard to know what you had checked at the point of completion of the partial quantity. If you have a failure later in the process, the 50 items that you already progressed were probably ok, but if the check results set remained open you can’t tell whether the failure related to the items that had already progressed or the items that remained on the operation i.e. you have a single results set that could apply in some way to two different batches. 

In 8.7, you are not allowed to partially complete and split a batch whilst a check results set is open. In this way, you are fixing the check results set at the point you split the batch. 

Check Item Template (Variable) 

The Check Item Template (variable) enhancement makes decimal places and unit of measure compulsory to ensure accurate and meaningful data entry.  

It prevents the creation of meaningless data, such as undefined measurements, by enforcing proper variable definitions. 

Approval of Pre-Production Workflows, BoMs and Recipes 

In controlled environments, the approval process manages the division of responsibilities through a pending approval status (which can be performed by one user), and then the approval (which can be performed by another user). Historically, the approval process allows for final approval at the point of going into production.  

In 8.7.0, the pre-approval to approval status is introduced earlier in the process as well; at pre-production stage. So, approval must be obtained at pre-production and production stages. This is important because pre-production can create product that can go out to the customer.  

The image shows the statuses of a workflow version in a controlled environment. 

Stock Items and Item Status Screens Improvements 

The old Stock Items screen by default always supported part matching of product and serial numbers. That was both slow, and could return more records than you wanted if you knew the exact serial number.  

In 8.7, that ambiguity was removed by including the flag that allows you to choose if you want to search for an exact match or a partial match. This improved performance by returning the records that you want. 

Test Plan Manager Excel and CSV Exports 

Previously, the Test Plan Manager would export all columns which would include several that were not of any use to the user. In 8.7, you can select which columns to include when exporting. 

Materialised Views 

The following improvements were made to the Materialized Views screen: 

• The date column can be sorted, and the format was changed to the correct data type (e.g., dd/mm/yyyy for the UK). 
• The new Materialised View Refresh History button allows users to review the history of materialized view refreshes, providing insights into when the data was last updated. This feature is particularly useful for users who rely on routine analytics reports that are generated from Materialised Views (such as many of the analytics reports), as it helps them ensure that the data is up-to-date and reliable. The feature is more relevant for development systems, as live systems should automatically refresh without issues, making this a troubleshooting tool for development environments. 

Location Deactivation 

Locations are linked to several different entries such as default product locations, they can be assigned products, they can have products in them, etc. 

Previously, you could just deactivate them which would invalidate many things in the system such as products, work centres and inventory. 

In 8.7, new validation controls have been introduced which prevent users from deactivating locations that are linked to other entities, such as products or work centres, without resolving the dependencies first. 

This feature ensures data integrity by preventing the creation of invalid data or orphaned records when deactivating locations. 

Public API 

The APIs continue to be improved in 8.7. 

MaterialItem 

Perform an adjustment of a material item’s actual qty through the public API. 

CreateProductSpecific Workflow 

Added targetworkflowversionstatus to: POST/api/Workflow/CreatePoductSpecific 

This allows you to create workflow in approved status. It cannot be set to approved if workflowtype requires an e-signature. 

Upsert Workflow Version 

Added a workflow version upsert API that will allow updating of an existing workflow version. 

Attendance API 

When sending multiple clock-in requests for the same user, the call fails but the error message does not indicate that the user is already clocked in. A user-friendly message indicating the user is already clocked-in has been added. 

Un-booked Hours in Attendance Summary Report 

The attendance summary report is now updated to include 'un-booked time', allowing the user to identify easily how much of the operator's time on shift is unaccounted for. 

Upload JPEG Image Files 

This enhancement allows you to upload .jpeg image type to those that were already supported; .png, .bmp and .jpg. This is to support images originating from Apple devices which use JPEG for image storage natively.  

If a User takes a picture with an apple device with its native Camera Application, then it saves it as a JPEG image. With the Item Document Action users can upload pictures from their camera roll. Allowing JPEG would mean that an Apple user would not have to convert the image file to a supported image file before uploading.