CS-4440

https://slxdev.atlassian.net/browse/CS-4440

Customer is configured to have all production during setup to be recorded as scrap and it is not always working as expected. In the attached examples the setup reasons are entered manually by the user but the production is not recorded as scrap. The issue seems to be related to the manual edits of setup reason instead of automated setup which occurs on a job change.

CS-4312

https://slxdev.atlassian.net/browse/CS-4312

CS-4231

https://slxdev.atlassian.net/browse/CS-4231

I just noticed that all our shoplogix screens are blank. Can’t say exactly when this happened but sometime this week.

Click case for link

CS-4181

https://slxdev.atlassian.net/browse/CS-4181

I have been doing some testings on OAuth using the Screen Managament Client and does not seems to be working,

I have used the same version of client with a server with Basic credentials and it is working, however when I tried on the OAuth server says Access unauthorized

I have used my own shoplogix user, the Slx.Client redirects me to the default browser, the validations process goes through okay, but when it gets back to the Slx.Client it says Unauthorized access (image attached)

I have downloaded the Screen Client from this link

I have also tried the previous version of the Slx.Client without being able to successfully configure it

As for tests I have tried:

1. Using

saas5 or the server name “paill” for this customer both gave same results,

1. Setting Chrome and Edge as default explorer giving the same result.

CS-4156

https://slxdev.atlassian.net/browse/CS-4156

When searching any of the english downtimes the downtimes show up

However, whenever searching any of the french words it isn't showing up

CS-3798

https://slxdev.atlassian.net/browse/CS-3798

Note a 4:50 downtime that is in the Maint. Code group. This is part of a timeframe where a Setup Machine state is on. It should not being associated with that Grouping as it does not show that way in the Flash Reports or WB.

CS-3765

https://slxdev.atlassian.net/browse/CS-3765

Note: 1 hour delta as site is EDT and collector is CDT. So the system is treating the records where not count is associated with the record as a 0. There is no change between the valid counts read.

The NULL record should be ignored and not treated as a 0. If this should be a different case, please let me know. In this case, RampIgnoreZero = 0. Note that Total = 38,400

CS-3622

https://slxdev.atlassian.net/browse/CS-3622

Whiteboard dashboard chronological timeline does not have a consistent time format, combines 24hour and 12hour. This should be consistent with other views such as the Chronological that has 12 hour

CS-3233

https://slxdev.atlassian.net/browse/CS-3233

Flush is set up as a Downtime Edit / Machine Reason on Portales HTST 5 unit. This is true when the tags value is equal to 4. It goes to 5 when in CIP. If you look at the fav below, you can see when the tag transitions from 4 to 5 as the mode switches from Idle to CIP. However, the machine holds Flush through the CIP and the Idle when it should turn off due to being Downtime Edit. Same tag so mutually exclusive.

CS-660

https://slxdev.atlassian.net/browse/CS-660

[Site]:LKB and Baddi QA

[Issue]: "Changeover" reason getting auto assign to the fault codes(Downtime reasons). This issue was fixed earlier but seems like issue is resurfaced
You can refer case ID HQ-1557066961 for your reference

We tested this on Baddi QA server