Versions Compared

Key

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

...

PNE-1042

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

Follow-up to https://slxdev.atlassian.net/browse/PNE-979

🖌Need to style the email template that is sent with a page as concept shows (image attached).

🚨 No major testing will be needed as functionality was all covered in PNE-979.

Tip

FIXED

PNE-1041

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

Customer is sending job data from their ERP to our system saving an XML file in the collector PC so we can populate the Job List in each of their machines automatically. This is working fine.

Now they need to feedback their ERP with job data from us. We already provided the API query to do this, but IT IS MISSING the ErpCode the customer provided to identify the machines.

We need to correct the API output to include the ErpCode please.

 

Enhancement Request

Tip

FIXED

PNE-1003

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

Icons should be re-designed + consistent with each other for the view, for the action icons as well as the tree legend machine/area icons.

Seeing as PEConfig is a different product than Whiteboard, it is normal for it to have it's own icon set that differs, just as the Advanced Portal has it's own icons that differ. If this product has the potential to be customer-facing, then we should be ready stylistically to present a cohesive platform.

Currently the icons are already considered temporary placements (CC Alex Karyakin (Unlicensed)) so I do believe bringing in the UX view into this card a big factor.

Icon Set

Tree Legend

Menu

Area

Machine

Tip

FIXED

PNE-979

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

Configure PagingEmailSender to send an email template

Whenever a page status change transaction takes place, there should be an email sent with the the page detail parameters, the template should be designed to be easily readable and understood.

For now, there will not be a link to the specific page from the email, we may add a link to the Paging List View (tbd).

Parameters for email:

  • Current status of the page.

  • Assignee (if available).

  • Message text.

  • Department page is created for.

  • Machine/Area of page.

  • Time of update (Created)

Design Iteration 1 :

Tip

FIXED

PNE-977

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

configure this PagingEmailSender to send emails upon creation of new page using the departments table in the database

i.e. when a page is created, an arbitrary email should be sent to the email address associated with that department

Tip

FIXED

PNE-965

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

Add the ability to edit existing alerts in the new config.

Have to save the alert and be able to edit the existing alerts

This case will only cover the editing of the actual values within the fields as editing the options (like type ) will affect all other options further down.

This will be in a separate issue, changing the alert type and some options that affect further selections and options.

Tip

FIXED

PNE-954

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

Description: Put line data in the cube in a reasonable structure so we can have line dashboards. (this story enables the iterating with product/Jesse to begin).

Acceptance Criteria:

  • Line data must be stored in the core data table

    • MachineId = “Line_” + LineMachineId

  • Machine, Area, and any related tables must have these “Line machine ids”

  • Machine table must have a “line filter”

  • If there are no lines in a plant, there must be no line core data (duh).

  • Build a sample dashboard showing how this all works together.

  

Technical notes:

Dim Machines:

  • MachineId = “Line”+MachineId

  • MachineName = Line.Name

  • Area = parent area (no change to default machine logic)

Dim Areas:

  • Stays in Areas, as is. Allows area level grouping of machines. (not sure if that's desired?)

Dim Machine Security:

  • Customer Account (from Area) unchanged.

  • Machine Id will be “Line” + MachineId

Tip

FIXED

PNE-904

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

Create signed installer for screen management windows client

 

Code Signing Options:

  1. Digicert: https://www.digicert.com/code-signing/

    1. PROS: Used by majority, highly recommended by most including Microsoft.

    2. CONS: Slower load times then GlobalSign (Applies to website SSL only).

    3. 3 YEAR VALIDITY COST: CodeSigning: USD $474, EV CodeSigning: USD $664.

  2. GlobalSign: https://shop.globalsign.com/en/code-signing

    1. PROS: Faster load times then Digicert (Applies to website SSL only).

    2. CONS: Not widely used, costly.

    3. 3 YEAR VALIDITY COST: CodeSigning: USD $599, EV CodeSigning: USD $950.

  3. Evaluated Trustcenter and SSL, not worth our time compared to options above.

 

After thorough research, analysis, and evaluation, by recommendation is to move forward with Digicert and purchase their EV CodeSigning package with a 3 year validity as that is the most secure and mature option.

Furthermore, I recommend we purchase the Advanced Installer Professional Edition that comes with a perpetual license at a single cost of USD $499 per user (We only need one user). This allows us to create installers for our applications and digitally sign them with our certificates. Link provided below:

https://www.advancedinstaller.com/purchase.html

Certificate

https://drive.google.com/file/d/1PcYNxT4CV3WAMtC3NiZFdRFXSAls9GO2/view?usp=sharing

Password: https://console.aws.amazon.com/secretsmanager/home?region=us-east-1#/secret?name=CodeSigningCertificate-Digicert-2022-06-06

Tip

FIXED