Release Notes 5.0.0.21047

When customers can expect in this update:

Group 1: July 12, 2022

Group 2: July 14, 2022

Group 3: July 21, 2022

Highlight from this release:

  • If reason ID is empty while importing data, the ID will be created. Also, error description is improved to describe duplicated names/reasonIDs.

Bug Fixes

PNE-2963

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

Problem: Getting message that duplicates exist.

Steps: Export the CSV and add some new downtimes. Save and export to CSV in excel. Import and get duplicate error.

SAAS124 / Slicer PC1 is the machine

Solution: Error will be displayed to the user so they can correct it:

PNE-2940

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

In the month of May (Saas11) and June(Saas120, machines Chosen and Ines), it randomly creates ghost shifts in the same schedule as the ones you have.
Example :
Day shift from 7 to 21:00 and same machine same day Unscheduled shift 07 to 21:00

Afternoon shift 15 to 21:00
Afternoon shift 19 to 7am
Shift unscheduled 19 to 7 am

This causes the Hourly report to not show the information.

What was done was to enter another machine that had the right calendar and export it, or apply the pattern from a date that was correct but only from May 16, because it does not let me do it further back.

But the problem continues backwards, and it is required to clean or correct these shifts in the calendar.

  • It should noy have phantom shifts.

PNE-2928

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

For Redlion machines on saas7 (Graphic pkg), production data is coming in at the correct time, but downtime information is delayed by 5 hours. Their local time zone is Central time (UTC -5), initial investigation by Chris and Jasper concluded that there might be an extra conversion applied against the local time variable causing it to be delayed by an additional 5 hours.

  • Downtime data time should match production counts.

PNE-2903

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

After saving the csv file mapping and adding DateTime field, if there is only one field that contain Date Format, the system will automatically choose that field to display in Date / Time Field; however, the system didn’t save it into Configuration.