Optimized Story Experience Improvements

The chart Builder panel has been redesigned to improve the design experience. These improvements include:

• Removal of the Chart category for better discoverability

• New entry points for the Available Objects panel and Chart Add-ons.

For more information, see Chart Builder Panel Improvements in Optimized Design Experience.

The Available Objects panel allows Story Designers to see all measures, calculations, and dimensions. They can easily add objects to the Builder panel using drag-and-drop or the quick action menu.

For more information, see Available Objects Panel in Optimized Design Experience.

Reference Line - New aggregation types

Custom Sort

With the detection of Filter by Range or Filtering Across Models, the visible section for Custom Sort will be ignored to prevent data incorrectness.

Legends Visibility

We've improved the visibility of the legend by allowing users to explicitly Show or Hide the Legend using the Show/Hide options.

Chart Title, Subtitle, and Footer Styling

Chart Text Styling options are unified with the Text Widget. With this, there are more Styling Options available such as text alignment.

For the footer, the right-click option will now show the Add Dynamic Text option.

Hierarchy & Drilling Appearance

The first hierarchy dimension listed in the dropdown will be chosen as default for non-BW models.

For BW models, the hierarchy must be set in the metadata cube and must not be mandatory for the dimension. For other BW models, the dimension will be shown flat.

In addition, to avoid loading all hierarchies upfront, the hierarchy icon may appear after the dimension is selected.

For dimensions that contain no hierarchies, only the Flat Presentation option will be available in the Set Hierarchy drop-down.

Token Actions and Menu Button Visibility

The Display As option will now apply to the entire dimension. This means that if the dimension is switch from hierarchical to flat, then the Display As option that is set will remain.

Tooltip Measures + Dimensions Entities Limit

There is no longer a limit to the number of entities that can be added to the Tooltip Measure or Dimension section.

Deletion Handling for Measure and Dimension Input Controls

The deletion of a Measure or Dimension Input Control is now aligned with Calculation Input Controls. This means that any Chart that consumes the respective input control will display an error state.

With the creation of a new Single Select Filter, we will not automatically display the All selection. It can still be displayed under the Show/Hide settings.

The size of the selection token beside the description remains consistent with the size of the text with restyle.

Bookmarked information is stored and saved based on User Interaction with the story.

Example: A story designer creates a story with three story filter: A, B, C.

• A story viewer updates story filter A and creates a bookmark.

• The story designer updates the story and removes story filters A and B.

The next time the story viewer opens the saved bookmark, the bookmark is updated based on the following:

• Story Filter A: Appears in the bookmark as the viewer had interacted with it to narrow down the search results when creating the original bookmark.

• Story Filter B is removed from the bookmark, as it was interacted with by the story viewer and removed by the story designer.

  Had the story viewer made changes to this story filter, it would not have been removed from the bookmark, like filter A.

• Story Filters C appears in the bookmark.

  Even though the viewer had not interacted with it, no changes were made by the designer that impacted story filter C.

Story scope linked analysis (shown as story filter) enabled for charts and geographical visualizations:

• New user interface token for story linked analysis filter.

  When the same dimension story filter is used, story linked analysis filter overrides it.

Additional new behaviors:

• Story level linked analysis doesn’t create local filter on visualization.

• Visualizations shows linked analysis filter when page/specified scope linked analysis is used.

• When the local filter resets, the associated linked analysis filter gets deleted. Also, when the linked analysis filter is deleted, the associated local filter gets reset.

• When the designer interacts with the local filter in the builder panel, the associated linked analysis filter gets deleted.

• When multiple widgets act as driver widgets and linked analysis is applied to the same dimension, it merges the linked analysis filter for the driven widget.

Variance is grouped under Applied to Chart in the Context Menu.

The measures listed in the tooltip dimension will only be the measures associated to the data point that is clicked / hovered on. If there is a color measure, it will be included.

There are multiple improvements to the minimum drill state, including the following.

Sorting behavior may change depending on what data is included in the sort.

Measure sort: measure sorting uses the data intersections as the sort type, but the sort is disabled when there are two dimensions.

Dimension sort: break grouping is always disabled when using dimension sorting.

Unbooked data: the heat map will respect the sort that is applied even though unbooked data (nulls) is present.

Version in auto-generated titles: the version will be removed from auto-generated titles (for example, “for Actuals” is removed).

Version in chart details: the version filter will be displayed the same as other widget level filters, except that it cannot be deleted.

Filtering on all data points using interaction: when attempting to exclude all data points in a chart, the exclude button is disabled and shows a helper tooltip.

Remove Member button: Instead of using Remove Member to remove individual members, you can deselect a member the same way you would in story and page filters.

Chart details filter token: The filters that were in the chart (that allowed you to remove or edit filters) have been moved to the action menu (  Applied to Chart).

Expanded dimensions: When the dimension is expanded, applying a rank will now flatten the list while preserving the rank that is applied.

Version: The version drop-down list is hidden when Version (Category) is not included in the Color section.

Auto-generated titles will no longer display the Version (Category)

• Non-optimized story: “{Measure} per {Dimensions} for {Version}”

• Optimized story: “{Measure} per {Dimensions}”

When a chart has a measure, a dimension, and a separate color dimension, applying a sort on the measure (ascending or descending) will break the grouping. This is because the color dimension is now included within the sort.

When Time is the outer-most dimension, auto-limits are applied to the chart and a descending order is applied on the Time dimension.

In Optimized View Mode, because the inner dimension ordering isn't changed, there may be a difference between the visualization that is displayed in Edit Mode versus Optimized View Mode.

Story Viewers can't delete Custom Current Date. This prevents them from accidentally resetting dynamic time filters to System Date.

When you have access to only one member out of multiple members in the hierarchy and you select that one member, the input control selects only that child member instead of the parent member.

Indirect time filters will function like direct time filters in the way that they find a match on a secondary model. This will ensure higher accuracy of data when fiscal time is mapped directly to calendar time.

Indirect multi-dimension links between level-based hierarchies and non level-based hierarchies increases the number of links, resulting in more accurate matches.

Improves generation of target filters and accuracy of data.

The Exclude descendants setting is now on by default when creating new dimension links. This configuration is recommended as it improves performance and accuracy of data.

To ensure that it reflects the actual state of the model in all cases, optimized view mode will check for an active hierarchy in the model before mapping to a secondary model.

BW Time Links are improved for more accurate matches.

The ranking behavior for BW is now aligned with Live HANA where ranking with multiple dimensions returns the Top / Bottom N results across the dataset.

Changing Hierarchy using a variable: The drill is removed, and the filter is preserved with its token. However, a warning will be displayed to indicate that the filter might conflict with the new hierarchy.

Changing Hierarchy using a hierarchy dialog (Flat or Hierarchy): The drill and filter are removed.

Changing Hierarchy to Flat using a variable: The drill is removed, and the filter is preserved.

Whenever a filter is added or updated after a drill, the drill is removed.

Hierarchical input controls will not apply the default anymore. However, the configuration from the input controls is still applied.

When drilling on a REST node, the result set contains the REST node and its children. The chart only displays the children because we've filtered out the REST node.

The linkedNode appears in multiple places, but you can't select or un-select it. (The rest of the nodes can be selected or un-selected).

 The linkedNode only appears on the first expanded parent.

Within a table, the children of a hierarchy will be loaded on demand.

BW Dynamic Filter tokens are now selectable, which means that items can be deselected from the token.

When the exit variable is reset the filter is overwritten.

Opening the variable dialog will now show the exit value. The old behavior can be restored by disabling exits on the local widget.

When the hierarchy variable is submitted, page filters and story filters remain on the old hierarchy.

There will be a warning on input Controls to make user aware of the fact that the filter is NOT on the current hierarchy.

Dependent on BW-InA Patch

• With the BW-InA Patch: the migration to Optimized View Mode is fast as we only fetch the selected nodes and their ancestors.

• Without the BW-InA Patch: the migration to Optimized View Mode will be slow as the entire hierarchy needs to be fetched.