Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This set of release notes covers both Release 5.0.0.17417

When customers can expect in this update:

Group 1: May 4, 2021

Group 2: May 5, 2021

Group 3: May 13, 2021

Highlights from Release 5.0.0.17417:

  • The Opportunity Pareto view has had multiple enhancements and should now perform better.

  • Certain customers were having issues with accented characters in file-names or paths. These issues have now been resolved

  • When new “Events” data was previously added to the Analytics Model, it caused some filters and joins to not work correctly. This is now been resolved.

Bug Fixes:

PNE-1851

https://slxdev.atlassian.net/browse/PNE-1851

Customer had a custom XML data on connector PC that was being uploaded.

Directory also contained other files, some of those directories had accented characters in the name.

Translation to upload archive causes accented characters to be replaced with ?.

? is not a valid character for paths. Upload failed, and subsequent data update failed.

This is been fixed, and proper logic to handle accented characters has been added.

PNE-1846

https://slxdev.atlassian.net/browse/PNE-1846

Adding new “Events” data to analytics model caused some filters and joins to not work correctly. This has been fixed so existing dashboards continue to work.

PNE-1844

https://slxdev.atlassian.net/browse/PNE-1844

CurrentState signals caused “Splice” signal to resolve to an incorrect time, resulting in an incorrect exit time for final setup state.

PNE-1842

https://slxdev.atlassian.net/browse/PNE-1842

Long text on tool-tips was causing it to overflow screen boundaries.

PNE-1816

https://slxdev.atlassian.net/browse/PNE-1816

After deleting all of the shifts in a month, if the month was empty, the calendar would prevent you from saving with an empty shift schedule.

PNE-873

https://slxdev.atlassian.net/browse/PNE-873

Combination of two issues:

  • Issue 1: If Enable Overcycling Tolerance = NO, the value was not displayed when changing Cycle Gauge. This was a visual bug.

  • Issue 2: If Enable Overcycling Tolerance = YES, the setting was not respected when changing Cycle Gauge. This was not a visual bug.

New Features / Status on Long-term Work:

PNE-1698

https://slxdev.atlassian.net/browse/PNE-1698

This update contains multiple feature enhancements to the Opportunity Pareto view in Whiteboard. They are listed below:

Opportunity Pareto - Default setting shouldn't change Levels
https://slxdev.atlassian.net/browse/PNE-1674
Selecting 'Default' in Settings should change all Setting options apart from Start and End date to default, however Levels (filters) should stay the same.
Currently, Level 1= Reason, while Level 2 and Level 3 are unselected if Default user clicks on Default.

Opportunity Pareto expanding other duplicating row
https://slxdev.atlassian.net/browse/PNE-1629
https://qatesting.shoplogix.com/whiteboard/#/opportunitypareto/machine/605C58C2-4AB5-0B20-EE34-99367F37C058/start/20210204T150000.000/end/20210205T150000.000/level1/shift/level2/reason/level3/job/maxsub=1

Expand Other (4) for day shift Reason, then expand Other (1) for job, In the afternoon shift section, there is another job added with different values

There is an issue with the expansion of others, it seems that because two rows have the same value in the second column they are both expanded when one is clicked and in some cases is also creating a value that should be in a different sub section to be in that one.

The similar names also seems to be causing two other subsections to expand at the same time

Opportunity Pareto exceeding time limit set over 3 months
https://slxdev.atlassian.net/browse/PNE-1230
When the time span restriction value in web.config is set to a value of
<add key="TimespanRestrictionSeconds" value="10370000" /> (120 days) the pareto response does not return the variable.
It seems to only apply to time restrictions over the default of 90 days.

May also need to ensure the machines restriction is not doing the same.

  • No labels