-
Migrating away from TILDE Datamodel
1. Abstract The use of Tilde ~ databases is a deprecated practice which is incompatible with the Subscription Hub, here we’ll look at the different options for migrating to a modern security configuration. 2. Context Tilde databases allowed the use of very granular user-specific security, however recent versions of Board…
-
Security Recommendations
1. Abstract The security is crucial and critical part of the data model design. It should be considered during the design phase already. In the following chapters clarifications and best practice approaches are described. This document is not a replacement for the manual. It will give some impression/ideas. It is…
-
Dummy entity elements for budgeting purposes
1. Abstract In planning processes, sometimes it is necessary to manage new occurrences that don’t exist in real life yet, which means creating provisional elements in the master data that will serve only for planning purposes. 2. Context Creating provisional elements in master data for planning purposes means creating new…
-
Dynamically manage calendar settings
1. Abstract In many cases, we will need certain mappings in our Calendar to define specific time frames for reporting and planning purposes. Some of those may be custom time dimensions and others might be created by mapping the standard calendar to specific periods. All those mappings have to be kept up-to-date. That can…
-
Normalization in High Concurrency
1. Abstract In Board’s multi-dimensional database, relationships are a core component of a data model configuration. Properly designing and maintaining relationships is essential for a well-functioning solution. Missing relationships, both direct or indirect, can lead to inaccurate or incorrect conclusions or behaviors.…
-
Data Access Control Architecture
1. Abstract Database and Application security refers in general to the range of tools designed to establish and preserve data confidentiality, integrity, and availability. In Board terms it is the definition of the various access levels so that the users are presented and can modify only data relevant to them and for which…
-
Use of Nexel
1. Abstract Nexel is a hugely powerful tool but it has its limitations, it’s important to understand when it’s appropriate to use Nexel and how best to store the original definition screen. 2. Context Use of Nexel can be hugely powerful, and in some cases necessary in order to achieve certain outcomes, however there are…
-
Offset Rules
1. Abstract Offset rules are a type of rule which allow you to reference multiple blocks in the same layout as part of your calculation, they can be very powerful but should be used with caution. 2. Context Offset rules can be very powerful in certain circumstances but should be used with caution due to the complexity they…
-
Naming Convention
1. Abstract The following document is intended to suggest and give concrete examples of the nomenclature to be used during the development of the back end and front end of a Board solution. The aim is to have a consistent and organized nomenclature that led to a maintainable solution that can be easily consulted in the…
