PNE-1819

https://slxdev.atlassian.net/browse/PNE-1819

Client has installed SLX software with no issues initially.
Shoplogix.Connector.exe.Config showed nothing as True; manually changed OPC to true. Log files showing all good except Modbus where in the 2021-04-12 Shoplogix.Connector.txt we see ModbusProcess process exited: Exit Code: -532462766

In the 2021-04-12 Shoplogix.Modbus.txt, the file wants to reference D:\BuildAgent\work\ yet there is no D drive

SLX will not create OPC directories for machines for any sort of validation

PNE-1796

https://slxdev.atlassian.net/browse/PNE-1796

Issue: Data for the current date/month is not available on the analytics portal.
Upon looking into it we found only 2 months (JAN & FEB) are available for selection.

Fixed by consolidating manual signals to at most one minute buckets.

PNE-1764

https://slxdev.atlassian.net/browse/PNE-1764

Encountered an error while exporting shift calendars across machines. On specific days (mostly at the beginning of month), night shift breaks are not getting copied. When exported from March all the months staring from April had missing breaks at the beginning of the month.

PNE-819

https://slxdev.atlassian.net/browse/PNE-819?filter=10130

There was a discrepancy between the values listed in the OEE Gauge and the Good Production Gauge when the values for scrap were fractional.

This has been changed to round down fractional scrap values to the nearest whole number for consistency.

PROD-366

https://slxdev.atlassian.net/browse/PROD-366

Previously, Shoplogix's Quality module allowed the end-user to set Quality inspections and group them using different job-based conditional groups as a way to determine their triggers/success criteria.

However, this is not this same behavior between SPC conditions and job-based conditions.

Example:

1. End-user sets the optimal upper/lower limits as success criteria for Product A, and runs Product A.

2. A new product--Product B--is scheduled to run in the afternoon. Product B's upper/lower limits are different than Product A.

3. PREVIOUS STATE: End-user needs to manually change the SPC upper/lower limits before running Product B.
   CURRENT STATE: SLX system automatically changes upper/lower limits based on job-based conditions, ensuring Product B’s SPC variables are evaluated against correct new success criteria.

PNE-1786

https://slxdev.atlassian.net/browse/PNE-1786

The number of available machine classifications, (Dim Machines) has been expanded from 5 to 9 machines. This has been done in order to provide more user flexibility.