Page Comparison

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.