PNE-1672

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

User cannot manually set or upload a job with Cycle Factor and/or Scrap Cycle Factor = 0

Expected behavior:
User can set manually or upload a job with Cycle Factor and Scrap Cycle Factor = '0' regardless of <AllowZeroCycleFactor></AllowZeroCycleFactor> setting.
Then if <AllowZeroCycleFactor>1</AllowZeroCycleFactor> the job should start with CF=0.
On the other hand if <AllowZeroCycleFactor>0</AllowZeroCycleFactor> the job should start with cycle factor/scrap cycle factor = 1.

Was originally implemented on https://slxdev.atlassian.net/browse/CS-2094 and https://slxdev.atlassian.net/browse/PNE-1165

It was working fine on version 5.0.0.16494, most likely broken on https://slxdev.atlassian.net/browse/PNE-995

PNE-995

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

Steps to reproduce:

1. Go to Job List

2. Select any existing non-running job or click on New

3. Click on 'X' in Cycle Factor field --> default machine Cycle Factor is displayed (if default machine Cycle Factor = 0, value '1' is displayed)

4. Save

5. Click on the Saved job from the previous step

Expected behavior: Cycle Factor = default machine Cycle Factor (or '1' if default machine Cycle Factor=0)
Actual behavior: Cycle Factor = 0

Edit: Same behavior is reproducible for Scrap Cycle Factor

CS-6565

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

I have been trying a lot to have TV screens to stay logged in,

1. I have test different users (made no difference)

2. I place a plug in in Chrome to refresh the page every 120 seconds (made no difference)

3. Place the remember me on the logging and save credentials on Chrome (made no difference)

4. Clear cache and cookies and log in back again (no difference)

TV screens do not last more than 2 hours logged in, and some screens have a couple tabs rotating and sometimes is only one of them failing

Can you please check if recent update is the root cause, it started yesterday on this account

If so please revert it o something as customer is receiving reports of Screens failing several times at day, and it is taking a lot of time going to remote connection and testing

Thanks

Sample URL

https://saas124.shoplogix.com/whiteboard

CS-6201

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

When a machine is in a setup state you are able to start a capacity reason by clicking on the flashing state. once the machine is on the capacity reason however you cannot end the reason and go back to setup.

Enhancement/bug fix is to allow customer to start and end a setup capacity reason during setup states. This is required especially if the customer has a job that stays in setup over the weekend.

Change In Behavior

When applying the “Blank” reason to clear a reason:

Previous behavior

• machine status for time edited is changed to the default Downtime state

Current behavior

• machine status for the time edited is not changed.

Sample URL

https://saas141.shoplogix.com/whiteboard/#/perioddetail/C6A6AA04-200E-28D7-F890-B2BF1F6CAB16/start/2021-01-28T14:00:00-05:00/end/2021-01-28T16:00:00-05:00/bucket/1/timeMetric=0

Open

Open

PNE-1700

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

Need to implement changes as per request for api/export which includes configuration changes to capture downtime categories that are specified in this request.

Project complete.

Build: 5.0.0.16808

Design document (Project details found here):

https://slxdev.atlassian.net/wiki/spaces/SD/pages/1305411637