Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

When customers can expect this release:

Group 1: October 6, 2020

Group 2: October 7, 2020

Group 3: October 15, 2020


Highlights this release:

  • A functionality to configure job filter labels for any Area that is a line has been created on the New Configuration Interface (PNE-1018)

  • Still active development ongoing for the Analytics Portal.

...

if (IsAuthenticated(context)) { var rules = _accessManager.CurrentRules; if (!_configManager.CurrentConfig.Machines.Any(m => rules.CanRead(_roles, context.User.Identity.Name, m))) { _log?.Trace($"401: CustomAuthentication: {context.User} can not read any machines: {context.Request.Url} {context.Request.UserHostAddress} {context.Request.UserAgent}"); context.Response.StatusCode = 401; context.ApplicationInstance.CompleteRequest(); return; } }

Code needs to be adjusted

countDelta = Current Count - Last Count minuteDelta = (Current Timestamp - Last Timestamp).TotalMinutes effective rate = countDelta / minuteDelta IF effective rate > (machine expected production rate * 10.0) THEN IGNORE END IF

Where 10 = hard-coded RateLimitFactor

For some scenarios (See https://slxdev.atlassian.net/browse/CS-3016 ) it would be helpful to be able to configure said threshold.

Added Error signal for when rate limiter triggered.

PNE-1246

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

The <MicroStopStatus> and <RunningSlowStatus> tags are not written for default status names and as a result not being used when enabled.
Have to always write default value into XML to avoid this issue

In LegendDeviceSettings.cs need to set defaults for read so it will match to the write values

PNE-1202

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

Currently `CustomAuthentication.cs` checks if a user can read any configured machine. Want to change this check to if a user can read any licensed machine.

eg. this code needs to be adjusted

Code Block

PNE-1197

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

Currently when there is a ramp/counter value for total/scrap/good we do a sanity check of

Code Block

...

PNE-1018

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

Summary

For Schedule Optimizer and (Flash) Quality Config job filter labels are configured at the Line level and needs to be available in the New Configuration Interface for any Area that is a Line (has a line machine configured)

Details

  • Need to implement settings interface that match Schedule Optimizer - Job Filters

  • Need to investigate possibly removing Machine level Job Filter labels since their current usage is unknown (The filter on machine level are used in Flash reports for re-labeling generic filters on some reports)

  • Need to implement changes to api call for area level that will return filters

  • Need to add Checkbox for enabling <ScheduleOptimizerEnabled>1</ScheduleOptimizerEnabled> tag on Plant level