Release Notes 5.0.0.17020
When customers can expect this update:
Group 1: March 23, 2021
Group 2: March 24, 2021
Group 3: April 1, 2021
Highlights this release:
Redesign of Layout View: Product Team is currently preparing launch plans for the redesigned layout view. Internal access, for now, will be via a link directly to the page as there will not yet be an icon available in whiteboard. Please reach out to Product for access.
Bug cleanup and continued stabilization of the Analytics Portal
Bug Fixes
CS-7167 | https://slxdev.atlassian.net/browse/CS-7167 We are experiencing issues with the PEConfig that is copying settings from one machine to the next when making multiple changes on multiple machines. It looks like whatever machine you are working on in the PEConfig the configuration is carried onto the next machine you work on so when you switch to work onto another machine parts of the other machines config are carried over. I noticed this when I was using the PEConfig to update Machine state OPC ID
Engineers are resorting to use the Flash config because the saving issues that are causing the team to redo their work repeatedly. Engineers have also reported that the following settings are also affect or reset to default as welll:
Steps to reproduce the issue:
|
CS-7164 | https://slxdev.atlassian.net/browse/CS-7164 Saas135 is down, https://softys.shoplogix.com/whiteboard/#/ |
CS-7139 | https://slxdev.atlassian.net/browse/CS-7139 Yesterday at 10:14 am start problems with the whiteboard on this client, in some machines we have a big delay and the others machines does not shows all data, data are in real-time on the saas, but the both connectors shows issues from yesterday at 10:14am a going with the same problem today. For example in the machine 6292DFF4-4B8F-E243-4CAF-62E929C8682B we should see an order that started at 1:38 am, but it is not being shown in the Whiteboard but it is seen in the OPCcombined. Thanks and regards. Sample URLhttps://saas139.shoplogix.com https://lamitech.shoplogix.com/whiteboard/#/perioddetail/0938A90B-DC72-74B3-FBA5-5F529ED3DD0D/start/20210310T070000.000/end/20210310T190100.000/bucket/60/timeMetric=0 https://lamitech.shoplogix.com/web/xmldata/cn_lamitechcol1/logs/2b35d602-4115-466a-84f5-b362d232a23b/2021-03-09%20RealtimeSync.txt?contentType=text/plain https://lamitech.shoplogix.com/web/xmldata/cn_lamitechcol2/logs/70a4cf74-6f32-466a-b9f2-56a475bbe6cb/2021-03-09%20RealtimeSync.txt?contentType=text/plain https://lamitech.shoplogix.com/whiteboard/#/perioddetail/6292DFF4-4B8F-E243-4CAF-62E929C8682B/start/2021-03-10T00:00:00-05:00/end/2021-03-10T19:01:00-05:00/bucket/60/timeMetric=0 https://lamitech.shoplogix.com/Web/query.axd?type=OpcCombined&start=20210310&machines=6292DFF4-4B8F-E243-4CAF-62E929C8682B |
CS-7111 | https://slxdev.atlassian.net/browse/CS-7111 We urgently need you to verify this case, the BPET09 line of the saas65 client cannot view the data in the system, this client is integrated with SAP and has not been able to download the shift information, checking the server they have all the production data. Thank you Sample URLLinea BPET09 https://koandina.shoplogix.com/whiteboard/#/shifthours/00d0c9ea5b28/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1 Linea BPET09 https://saas65.shoplogix.com/whiteboard/#/shifthours/00d0c9ea5b28/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1 |
CS-7028 | https://slxdev.atlassian.net/browse/CS-7028 Case is to log time against updating MDLZ Cube and verifying changes against their existing Analytics Dashboards. Sample URLhttps://portal.shoplogix.com/app/main#/dashboards/604286e521e9ef002fc21e77 |
CS-6352 | https://slxdev.atlassian.net/browse/CS-6352 All 3 germans sites in coveris are looking to send jobs to an area and not to a machine. Like it is done in Campine (also on saas141). Coveris, Neuwied is the test site and the following details have been added to the configuration.xml for the plant:
This allows jobs to be sent to an area ID through their xml job files. Rather than using MachineID as an attribute AreaID is used. For example: Attached is the job file that customer sent as a test and shoplogix failed to accept the jobs. Sample URL |
New Features / Status on Long-term Work
PROD-247 | https://slxdev.atlassian.net/browse/PROD-247 Please check the attached for the latest mockup demo for Phase 1. Efficiency = OEE
Design Doc: https://slxdev.atlassian.net/wiki/spaces/SD/pages/1231618068 |
PNE-1650 | https://slxdev.atlassian.net/browse/PNE-1650 The dropdown component needs a facelift! I have attached an initial concept for the redesign :
🚀
I have a few follow-up questions regarding colour schemes and how they are set and by whom, as well as font colour and when it is toggled dark/light. |