PNE-1286

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

Summary

There are problems with the screen client surrounding missing dependencies after it has been installed when attempting to run the exe.

PNE-1319

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

Machine Types: OPC, XML and Plantnode Cloud

• When brand new machine is created Uptime machine state is named Slow Running by default.

Expected behavior: Uptime state is named Running by default.

Machine Types: PN 360 and New 360

• When brand new machine is created Uptime machine state named Running is missing. Only Oscillating is created.

Expected behavior: Uptime state named Running is created by default.

Note: Not sure when issue is introduced, but it reproducible on version: 5.0.0.14757

PNE-1258

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

1. Downtime (idle) state

• All changes made to chackboxes get reverted upon Refresh

• Production Override dropdown is missing while it is there in Flash config.

2. Micro Stoppage

• Cannot turn off checkboxes

3. Adding opcID to machine state puts it to a wrong state

PNE-1241

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

In the New Config attempted the following:

• Attempted to change the (Opc) Id and Machine Reason setting for a scrap variable

• Made the changes, saved, and the changes were lost

• Ended up using Flash Config to get the changes made

PNE-947

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

Prerequisite:

• Have running job with Blocked Cavities > 0

Expected cycle time shouldn't be affected by blocked cavities.

CS-4299

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

Description

Problem Found
The problem is related to the export functionality and shifts that overlap midnight.

Steps to Re-produce

Clear shift from 2-Oct-2020

Copy Day from 8-Oct-2020

Paste Day to 2-Oct-2020

Save Changes

Click Export (start time will be automatically set to today’s date 2-Oct-2020 at the time of testing)

Refresh the shift calendar (you won’t see the problem otherwise)

Results
Shift 3 starting from 1-Oct-2020 22:00 to 2-Oct-2020 06:00 has been deleted.

Fix Needed
This shift calendar should only be exporting/shifts that start on the day that’s specified in the Export From date/time:

and not shifts that intersect with that time.

CS-4252

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

I've been having problems loading flash reports, creating favourites etc on saas136.shoplogix.com. I don't know if OAuth is part of the problem, but seems to be worse after OAuth.

First time logging in in the morning, usually there's no problem. After awhile, I get an error that says "server problem, working offline" (see screen shot below). Then navigation tree doesn't load anymore. I've cleared caches and can't fix it. I tried MS Edge instead and it works for awhile, then the same thing happens.

CS-4230

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

Open Jira Ticket to see image, link, and code

CS-3917

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

Please assist customer Lithotech they are unable to start a job on Grapha 4.

CS-3492

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

SlxClientInstaller does not open because it is asking for admin password
our policy we are not allowed to give admin right to anyone
all our programs mast work with stander user

PNE-1309

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

This may be a duplicate, but the PEConfig currently sets any machine to a cycle factor of zero

This is preventing Eng utilization and rollout.

PNE-1237

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

Model and layout for area settings has been completed.
Need to move it out of config main and into its own file.
Connect up the save functionality with the new area settings api endpoints to allow saving and editing of the values.

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

• Need to add Line machine field to be configurable and visible.

• Make sure all the fields currently on area level are covered

PROD-212

https://slxdev.atlassian.net/browse/PROD-212

Summary

Enhancement request to add Pull jobs flag in the export API. In addition to the pulled job flag all job flag type fields should be exported.

Details

The following JobRecord fields should be added to exported job data where applicable from api/export (whenever job information is included in the export query results)

• blockedCycleFactor

• bom

• description

• operation

• lineCycleFactor

• electricityExpected

• finishedGoodsCycleFactor

• gasExpected

• inventoryCycleFactor

• jobMaxRunRate

• operationOffset

• runtimeExpected

• scrapCycleFactor

• waterExpected

• blocked

• confirmed

• pulled

Acceptance Criteria

• All of the JobRecord fields mentioned above should be added to the exported job data

PROD-199

https://slxdev.atlassian.net/browse/PROD-199

Final Requirements For Linking Report Config

• On the machine level:

  • Make sure machine GETs the list of custom filters that were set on its plant level.

  • For each custom filter:

    • Render an input field based on type of filter (dropdown)

  • User can select from the list of custom filter values that suits their machine.

  • On clicking save, form saves the custom filters that were set for the machine.

    • User does not need to select every filter.

    • User does not need to save any filter(s) or all filters.

• When reloading / loading machine level report config tab:

  • GET the custom filters + the selected filter that was set on the machine level to load relevant input fields.