Board 11 Release Notes

What's New in Board 11

Data Modeling

Entities: with BOARD 11 when defining a new entity you no longer need to define the max item number, this property and related settings no longer exist.

Cubes: with BOARD 11 when defining a cube you only need to define the entities by which it is structured. You no longer need to define sparsity and secondary versions.   

 

Capsule Designer

Copy & Paste Actions and Shortcuts

It is now possible to copy and paste the layout configuration from the web layout designer. Once a layout is opened there are new buttons available in the editor: Copy, Paste, Clear.

 

copyLayout.png

 

The same function has been added for the Select. So the copy and paste buttons are available on the web select window.

 

copySelect.png

 

A new set of shortcuts has been introduced in different sections of the web designer. Below the list of the shortcuts:

 

Screen Designer:

CTRL+C -> copy toolbox

CTRL+V -> paste toolbox

CTRL+S -> save

CTRL+Z -> undo

CTRL+Y -> redo

DELETE -> delete toolbox

F5 -> refresh layout

F4 -> switch design play

 

Rules:

CTRL+C -> copy rule

CTRL+V -> paste rule

CTRL+A -> select all

ESC -> deselect cell, lost focus

DELETE -> delete rule

 

Layout editor:

CTRL+C -> copy layout

CTRL+V -> paste layout

F5 -> refresh preview

 

Procedure steps:

CTRL+C -> copy toolbox

CTRL+V -> paste toolbox

 

Select window:

CTRL+C -> copy select

CTRL+V -> paste select

Layout Aggregation Functions

The aggregation functions are available in the layout editor on the block settings. These functions replace and enhance the MXC cube functionality.

 

aggregFunctions.png

 

There are three aggregation functions:

The user can filter the counting entity members with a rank. For example, it can restrict the sum only on the top 10 products or on the flop n products or restrict the analysis only on a given range of products in terms of percentiles (i.e. from 20% to 80%).

NEXEL Editor

It is possible to configure the NEXEL layer directly from the web application. The NEXEL can be enabled from the layout editor on the block configuration settings. When enabled it is also possible to select the formula type: single formula or deepest entity formula.

 

Nexel.png

 

Once enabled, the configuration is done from the sliding toolbar of the dataview:

Nexel2.png

Clicking on the fx button, it will open the configuration window where it is possible to define the formula and set-up all the nexel options needed.

Nexel3.png

 

If you want to read more about the NEXEL you can go HERE.

 

Block Format Editor

The Block Format Editor has been added to the web designer. The editor is accessible when the screen is in design mode, selecting the dataview, on the right side configuration panel.

blockformat1.png

 

Clicking on Block Format it will open the configuration window where it is possible to customize the block appearance on the dataview.

blockformat2.png

 

If you want to read more about the Block Formatting you can go HERE.

 

Row Format Editor

The Row Format Editor has been added to the web designer. The editor is accessible from the data model designer, through the Format tile.

rowformat1.png

 

rowformat2.png

 

Clicking on +TEMPLATE it is possible to define and design your row templates through the below configuration panel:

 

rowformat3.png

 

If you want to read more about the Row Formatting you can go HERE.

 

Dataview Suggested Values Drop-down list

It is now possible to set up an entity as suggested values in a dataview column as a drop down list:

entityDropDown.png

Label Shapes

the object label can now be configured with several shapes

 

labelShapes.PNG

 

 

Rules

A new flag has been introduced in the Rules definition: "Authorize editing by power user". If an admin creates a rule, it can give the permissions to the power users to enable that specific rule.

 

Procedures Design

Dataflows

The DataFlow calculations are now by default executed only on the non-null cells of the DataFlow Layout. The Dataflow will process the formula for each combination of the members of the entities that are in the structure of the target cube. Not every potential combination, but only the ones that have a non-zero value on at least one of the Dataflow blocks, each combination is called a tuple.

 

It is possible to extend or reduce the range of processed tuples through the Calculation Domain setting which has been newly introduced.

 

The domain can be limited or expanded:

 

The Calculation Domain allows to explicitly define the range of cube cells that are processed therefore simplifying the definition of Dataflow regardless of the structure of cubes and at the same time optimizing performance by processing only the desired portion of cube.

 

Procedure Temporary Cubes

It is now possible to define within a Procedure one or more temporary cubes that are created and used only locally within the scope of the procedure. Temporary cubes are created at the start of the execution of the procedure and destroyed when the procedure ends. By nature, Temporary cubes only occupy RAM during the course of the execution of the procedure and are never physically stored to disk. Within the procedure, temporary cubes can be used as standard cubes, in Dataflow calculations (as target or source of a Dataflow), in selections, extract and other actions involving cubes.

Temporary cubes are defined in the procedure main property panel.

 

tempCubes.png

 

It is possible to define the name for the cube, the data type and the structure of it (in terms of dimensions).

These cubes are allocated to memory only during the execution of the procedure and are deleted at the procedure completion. The temporary cubes are can be used only within the procedure where they are defined, they are not visible from the Cubes list of the database. Every procedure invocation allocates a different temporary cube, therefore two different users launching the same procedure will not impact each other, they remain fully isolated.

Broadcasting Procedure Step

A Broadcasting action can be invoked from a Procedure:

 

broadcastProcStep.png

 

Learning Mode

The Learning function allows to optimize performance of a Layout by automatically generating best possible pre-aggregated version that improves performance on the layout. To activate learning mode the license level must be developer with administrator rights on the database.

Learning might take some time to be executed. At the end of the learning mode the layout performance will be optimized. Learned cube versions can be deleted from the DB manager. Those versions are auto-aligned versions.

The Learn function is available on the layout editor.

 

Extract Cube Step

The extract cube procedure step has been enhanced. It is now possible to define the structure of the exported file (entities and order). Below the interface available in the procedure designer:

 

extractLogico.PNG

 

Fixes and Minor Changes

 

Upgrade instructions

Version 11 introduces a full web HTML5 client. The windows client has been dismissed. Capsules that are created from the web client have a new format: ".bcps". The old ".cpsx" capsule can be still used in play mode in the old format. Old capsule in ".cpsx" need to converted into the new ".bcps" format to be used in edit mode on the web client (a common web browser). The migration process is automatic and documented HERE. The system will retain a copy of the capsule in the old format renaming it with the "(BKP) tag in the capsule name.

 

Database migration

The following activities must be performed to migrate a database to BOARD 11:

Before upgrading to 11, open the database you want to migrate using your current version (BOARD 10.x or earlier)

 

Now install version 11:

 

 

Important Notice

 The MXC cubes won't be available in the migrated version of the Database. The MXC cubes can be easily replaced by the aggregation functions. If you have any BigData cubes defined in the database, you need to change the cube type to the standard cube one before the database migration. The H-OLAP cubes (MOLAP and ROLAP versions) just keeps the most detailed version after the migration.