Chapter 4

Apps

4.01-01 Naming Conventions

As short as is practical.  Use Alpha numeric to prefix the Page name to help order the pages correctly on the App Contents page

 

Best Practice article
Understanding Anaplan's UX with Analogies, FAQs and Best Practices

4.01-02 Use Custom Views

Using Custom Views allows the Page Builder to use inherent functionality like richer conditional formatting options

 

Exceptions
4.01-02a – It may be advantageous to use Module Views when the same data layout will be used for more than one Card type (e.g. a grid and a chart)
4.01-02b – Module Views should be used where columns with a certain width are needed
4.01-02c - Module Views should be used when line items need to be reordered or reorganized.

 

Best Practice article
Understanding Anaplan's UX with Analogies, FAQs and Best Practices 

 

4.01-03 Create Output modules when using Custom Views

When staging line items are not needed to be viewed by the page builder, create an output module to be used for generating the Custom View

 

Related to Rule:
2.01-04 Use the D.I.S.C.O. Methodology for Module Design 

4.01-04 Use Boards for smaller datasets

Use Boards to render KPI’s, graphs, variance reporting, reviewing data from multiple modules, landing pages

 

Best Practice article
Understanding Anaplan's UX with Analogies, FAQs and Best Practices

4.01-05 Use Worksheets for larger datasets

Use Worksheets for entering or editing large data sets, pivoting data

 

Best Practice article
Understanding Anaplan's UX with Analogies, FAQs and Best Practices 

4.01-06 Create Pages for Mobile

When creating Apps for mobile, think through the layout of the pages and develop the flow of page elements from left to right within each row on a Board.  It may be appropriate to create a separate App for the mobile with proper spacing among the different elements

 

Best Practice article
Top 5 Design Best Practices for UX—Desktop and Mobile

4.01-07 Use card templates

When utilizing the same module for multiple cards that are the same "card type", then consider saving it as a template.  This will allow increased efficiency when creating boards or worksheets. 

Dashboards

4.02-01 Back to front design

At the beginning of the design process, take the user stories and the UX Principles.  Start with the end in mind

 

Best Practices article:
Designing Dashboards

4.02-02 Avoid horizontal scrolling

Try and avoid the screen scrolling horizontally.  It is better to fix the grid and scroll within the grid

 

Related to Rule: 
4.02-03 Consider the screen size of the end users

 

4.02-03 Consider the screen size of the end users

Don't build based on your screen size.  Consider the smallest size that users will be viewing the dashboard and build to that size.  You should change the screen resolution to double check how the dashboards will look for the end users

 

Related to Rule:
4.02-02 Avoid horizontal scrolling

 

4.02-04 Add Page Selectors rather than module selectors

Use separate page selectors rather than module page selectors, especially if the dimensions are repeated in multiple dashboard elements

 

Related to Rule:
4.02-05 Turn off module page selectors

4.02-05 Turn off module page selectors

Show the page selector is appropriate but try and drive the selection from a general page selector

 

Related to Rule: 
4.02-04 Add Page Selectors rather than module selectors

4.02-06 Deep Level hierarchies

Create a separate dashboard with selection modules to keep the main dashboards clean. This also allows for more efficiency navigation up and down the hierarchy tree

4.02-07 Avoid buttons for Navigation

Use the contents page for navigation rather than clutter the dashboards with buttons

 

Exceptions:
4.02-07a Iterative processes: When the user needs to toggle back and forth between dashboards, it is acceptable to have navigation buttons (old UX)

4.02-08 Avoid Refresh buttons

Educate the users to use the Refresh option in the toolbar rather than action "refresh" buttons to open dashboards

4.02-09 Publish charts with full filters initially

If the chart has a filtered axis, set the filter such that all items are shown, then publish the chart.  Then set the filter criteria back as desired; the chart will then respect the filter

4.02-10 Turn off the Module name

Use dashboard text to describe the grid, rather than display technical module names

 

Related to Rule:
2.01-01 Naming Convention

 

Exception:
4.02-10a Space Saving: If screen space is at a premium, heading text can take up more space than desired, but do consider the overall user experience and don't clutter up the dashboard

4.02-11 Publish Process Actions instead of Import/Export Actions

Import and Export actions need to be republished if modified or replaced, whereas Process Actions are always consistent with whatever is held within the Process, making management easier

 

Relate to Rule:
5.01-02 User Facing Actions in a process

4.02-12 Avoid using Delete action buttons on dashboards for end users

End users could potentially delete historical data, so keep the list element maintenance separate as part of the administration process

 

Related to Rule:
4.02-11 Publish Process Actions instead of Import/Export Actions

4.02-13 Store image URLs in a separate module

Keep all of the image URLs for a list in a separate System module.  Be mindful of the correct dimensionality

 

Related to Rule:
2.01-04 Use the D.I.S.C.O. Methodology for Module Design

4.02-14 Enable Personal Dashboards

Use Personal Dashboards to enable users to personalize the views of the data

 

Related to Rule:
6.04-03 Master Dashboards

 

Best Practice article:
Personal Dashboards - Tips and Tricks

4.02-15 Limit modules with many formatted list line items

Too many list formatted line items displayed on a dashboard can adversely affect performance especially if the lists are large.  Try and limit the number of displayed line items in a single module; split them into separate modules if necessary

Filters

4.03-01 Use efficient filters

For most efficient performance resolve filters to a single Boolean condition for each axis

 

Related to Rule:
4.03-06 Avoid filtering on Nested Dimensions

 

Best Practice article:
Filter Best Practice

4.03-02 Keep Filters in separate modules

Try and keep filters in separate System modules.  They can then be reused for different modules

 

Relate to Rule:
2.01-15 Filters in separate modules

4.03-03 Use time filters on all dashboards

Do not use show/hide function for time; these are static.  Using the Time Settings module makes the filtering dynamic when the model calendar changes

 

Related to Rule:
2.01-07 Time Settings Module

4.03-04 Filter Selections in order of size

If using multiple conditions in a filter, include the conditions in order of list size with numeric conditions last

4.03-05 Use User filters to provide dynamic reporting

Create filter modules dimensioned by the users list to support dynamic filtering of module data

 

Related to Rule:
1.03-02 Performance and size can be dependent Users list

 

Best Practice article:
Increase end user adoption with smart filters

4.03-06 Avoid filtering on Nested Dimensions

If possible, try and avoid filtering on nested dimensions.  Try and pivot the view differently.  If this is not possible, ensure the filters are efficient

 

Related to Rule:
4.02-01 Use efficient filters

 

Best Practice article:
Filter Best Practice

4.03-07 Use notes to document line items used as filters

Make use of the notes section in the blueprint to document where a line item is used as a filter. This will help in the auditing of a model for saved views, and dashboard filters.