Release Notes: 5.0.0.14022
- Madeleine Nolan (Unlicensed)
When customers can expect this release:
Group 1: July 29, 2020
Group 2: Jul 30, 2020
Group 3: August 6, 2020
Bug Fixes:
Fix Problem with Futuristic JobsSummary Seeing cases where a job is in the future which causes Job Command checks to fail thus from the customer’s perspective breaks job functionality (e.g. can’t start/stop jobs)s Things to Fix
Possible Scenarios
FIXED | |
|---|---|
PNE-259 | Schedule Optimizer - Filter bugs#1141 Link for all bugs and steps to reproduce (use Filters sheet): https://docs.google.com/spreadsheets/d/186W93J65hZCoHIrFgOgBKZvlpV9qfGDsbo4pWjtagNQ/edit?usp=sharing |
CS-3006 | Time zone changetime zone was assigned to the machines of the company Watts (saas5) America / Santiago was assigned to all the lines are more than 40 machines, the problem is that all the data is historically out of date in terms of stops and rejections several hours of lag that is to say, if the strike was attributed at 18 hours, it now moved between 4 and 6 hours apart. Regards Sample URL |
CS-2668 | Line summary view is not showing OEE nor scrapIn Rica/ CocaCola the line summary view shows no OEE as well as the scrap count also in zero. Sample URLhttps://lasmargaritas.shoplogix.com/whiteboard/#/linesummary/area/135/layoutoption=1&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&remain=false&elapsed=false https://saas11.shoplogix.com/whiteboard/#/linesummary/area/135/layoutoption=1&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&remain=false&elapsed=false |
CS-2280 | Display problem of the whiteboard on the screen hour by hour Softys Argentina Plant (papelera de la Plata)Hello guys. They support me with this case, the client Softys Argentina notified us that on the whiteboard in Line MP1 the hourly graphics of the screen are not shown well, they can verify what happens, it is only in that Line the others are working well. Attached image and URL of the problem. Server = saas65 Thank you Sample URL |
CS-1373 | Seeing job record created when one should not be created - For AIC BirminghamPress A Line has the following job logic set up. But getting duplicate job records (two records for Job 24 with start of A / End of B and start of B / End of C and Key data from above <S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:01:45.3530214-06:00" Value="1" Rec="1003" /> NO NEW RECORD Key Data from above Note the end of above and start of below the transition record above <Job Name="24" Instance="c79971fd01fd43f2a0fce91f4139c643" Source="Actual" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" TimeStamp="02/26/2020 00:02:16.897" Created="12/04/2019 18:51:49.232"/> Job Command Query <JobCommand Command-Id="1205032d017d466ba7603dec8979244c" Command-Action="1" Command-TimeStamp="02/26/2020 00:02:16.897" Command-Username="ConnectorProcessService" Command-GenerateInstance="1" Name="24" Instance="c79971fd01fd43f2a0fce91f4139c643" CurrentJob="1" Source="Actual, Command" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" Created="12/04/2019 18:51:49.232"/> <JobCommand Command-Id="cb1a277c96da4a838833b3780fba35dd" Command-Action="1" Command-TimeStamp="02/26/2020 00:07:14.470" Command-Status="3" Command-Username="ConnectorProcessService" Command-GenerateInstance="1" Command-StatusReason="Duplicate of Command for 24 Start: 2/25/2020 12:01:45 AM End: 2/25/2020 12:48:17 AM received within 5 minutes of last command." Name="24" Instance="bccb9269b3e0209f6d07620cef6af1dcbf5c587a" Source="Actual, Command" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" Created="12/04/2019 18:51:49.232"/> Sample URLListed below in the description as several. |
New Features / Status on Long-term Work:
PROD-144 | Whiteboard Dashboard Scrap Reason ReassigningUser Story: As an operator, I want to reassign a scrap reason to automated scrap that have no reason, from the Dashboard view. Background:Coveris is requesting the ability to reassign a scrap reason to automated scrap that have no reason. This functionality exists in the hourly view but not the dashboard which is where Coveris Operators are using the system. Enhancement is add the functionality in the dashboard view. Requirements:Add navigation to scrap edit dialogue from Dashboard view to reassign automated scraps that have no reason. This feature should be the same as that in Hourly & Chrono views. The navigation to the scrap edit dialogue that must be added is highlighted below:  UI Component Requirements:REQ 1. The scrap edit dialogue should contain
REQ 2. After assigning a reason to scraps, text depicting the scrap, its corresponding reason, and the number of scraps should be visible below other scraps, next to a brown square (indicating scraps). E.g. “Ink Pumps Scrap, 5”, see below.  Functionality Requirements:Scrap Edit Flow FR 1. Users must navigate from the Dashboard view to reassign the scrap reason as follows:
Where to make this available:This component is to be made available in the following view:
Prototype / Screenshots / Examples:Link below showing how the new feature works in the Hourly view: Example of current scrap edit dialogue on dashboard: Acceptance Criteria:
|
|---|---|
PNE-1029 | New Config Alerts add validation on the alert Modal to make sure all necessary fields are filled before the modal is closedThis needs to be implemented before we can work on the alert dropdown edits that affect further selection.
Need to make sure the required fields are filled (depending on which fields become available) before being able to close modal. There should be some some user feedback to which field needs changing. Required Fields:
Window Alerts values in Escalation Level(s)
Please see the epic https://slxdev.atlassian.net/browse/PNE-812 for the individual alerts and which fields/dropdowns become available.
Testing: Try to edit an alert, leave any of the above fields blank (if that field applies to the alert) and try to close the modal.
|
PNE-970 | Adoption metric percentTargetComments > 100%The adoption metrics from servers have adoption scores of > 1, due to the percentTargetComments metric having a score >1. The example URL shows a percentTargetComments of ~891% Where to find the issueAs of 2020-04-17 Steps to recreateUse below to find all occurrences where percentTargetComplete is >100% for the day. SELECT plant_id, date_day,scheduled_time, total_time, online_machines, reporting_scrap, scheduled_machines, using_comments
FROM pne.scorecard_plant_day
where
using_comments > scheduled_machines
and scheduled_machines > 0;CalculationWe assume the formula for percentTargetComments is as follows, calculated daily: (# of machines with a comment) / (# of machines scheduled for the day) |