Versions Compared

Old Version 1

changes.mady.by.user Jeff Dryden (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Jeff Dryden (Unlicensed)

Saved on

Key

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

This set of release notes officially covers Release 5.0.0.17657. With the additional hotfix the specific Version Number for this release is 5.0.1411.17714.

When customers can expect in this update:

...

Group 2: June 2, 2021

Group 3: June 10, 2021

Info

Highlights this release:

  • Certain customers were having issues matching Shift Data information between Whiteboard and the Export API. This has been fixed.

  • Paging Data tables have been created, currently with limited access.

  • A special hotfix increasing the maximum length of Reason Name widths to 44 characters has been included in this release.

Table of Contents
minLevel1
maxLevel2

Bug Fixes

PNE-1893

https://slxdev.atlassian.net/browse/PNE-1893?filter=10130&jql=fixVersion%20%3D%205.0.0.17657%20AND%20issuetype%20not%20in%20(Admin%2C%20Dev-Sub-Task%2C%20Bug-Sub-Task)%20AND%20component%20not%20in%20(DevOps-JSFrameworkUpdates%2C%20DevOps-Tools%2C%20DevOps%2C%20Cex%2C%20DevOps-CoreDatabase%2C%20Identity%2C%20Config-New)%20AND%20(%22Epic%20Link%22%20is%20EMPTY%20OR%20issueType%20%3D%20Epic)%20AND%20(project%20%3D%20PNE%20OR%20issueType%20%3D%20Epic)

An issue where certain shift data information could not be looked up was discovered. While fixing this error, an additional error with issues matching Shift Data information between Whiteboard and the Export API was found. Both of these issues have been fixed.

PNE-1905

Included as a special Hotfix

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

Certain Reason names could not be displayed in their entirety due to their length. Changes have been made to make sure Reason names up to 44 characters are supported.

...

PNE-1877

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

Create Paging tables with the following data points from whatever we have in PNE databases.
Use the federator postgres connection.

Dim Page

Page Id (NOT hidden)

Title (first “text” node)
Machine_id (hidden, joins to Dim Machines)
IsResolved
IsCancelled

Created By

Department

Fact Page Status

Page Id (hidden)

Status (open,WIP,Resolved,Cancelled)

Start DateTime
End DateTime
Duration (resolved or cancelled durations (last status) is always 0. “terminal step”.)
User (accepted_by)

Joins:

  • Dim Page joins to Dim Machine, single linear path.

  • Dim Page cannot join to shifts without sisense help → join paths will get very confused and we cant use the “buster” technique because shortest path is not respected (bug?).