Release Notes 5.0.0.14177
When customers can expect this release:
Group 1: August 11, 2020
Group 2: August 12, 2020
Group 3: August 20, 2020
Bug Fixes:
PNE-802 | Scrap reason Comment is not showing in Shift Hours TotalSteps to reproduce:
Expected Behavior: All Scrap reasons with Comments are displayed in Total section FIXED |
CS-3318 | time is 12:41 but Shoplogix still at 12:13time is 12:41 but Shoplogix still at 12:13 Sample URLFIXED |
CS-3229 | Quality Data Export Timestamp incorrectMachine is set up for Ad hoc queries. Look at the timestamps of the check using the Audit screen. No match to those shown in the Audit report and they all have minute of :07: ? Timestamps in the export do not match timestamps seen in the Audit report machineName,machineId,jobName,jobInstance,name,timestamp,hyperLink,value,checkPass,userName,type,stage,state,target,spc,critical,comment |
CS-2677 | Bug - Altering Timescale and Bucket isn’t behaving predictablyDescription
This is a very odd bug, but it is very frustrating when it occurs. In certain combinations such as the one demonstrated in this video, the time adjustments "do not work" For the purposes of this ticket and narrowing scope I would like to focus on the chrono view as that is the primary view that Timothy uses, but any modifications made will need to be replicated to all views eventually. ~ Hino Sample URLkamtek-cosma-magna.shoplogix.com/whiteboard/#/perioddetail/C4061324-E1CE-4B2A-B8B3-E4FF1E9A3723/start/2020-06-17T04:50:00-05:00/bucket/60/timeMetric=0 or saas16.shoplogix.com/whiteboard/#/perioddetail/C4061324-E1CE-4B2A-B8B3-E4FF1E9A3723/start/2020-06-17T04:50:00-05:00/bucket/60/timeMetric=0 |
CS-2556 | [Mondelez]:JSON changeover logic[Issue]: Unable to identify the changeover on Line GE view if 2 SKUs with the same material number (different line parameters) are running on the Bottleneck machine. |
CS-2311 | Nirsa (SAAS 120) Values of reasons do not match. Hi. Please, could you check outputs in data of API? values of reasons grouped by plant, area and machine does not match, attached images Thanks and regards. Sample URL saas120.shoplogix.com https://nirsa.shoplogix.com/web/api/export/summary?Start=20200501T070000&End=20200520T070000&metrics=reasons,&groupBy=machine,&machines=XMLCN_nirsa1&format=xml |
CS-2206 | API query filtering jobs throws an erroran API query throws an error when has a jobFilter in the URL: this is an example(throws error): this example don't: the difference between this URLs is " jobFilter=Filter1,20017305&jobFilterType=Exclusive " I read all the API documentation and it looks like everything's okay Sample URLthis is an example(throws error): https://saas120.shoplogix.com/web/api/export/summary?Start=20200422T060000&End=20200423T060000&metrics=uptimeHours,downtimeHours,setupHours,total,scrap,&groupBy=machine,jobInstance,&areas=8&jobFilter=Filter1,20017305&jobFilterType=Exclusive&classificationFilter=capacity&classificationFilterType=Exclusive&reasonNameFilter=Unscheduled, Planned Downtime&reasonNameFilterType=Exclusive&format=xml this example don't: https://saas120.shoplogix.com/web/api/export/summary?Start=20200422T060000&End=20200423T060000&metrics=uptimeHours,downtimeHours,setupHours,total,scrap,&groupBy=machine,jobInstance,&areas=8&classificationFilter=capacity&classificationFilterType=Exclusive&reasonNameFilter=Unscheduled, Planned Downtime&reasonNameFilterType=Exclusive&format=xml |
CS-1345 | SPC chart only shows upper and lower limits for a small segment of timeHQ-1585825671 Reporter: Ian McGregor |
New Features / Status on Long-term Work:
PROD-179 | We need some confirmation/feedback schedule was saved correctly.HQ-1577663658 |
PROD-146 | PLC driven Jobs default to 0 Cycle Factor for jobs not in listProblem Details On a machine that uses a tag for a job change, when there is no corresponding job for the tag, the cycle factor defaults to 0 The default cycle factor should be set to 1 to the machine configured cycle factor. SolutionNeed to change the way Cycle Factor is handled for jobs when This will affect:
ExampleJob started from PLC inputs, no Cycle Factor is supplied and there is no information from Default Job list, Cycle factor should be set to Machine’s Cycle Factor. |
PNE-1124 | Create Plant-Level Custom Filtering For MachinesOn the plant level for PEConfig, add the “Report Config” tab which will contain the following :
This card will only focus on implementing the information on the front end, a list of things to do :
– Model Structure Template [ {label: “Filter 1 Label”, values: “v1, v2, v3”, type: “string”}, {label: “Filter 2 Label”, values: “1, 2, 3”, type: “number”}, {label: “Filter 3 Label”, values: “v1, v2, v3”, type: “string”}, {label: “Filter 4 Label”, values: “1, 2, 3”, type: “number”}, {label: “Filter 5 Label”, values: “v1, v2, v3”, type: “string”}, ] |
PNE-1025 | Alert Config - add subrows in escalation level table to support multiple shift / email pairs in the tableEach escalation level might have multiple shifts configured with different emails per shift. Need to add sub rows for each escalation level to be able to configure that and also need to add the ability to add new sub rows per escalation level. Example: Example datatable: https://www.gyrocode.com/articles/jquery-datatables-how-to-expand-collapse-all-child-rows/ API needs to be modified to handle multiple email - shift pair per escalation level. Would also need a way to add new subrows to escalation levels and using the validation for alerts to ensure user fills in all the required fields prior to saving the alert |