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 Total

Steps to reproduce:

  1. In Shift Hours add several Scrap reasons with Comments

Expected Behavior: All Scrap reasons with Comments are displayed in Total section
Actual Behavior: All Scrap reasons are displayed in Total section, however some Comments are missing.

Ex: https://qatesting.shoplogix.com/whiteboard/#/shifthours/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/20200403T123825.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

FIXED

CS-3318

time is 12:41 but Shoplogix still at 12:13

time is 12:41 but Shoplogix still at 12:13
big delay in the time

Sample URL

saas32.shoplogix.com

FIXED

CS-3229

Quality Data Export Timestamp incorrect

Machine is set up for Ad hoc queries.

https://mauser.shoplogix.com/whiteboard/#/shifthours/00d0c9e8d644/quality=true&units=1&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%2Fquality%3Dtrue%2Fquality%3Dtrue

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: ?

https://mauser.shoplogix.com/whiteboard/v3/#/qualityaudit/machine/00d0c9e8d644/start/20200723/end/20200725T000000.000

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
HW #6 BM 202.U4,00d0c9e8d644,055C400UL1,7222b02db6b1453ab7775c31e6b31821,Drum Weight,2020-07-24 14:07:45,,20.93,false,Brock,Measurement,AdHoc,Complete,20.8,true,false,3:00 PM Sample,
HW #6 BM 202.U4,00d0c9e8d644,055C400UL1,3e73fe9f0739471780b020036436894d,Drum Weight,2020-07-24 16:07:02,,20.72,false,Brock,Measurement,AdHoc,Complete,20.8,true,false,1:00 PM Sample,
HW #6 BM 202.U4,00d0c9e8d644,055C400UL1,3e73fe9f0739471780b020036436894d,Drum Weight,2020-07-24 16:07:19,,20.23,false,Brock,Measurement,AdHoc,Complete,20.8,true,false,2:58 PDT,

CS-2677

Bug - Altering Timescale and Bucket isn’t behaving predictably

Description

 

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 URL

kamtek-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.
Please find the attached file for an example from Rockford Plant.

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 error

an API query throws an error when has a jobFilter in the URL:

this 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

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 URL

this 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 time

HQ-1585825671
the UCL and LCL lines only show for very breif time intervals instead of stretch across entire chart

Reporter: Ian McGregor

New Features / Status on Long-term Work:

PROD-179

We need some confirmation/feedback schedule was saved correctly.

HQ-1577663658
When you press the button to save your schedule, there is no confirmation schedule was saved. It looks as if nothing happened. We need some confirmation/feedback schedule was saved correctly.

PROD-146

PLC driven Jobs default to 0 Cycle Factor for jobs not in list

Problem 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 0 CF function is turned on for Rework jobs
It uses all of the default machine values except the CF

The default cycle factor should be set to 1 to the machine configured cycle factor.

Solution

Need to change the way Cycle Factor is handled for jobs when AllowZeroCycleFactor is set. If Cycle Factor is supplied then that value is used (even if the value is 0), if Cycle Factor is not supplied then a non 0 default value chosen.

This will affect:

  • Jobs starting from machine inputs (jobs started in ConnectorProcessService)

  • Jobs being uploaded to either the schedule or default list

  • Jobs Started/Edited through Whiteboard

Example

Job 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 Machines

On the plant level for PEConfig, add the “Report Config” tab which will contain the following :

  • 5 Input Groups representing 5 different filters

    • Textfield for the filter label

    • Textfield for the filter values separated by a comma (will be used later on to populate dropdown list)

    • Dropdown menu to select the value type (NUMBER or STRING)

This card will only focus on implementing the information on the front end, a list of things to do :

  • ReportConfig.ts model for what will be sent to the backend

  • main.tsx with new function calls

  • treeActions.ts with reportConfig func, creation of put/get + done functions

  • treeReducer.ts with action commands

  • mainState.ts with function call

  • actionTypes.ts with new actions for PUT/GET/DONE commands

  • configMainContainer.tsx to pass put/get functions to the view.

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 table

Each 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:
Escalation level 1 will have 3 shifts configured and will have 3 different email addresses per shift, so when alert is triggered in different shifts it will send email to appropriate manager / operator.

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