"The best journey is the one with the fewest steps. Shorten the distance between the user and their goal." | ||
--Author Unknown |
"It takes less time to do a thing right than to explain why you did it wrong." | ||
--H.W. Longfellow |
Pages are NAV 2015's object type for interactively presenting information. The page rendering routines that paint the page on the target display handle much of the data presentation detail. This allows a variety of clients to be created by Microsoft, such as Web browser resident clients, Windows RTC clients, and new tablet clients (iPad, Android, Windows). Independent Software Vendors (ISVs) have created mobile clients and even clients targeted to devices other than video displays.
One of the benefits of Page technology is the focus on the user experience rather than the underlying data structure. As always, the designer/developer has the responsibility of using the tools to their best effect. Another advantage of NAV 2015 pages is the flexibility they provide the user for personalization, allowing him/her to tailor what is displayed and how it is organized.
In this chapter, we will explore the various types of pages offered by NAV 2015. We will review many options for formatting, data accessing, and tailoring the pages. We will also learn about the Page Designer tools and the inner structures of the pages. Topics we will cover include:
Pages serve the purpose of input, output, and control. They are views of data or process information designed for on-screen display only. They are also user data entry vehicles.
Pages are made up of various combinations of controls, properties, actions, triggers, and C/AL code.
The internal structure of a page maps to an XML structure, some of which is readily visible in the Page Designer display while the rest is in the background.
C/SIDE allows us to create pages with a number of different look and feel attributes. The standard NAV application only uses a few of the possibilities, and closely follows a set of Graphical User Interface (GUI) guidelines that provide consistency throughout the system. These guidelines are described in an interactive document named Microsoft Dynamics NAV 2015 User Experience Guidelines (UX Guide for short). Obtain a copy of this guide from the MSDN Library (https://msdn.microsoft.com/en-us/library/jj651618(v=nav.80).aspx) and study it.
Good design practice dictates that enhancements integrate seamlessly with the existing software unless there is an overwhelming justification for being different. When we add new pages or change the existing pages, the changes should have the same look and feel as the original pages unless the new functionality requires significant differences. This consistency not only makes the user's life easier, it also makes support, maintenance, and training more efficient.
There will be instances where we will need to create a significantly different page layout in order to address a special requirement. Maybe we need to use industry specific symbols, or we need to create a screen layout for a special display device. Perhaps we are going to create a special dashboard display to report on the status of work queues. Even when we are going to be different, we should continue to be guided by the environment and context in which our new work will operate.
Let's take a look at what makes up a typical page in the NAV 2015 Role Tailored Client. The page in the following screenshot includes a List page at its core (the content area).
Following is a brief description of all these options:
If we click on one of the right-facing arrowheads in the Address Bar, the child menu options will be displayed in a drop-down list (as can be seen in the following screenshot). The same list of options subordinate to Sales Orders is displayed both in the drop-down menu from the address bar, and in the detailed list of options in the navigation pane.
If we click in the blank space in the Address Bar to the right of the breadcrumbs, the path display will change to a traditional path format, as shown next: