Bug Fixes

CS-6204	https://slxdev.atlassian.net/browse/CS-6204 In domiberia we have a machine that is stuck in a machine state and does not go into production, even though it is counting parts and recording them. Saas120 Machine: P1 Machine Id: 1AA23A77-BF9F-6090-F332-4DF6A662D046
CS-5857	https://slxdev.atlassian.net/browse/CS-5857 Since the flash plugins have been removed, what is the recommended way to get into the configuration? Can we start using the html5 interface for the configuration yet?
CS-5801	https://slxdev.atlassian.net/browse/CS-5801 https://saas126.shoplogix.com/whiteboard/#/perioddetail/4B69A435-6C03-8C22-8089-2C7B0A5914EA/start/2021-01-13T00:00:00-05:00/end/2021-01-13T01:00:00-05:00/bucket/1/timeMetric=0
CS-5575	https://slxdev.atlassian.net/browse/CS-5575 I performed a comparison between the Analytics Portal and the waterfall view to compare MTBF and MTTR. These values are not consistent, and the fact that they are not the same value is only a 1 sentence point in the documentation. I would urge that we include a MTBF and MTTR value in the Analytics Portal the the MTBF and MTTR duration values between these views. Now I need to explain to the customer that these two values are different, and require the user to input extra data despite them seeming the same. and open the possibility to more customer confusion when someone inevitably makes the same mistake again. Moving forwards I would recommend 1 of two possible changes : Add an MTTR And MTTF equation Change the current value of MTBF and MTTR to be that value after equation. I think adding the equation would be a very small change, and is one of those easy low hanging fruits. I would like to get other engineers opinions on this. ~ Hino Edit : This was unclear clarification → The current MTBF and MTTR duration values must stay in the AP. Some Customers may use those duration values for other equations.