Planual rules regarding Pages
4.02-01 Back to front design
At the beginning of the design process, take the user through the UX principles. Start with the end in mind and work backward.
For example, the requirements for this report are X and Y. As a model builder, I will need to get these values from modules A and B.
bestPracticesArticles
4.02-02 Avoid horizontal scrolling
Try and avoid the screen scrolling horizontally. It's better to fix the grid and scroll within the grid.
relatedToRule
4.02-03 Consider the screen size of the end users
Don't build based on your screen size. Consider the smallest size the users will be viewing the page and build to that size. You should change the screen resolution to double-check how the page will look for the end users.
relatedToRule
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.
4.02-05 Turn off module page selectors
Showing the page selector is appropriate, but try and drive the selection from a general page selector.
relatedToRule
4.02-06 Deep Level hierarchies
Create a separate page with selection modules to keep the main pages clean. This also allows for more efficiency in navigating up and down the hierarchy tree.
4.02-07 Avoid buttons for navigation
Use the App Menu for navigation or the module hyperlinks rather than cluttering your pages with buttons.
4.02-08 Avoid Refresh buttons
Educate the users to use the Refresh option in the toolbar rather than action "refresh" buttons to refresh pages.
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 using a filter.
4.02-10 Use card Title and Description
Use Title and Description when configuring a card, rather than adding text to the page.
relatedToRule
4.02-11 Publish Process Actions instead of Import/Export Actions
Import and Export actions need to be republished if modified or replaced, whereas Processes are always consistent with whatever is held within the Process, making management easier.
relatedToRule
4.02-12 Avoid using Delete action buttons on dashboards for end users
End users could delete historical data, so keep the list element maintenance separate as part of the administration process.
relatedToRule
4.02-13 Store image URLs in Assets
Keep all the image URLs in Assets. To display the image for a certain list member, create a separate System module based on that one list.
relatedToRule
bestPracticesArticles
4.02-14 Enable My Pages
Use My Pages to enable users to personalize the views of the data.
4.02-15 Limit modules with many formatted list line items
Too many list formatted line items displayed on a page can adversely affect performance, especially if the lists are large.
Try and limit the number of displayed line items in a single module. If needed, split the list formatted line items into separate modules.