Release Notes 5.0.0.14349
- Madeleine Nolan (Unlicensed)
- Steven Arrol (Unlicensed)
When customers can expect this release:
Group 1: August 26, 2020
Group 2: August 27, 2020
Group 3: September 3, 2020
Highlights this release:
Our Quality/SPC Module now accepts and plots manually entered SPC inspections. This means if you mark a quality inspection in the Quality configuration screen as SPC, it will populate the user-defined results into the Analysis screen
Paging Beta is ready. If any customer already has Messaging Module and is interested to learn more about these new capabilities, please let @Steven Arrol (Unlicensed) know.
Bug Fixes:
New Features / Status on Long-term Work:
PROD-202 | https://slxdev.atlassian.net/browse/PROD-202 Remove Walkme user access popup. Acceptance Criteria:
|
PROD-180 | https://slxdev.atlassian.net/browse/PROD-180 When SLX began work on the Quality & SPC Module, we did not add a requirement for SPC-Based Quality Checks to be displayed in the SPC Analysis view of the Whiteboard. This request is for all Quality checks configured in the /quality/, which hace the SPC flag enabled, to be displayed in the analysis view. Reference examples from saas102: https://saas102.shoplogix.com/whiteboard/v3/#/qualityanalysis/machine/XMLCN_Tecnova1/start/20200701T000000.000/end/20200727 ACCEPTANCE and TESTING: (EDIT by Scaletti)
|
PROD-172 | https://slxdev.atlassian.net/browse/PROD-172 Coveris operators use dashboard view and would like to lock the whiteboard to that view so operators cannot access other machines. lockView=2 allows chrono and hourly view and would need to add dashboard to allow all three menu options. Enhancement request is to add another lockview option 4 as shown bellow that has Dashboard as a menu option. Current:
Proposal:
Long term strategy:
|
PNE-932 | https://slxdev.atlassian.net/browse/PNE-932 Summary Currently the front-end, Opportunity Pareto, limits the time for the Details
TimespanRestrictionSeconds MachinesRestricted
Sample Response with Limits{
"type": "Reason",
"machinesRestricted": 50,
"timespanRestrictionSeconds": 7905600,
"data": [
{
"name": "Unscheduled",
"duration": 2927690478.7287,
"occurrences": 46,
"percentage": 0.9600000074375954
},
{
"name": "Production Complete",
"duration": 121987079.653,
"percentage": 0.03999999256240452
}
],
"start": "20200525T000000.000",
"end": "20200526T000000.000"
}Sample Response when no Limits are Applied:{
"type": "Reason",
"data": [
{
"name": "Unscheduled",
"duration": 2927690478.7287,
"occurrences": 46,
"percentage": 0.9600000074375954
},
{
"name": "Production Complete",
"duration": 121987079.653,
"percentage": 0.03999999256240452
}
],
"start": "20200525T000000.000",
"end": "20200526T000000.000"
} |
PNE-860 | https://slxdev.atlassian.net/browse/PNE-860 Currently in the config new variables are added and then edited.
Also need to check to see if another variable with same name already exists and is active. If it is, the user will get a validation message “Variable name in use” and will have to pick a different name.
Notes:
|