-
Data entry input validation rules
1. Abstract Data entry is an essential component of any planning application within Board. With a dependency on end users, applications should aim to minimize human errors. When data entry is enabled in Board, it allows our end users to input information and write it back into the Board Data Model, contributing to…
-
Drill Anywhere Options: "Drill To" vs "Go To"
1 . Abstract The Drill Functions provide several interactive options, which are: Drill anywhere, Drill-down, Drill-to screen, Drill-procedure. In design mode, interacting with the ‘Drill-to screen’ feature, either in a Data View or in a Chart, there are some notable differences regarding ‘Drill-to screen’ and ‘Go-to…
-
Reporting Layer: Optimize a report
1. Abstract Users are more and more demanding and are looking for the right balance between the correctness of the result and the scalability of the solution at the same time. Improving response time has always been a top priority, therefore the purpose of this document would be to explain the main best practices to apply…
-
Drill Actions
1. Abstract Board offers multiple drill options, it’s important to consider the requirements when planning or setting up drill options and to design the solution accordingly. 2. Context Board offers multiple options when drilling into data, which is the right one to use depends on the specific requirements – whether the…
-
Comparison between different versions or scenarios in the same report
1. Abstract During the implementation of any application, a typical request is to combine multi-scenario or multi-version information in the same view to promote delta analysis and quick data comparison. Board plays an important role due to its flexibility and allows a solution to be achieved in several ways to provide the…
-
Navigation - Tips & Common Mistakes
1. Abstract Talking about navigation, there are several best practices and tips to avoid common mistakes and sources of issues. 2. Content No calculation in navigation procedures: based on what has been discussed in the Application navigation design article, the usage of navigation procedures should be very limited since…
-
Application Navigation Design
1. Abstract Navigation is "the act of moving between screens of an application to complete tasks". It is about managing the path that the users can follow when using an application and therefore it involves defining the different navigation steps (based on the level of flexibility required) and eventually combining them…
-
The Use of Tab Container
1. Abstract As soon as developers face screen creation, in particular, if we are talking about reports or BI Dashboards, where usually a lot of different data has to be shown, they need to use carefully the layouts to avoid any screen object overflow and, consequently, less impactful data meaning. 2. Context In the…
-
Use of Number Scaling
1. Abstract A common requirement when displaying data, particularly financial data, is to use scaling – whether that’s displaying numbers in thousands, millions or whatever makes sense in order to make the displayed data more easily readable. 2. Context There are multiple ways in which scaling can be introduced when…
-
Data Entry Saving Methods
1. Abstract When saving data entry on a Screen, either the data entry Tick can be used or a separate save button. We’ll discuss which should be used, depending on several different variables. 2. Context Use of ‘on data entry’ triggers and save procedures are valid and applicable in different cases. To determine which…
-
On-the-fly Calculations: Pros and Cons
1. Abstract The term “on-the-fly calculation” refers to all the calculations executed directly at the layout level, meaning that the result is not physically stored in a Cube. This directly affects drill-down functionality and has advantages in terms of reducing the overall size. 2. Context During the development phase the…
