When customers can expect this release:

Group 1: November 17, 2020

Group 2: November 18, 2020

Group 3: November 26, 2020

Highlights this release:

A new feature that allows only ADMIN users to schedule emails reports based on Elasticube Update Schedules has been added to the Analytics Portal (PROD-293)
The new Machine Filter columns have been added into the Analytics Portal (PROD-210)
Mainly consisting of bug fixes while active development and rollout continues for Analytics Portal

Bug Fixes:

PNE-1296	https://slxdev.atlassian.net/browse/PNE-1296 Something new, whether our system or Chrome has now messed up the redirect flow in both Basic and OAuth. I have come to the conclusion that Identity redirects the correct token back successfully not only in the Android app, but also the Desktop app. Problem seems to happen when the client apps attempts to redirect back to /screenclient
PNE-822	https://slxdev.atlassian.net/browse/PNE-822 Steps to reproduce: In Peconfig select any OPC machine > Part Counts > Edit > Add Variable > Set Ignore 0 = No > Save In Flash Config make any change (or no change) > Save Navigate back to Peconfig > Select the same OPC machine from step 1 > Part Counts Expected Result: Ignore 0 from step 1 is still set to 'No' Actual Result: Ignore 0 from step 1 is still set to 'Yes' Note: In case https://slxdev.atlassian.net/browse/CS-1148 RampIgnoreZero is set to true by default, however if it set to false it shouldn't be overridden to true.
CS-4620	https://slxdev.atlassian.net/browse/CS-4620 Customer reported that only some custom areas are working in Whiteboard Confirmed that only Production Area 1 is functioning correctly The remainder of custom areas, while they are present, cannot be selected They work correctly in PNE reports
CS-4278	https://slxdev.atlassian.net/browse/CS-4278 When the language is switched to French in the Analytics Portal the text in the Field and Design Window does not translate.
CS-4150	https://slxdev.atlassian.net/browse/CS-4150 I would like a detailed explanation and plan as to why shop logic is not reporting running loss as it previously did and when it will be fixed. I have asked on several occasions and frankly the response as to why has not been adequate nor has the response to correct the issue or issues.

New Features / Status on Long-term Work:

PROD-293

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

Background

Had meeting with Manny, Tarannum, and Tyler to identify additional items that our customers should not be exposed to. It appears a customer can schedule reports on an Elasticube update trigger. This will make no sense to our users and may introduce unexpected issues in the future.

Requirements

REQ 1. Remove the currently existing ability for all end-users (except ADMIN) to schedule email reports based on Elasticube Update Schedules.

Acceptance Criteria

End-users should not have the ability to see the above radio button option when using the Republish/Share feature on a dashboard. This includes OWNERS of the dashboard as well.
The only end-user with this ability should be an ADMIN account (and even this is not particularly needed, but we should keep it just in case in the future we require some sort of trouble-shooting)

PROD-210

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

Problem:

new feature is implemented but not pushing into cubes.
Joe already implemented new fields in portal api.
Just need to add them to the cube and provide a way to test (touch base with Aleks, he probably already has a way).

Solution:

add `Dim Machine Classifications` to portal model
- Need Machine Filter keys and values added to reporting model.
Increment schema version to 00009.