Beruflich Dokumente
Kultur Dokumente
1 Manual
Table Of Contents
Foreword ........................................................................................................................................................ 1
Board Capsules and Databases .................................................................................................................... 2
BOARD Capsules and Databases ............................................................................................................. 2
Board Capsules .......................................................................................................................................... 2
Board Databases ........................................................................................................................................ 4
The workspace ............................................................................................................................................... 5
Installation concepts....................................................................................................................................... 6
Installation concepts ................................................................................................................................... 6
Choosing the architecture .......................................................................................................................... 7
Stand-alone installation overview ............................................................................................................... 7
CMS installation overview .......................................................................................................................... 8
WebServer installation overview ................................................................................................................ 8
The Client-Master-Server Architecture .......................................................................................................... 9
Component connections and deployment ..................................................................................................... 9
Application architecture ................................................................................................................................ 11
Deployment configurations .......................................................................................................................... 11
Deployment configurations ....................................................................................................................... 12
Stand-alone installation ............................................................................................................................ 12
CMS installation........................................................................................................................................ 13
Dimensioning criteria.................................................................................................................................... 15
Dimensioning criteria ................................................................................................................................ 15
Running multiple sessions of BoardServer .............................................................................................. 15
Server clustering and dynamic load-balancing ........................................................................................ 16
Board in a demilitarized zone (DMZ) ........................................................................................................... 17
Board Client installation and configuration .................................................................................................. 19
BoardMaster and BoardServer installation .................................................................................................. 22
BoardMaster configuration ........................................................................................................................... 23
BoardMaster configuration ....................................................................................................................... 23
CMS configuration tab .............................................................................................................................. 23
Web Configuration tab .............................................................................................................................. 25
Security ..................................................................................................................................................... 28
How to create a User Group..................................................................................................................... 29
How to create a user account................................................................................................................... 32
How to find a user account ....................................................................................................................... 33
Licenses and accounts summary ............................................................................................................. 34
Monitor ...................................................................................................................................................... 34
Options Tab .............................................................................................................................................. 35
Board Server configuration .......................................................................................................................... 36
Installation example of a StandAlone architecture....................................................................................... 39
iii
Table Of Contents
Defining time entities relationships ........................................................................................................... 68
Adding and deleting members of a custom time entity ............................................................................ 69
Assigning relationships ............................................................................................................................. 70
Viewing a relationship in analytical mode ................................................................................................ 71
Viewing a relationship in summarized mode ............................................................................................ 72
Identifying missing relationships (orphan items) ...................................................................................... 73
Assigning a relationship to all orphan items ............................................................................................. 73
Entities ......................................................................................................................................................... 74
Basic concepts ......................................................................................................................................... 74
Creating an entity ..................................................................................................................................... 74
Defining the Max Item Number................................................................................................................. 76
Modifying entity properties ....................................................................................................................... 77
Deleting an entity ...................................................................................................................................... 78
Setting the entity cut-off ............................................................................................................................ 78
Inserting, editing and deleting entity members ......................................................................................... 79
Deleting all entity members ...................................................................................................................... 80
Relationships................................................................................................................................................ 81
Basic concepts ......................................................................................................................................... 81
Defining a relationship .............................................................................................................................. 82
Removing a relationship ........................................................................................................................... 83
Assigning a relationship ........................................................................................................................... 83
Viewing relationship in analytical mode.................................................................................................... 85
Viewing relationship in summarized mode ............................................................................................... 85
Identifying missing relationships (orphan items) ...................................................................................... 86
Assigning a relationship to all orphan items ............................................................................................. 86
The Normalize function ............................................................................................................................ 86
InfoCubes ..................................................................................................................................................... 87
Basic concepts ......................................................................................................................................... 87
Introducing sparse structures ................................................................................................................... 88
Sparse actual size and density................................................................................................................. 89
The sparse types: Dynamic, Static and Static External ........................................................................... 90
About InfoCubes, versions and sparse structures ................................................................................... 91
Numeric data types................................................................................................................................... 91
MXC data type .......................................................................................................................................... 92
Text data types ......................................................................................................................................... 92
Date data type .......................................................................................................................................... 93
Creating an InfoCube ............................................................................................................................... 93
Copying an InfoCube structure................................................................................................................. 95
Creating a new InfoCube with the same structure as an existing one ..................................................... 95
Moving an InfoCube ................................................................................................................................. 95
Adding a new version to an InfoCube ...................................................................................................... 95
v
Table Of Contents
Assigning a security profile to a user account ........................................................................................ 127
DB Verify &endash; database integrity check and optimization ................................................................ 127
Log file ........................................................................................................................................................ 127
Capsule basic concepts ............................................................................................................................. 129
Prerequisites........................................................................................................................................... 129
Capsule structure ................................................................................................................................... 129
Understanding Runtime mode and Design mode .................................................................................. 130
Working with Capsules .............................................................................................................................. 131
The Capsule object model ...................................................................................................................... 131
Opening a Capsule ................................................................................................................................. 131
Navigating through screens.................................................................................................................... 131
Workspace features................................................................................................................................ 133
Collaboration functions .............................................................................................................................. 133
Boards collaboration functions .............................................................................................................. 133
Presenting a Briefing .............................................................................................................................. 134
Attending a Briefing ................................................................................................................................ 135
Running a Synchronous Collaborative session...................................................................................... 136
The Workspaces DynaSheet and DynaWrite ........................................................................................... 138
The Select .................................................................................................................................................. 138
What is the Select function ..................................................................................................................... 138
Making a selection .................................................................................................................................. 139
Resetting a selection .............................................................................................................................. 139
Adding entity members to a selection .................................................................................................... 140
The Find function .................................................................................................................................... 141
The Keep function .................................................................................................................................. 141
The Focus function ................................................................................................................................. 142
The time entities scroll buttons ............................................................................................................... 142
The DynaBar .............................................................................................................................................. 142
What is the DynaBar............................................................................................................................... 142
Configuring the DynaBar ........................................................................................................................ 143
Using the DynaBar ................................................................................................................................. 144
DynaBar synchronization across screens .............................................................................................. 144
Drill-down and drill-through ........................................................................................................................ 145
How to drill-down .................................................................................................................................... 145
How to drill-through ................................................................................................................................ 146
Printing from a drill-down window........................................................................................................... 146
Exporting data to Microsoft Excel .............................................................................................................. 147
Capsules Management .............................................................................................................................. 147
Copying and Deleting Capsules ............................................................................................................. 147
Copying or deleting Capsule screens or Procedures ............................................................................. 147
Opening a capsule from command line .................................................................................................. 148
vii
Table Of Contents
Button ......................................................................................................................................................... 180
The Button object ................................................................................................................................... 180
Creating a Button.................................................................................................................................... 180
Button Appearance ................................................................................................................................. 180
Button Actions ........................................................................................................................................ 181
Button Options ........................................................................................................................................ 182
Picture ........................................................................................................................................................ 183
The Picture object................................................................................................................................... 183
Creating a Picture or a text label ............................................................................................................ 183
Folder ......................................................................................................................................................... 184
The Folder object.................................................................................................................................... 184
Creating a Folder .................................................................................................................................... 184
DataView .................................................................................................................................................... 185
The DataView object .............................................................................................................................. 185
Creating a DataView .............................................................................................................................. 185
Data-entry features ................................................................................................................................. 185
Formatting options .................................................................................................................................. 186
Drill-down on a cell ................................................................................................................................. 187
Graph ......................................................................................................................................................... 188
The Graph object .................................................................................................................................... 188
Creating a Child Layout Graph ............................................................................................................... 188
Creating a Stand-alone Layout Graph ................................................................................................... 189
Formatting a Graph using the Chart Wizard .......................................................................................... 190
Formatting a Graph using the Chart Designer ....................................................................................... 190
Creating and using chart templates........................................................................................................ 192
GDE Graphic Data-entry ......................................................................................................................... 192
The GDE object ...................................................................................................................................... 192
Creating a Child Layout GDE ................................................................................................................. 193
Creating a Stand-alone Layout GDE ...................................................................................................... 194
Using a GDE........................................................................................................................................... 194
Setting a background picture on the GDE object ................................................................................... 195
Mapping ..................................................................................................................................................... 195
The Mapping object ................................................................................................................................ 195
Creating a Mapping ................................................................................................................................ 196
Using a Mapping chart ........................................................................................................................... 196
Setting a background picture on the Mapping object ............................................................................. 198
Cockpit ....................................................................................................................................................... 198
The Cockpit object .................................................................................................................................. 198
Creating a Cockpit .................................................................................................................................. 199
Using a Cockpit ...................................................................................................................................... 200
Setting a background picture on the Cockpit object ............................................................................... 201
ix
Table Of Contents
Select ...................................................................................................................................................... 230
Process ................................................................................................................................................... 231
The DataFlow process ........................................................................................................................... 232
Print ........................................................................................................................................................ 234
Launch .................................................................................................................................................... 235
Data Read .............................................................................................................................................. 235
Xtract ...................................................................................................................................................... 237
More ....................................................................................................................................................... 238
The Broadcasting function ......................................................................................................................... 238
About the Broadcasting function ............................................................................................................ 238
How to set up a Broadcasting screen..................................................................................................... 239
Board Web Server basics concepts ........................................................................................................... 241
About Board Web Server ....................................................................................................................... 241
About Board Web Queries ..................................................................................................................... 241
The Board Web root directory ................................................................................................................ 241
The Web Server architecture ..................................................................................................................... 242
Overview................................................................................................................................................. 242
Notes on Security ................................................................................................................................... 242
Getting started............................................................................................................................................ 242
Installation and overview ........................................................................................................................ 242
Notes on Database design and content ................................................................................................. 243
Building your Board Management Intelligence Quick Site ......................................................................... 243
What is Quick Site .................................................................................................................................. 243
Board Quick Site features ...................................................................................................................... 244
Quick Site navigator tree ........................................................................................................................ 244
Personal folders and Group folders ........................................................................................................... 246
The online Query Builder and Query Manager .......................................................................................... 246
Accessing the Query Builder .................................................................................................................. 246
Creating a query using the Query Builder .............................................................................................. 247
Saving a Board Web query .................................................................................................................... 250
Query Builder functions reference .......................................................................................................... 251
Fundamental end-user functions ............................................................................................................... 258
Navigating through an existing query ..................................................................................................... 258
Changing page ....................................................................................................................................... 259
Changing selection ................................................................................................................................. 260
Saving a Query to a MS-Excel file.......................................................................................................... 261
Using the Drill-down and Drill-through features ..................................................................................... 261
Printing a query ...................................................................................................................................... 262
Data entry options .................................................................................................................................. 262
How to port Capsules reports to the Board Web queries .......................................................................... 264
Generating the Board Web query script from a Capsule ....................................................................... 264
xi
Table Of Contents
LDAP and AD authentication .............................................................................................................. 297
Microsoft AD Authentication ............................................................................................................... 299
OpenLDAP Authentication .................................................................................................................. 301
LDAP General concepts ..................................................................................................................... 304
Release notes for version 6.0D.................................................................................................................. 306
Release notes for version 6.0 .................................................................................................................... 307
What's new in version 6.0....................................................................................................................... 307
Instructions for upgrading to version 6.0 ................................................................................................ 308
Skins: interface look and feel themes..................................................................................................... 309
The DynaWrite++ environment .............................................................................................................. 310
The DynaSheet++ environment ............................................................................................................. 314
DataView cells as Buttons ...................................................................................................................... 317
Sorting on columns of a DataView or DynaSheet report........................................................................ 318
The BLOB InfoCubes ............................................................................................................................. 318
Data-entry Locking ................................................................................................................................. 321
Drill-to Child Screen................................................................................................................................ 322
The Select Based On Action .................................................................................................................. 325
The automatic roll-up rule ....................................................................................................................... 326
New Select options ................................................................................................................................. 328
Changes to the Button and Picture objects ............................................................................................ 330
On-screen-exit procedure ....................................................................................................................... 330
Version 6.0 other changes and bug-fixes ............................................................................................... 331
Release notes for version 5.6D.................................................................................................................. 333
Release notes for version 5.6B .................................................................................................................. 334
Release notes for version 5.6 .................................................................................................................... 337
What's new in version 5.6....................................................................................................................... 337
Instructions for upgrading to version 5.6 ................................................................................................ 338
BoardClient version 5.6 new features .................................................................................................... 339
DataView Dynamic format .................................................................................................................. 339
DataView Header ................................................................................................................................ 341
Cockpits enhanced ............................................................................................................................. 344
Multi-language Database capabilities ................................................................................................. 346
Capsule Themes ................................................................................................................................. 348
Improved performance for large reports ............................................................................................. 351
BoardClient 5.6 - Other changes ........................................................................................................ 351
Board Web Server version 5.6 new features ......................................................................................... 353
The Web Menu Designer .................................................................................................................... 353
Web Button Themes ........................................................................................................................... 358
Board Web Server Pages ................................................................................................................... 359
Release Notes for version 5.5E ................................................................................................................. 369
Release notes for version 5.5B4 ................................................................................................................ 370
xiii
xiv
version 6.1
User manual
Foreword
Board-Management Intelligence has been designed to provide an information management tool to
assist decision-making processes that ensures:
Speed
Ease of use
Rapid applications development
Interactive modelling
BOARD is a unique product, based on an abstraction rooted in a profound knowledge of
organizational and management issues. In addition to simple analysis and data navigation (normally
referred to as Business Intelligence), BOARD models information and processes to perform advanced
simulations and help answer predictive-type questions. This can all be carried out without any
programming and with total adaptation to any company structure.
BOARD heralds a new category of products, designed to place technology at the service of
management needs: Management Intelligence Toolkits. BOARD is extremely versatile, providing the
right tools to improve decision-making at every level and function of a company. In addition, due to
BOARDs exceptional ease of use, costs associated with application development, maintenance, and
user training are extremely low.
Board Capsules
A Capsule generally is a collection of screens, each containing single or multiple objects such as
spreadsheets charts, images or dashboards and indicators.
A Capsule is the end-user environment that allows viewing and manipulating data from a Board
database, it provides the typical multidimensional analysis functions such as drill-down and slice and
dice and several more.
Capsules made of several screens generally include buttons allowing navigation from one screen to
another, providing the user with a guided and logical path through the various business analyses,
simulation models or business tasks such as a companys budgeting process.
A Capsule may also be a free and unstructured environment for ad-hoc analysis. Users can create
their own Capsules and manage them in a personal folder. The Capsule Designer environment
provides tools and objects &endash; with native data analysis features - for creating simple reports or
complex business models.
A Capsule does not necessarily only hold data presentation objects like spreadsheets and charts, it
may also include some database administration tasks organized in a Board Procedure. A Procedure is
a sequence of actions such as a DataFlow, which is a calculation between InfoCubes (for example
calculating the Cost of good sold by multiplying the InfoCubes Quantity times the Product
Standard Cost) or a DataReader, which is a process that loads data from a given data source into a
Board Database.
In a typical Board environment all the different types of Capsules can be found. The analysis
Capsules, holding the reports and charts and other analysis objects. The application Capsules, which
are Management Intelligence applications combining reporting with data-entry and simulation screens.
Finally, the administration Capsules, managed by the database administrator for the management of
the database such as scheduled daily updates, reports distribution etc...
It has never been so easy to create reports and sophisticated analysis which are perfectly tailored to
your requirements and of outstanding presentation quality.
Hereafter are a few examples of Capsules which can be created with only a few mouse clicks.
A sales performance monitoring analysis example.
A Dashboard example
3
Board Databases
Boards database engine is designed to ensure maximum efficiency in managing very large volumes
of data and to provide top-level performance. The implementation of exclusive multidimensional
management techniques completely avoids the database explosion problem typically associated with
multidimensional databases (also referred to as M-OLAP).
Boards databases are multidimensional and are therefore optimal for online analytical processing
(OLAP) of applications. Conceptually, a multidimensional database uses the idea of a data cube
where the cube dimensions represent the different possible perspectives on data. For example, a
"sales" cube could be viewed by various dimensions such as product (i.e. the sales figure per
product), geography (i.e. sales figure by city or region), time and so on.
The information, such as turnover, balance sheets, general expenses, etc., is stored in
multidimensional objects called InfoCubes that are structured by Entities (such as Month, Customer,
and Product). Some Entities can be linked by relationships to establish hierarchical structures (e.g.
Customer Country State).
A Board database is made up of
Entities: these are information sets, generally text and codes like the set of Customers, Products,
and Cities. Entities (and hierarchies) are the InfoCubes dimensions.
Hierarchies: when two or more entities have an n-to-one relationship, then a hierarchy can be
defined. For example, the entities Customer, City and State can be organized into the hierarchy
Customer City State since there is an n-to-one relationship existing between Customer and
City and between City and State.
InfoCubes: the data (often numerical but not strictly) that can be analyzed and viewed by its
different dimensions.
Entities, Hierarchies and InfoCubes form the multidimensional data model of the company or more
generally the system modelled. We will use term dimension to refer to an independent entity or an
entire hierarchy, used as an axis for an InfoCube. For example, the entity Currency can be a
dimension for InfoCubes such as Orders figure and Invoice figure. The three entities Customer, City
and State, being hierarchically related form a unique dimension referred to as the Customer dimension
&endash; the dimension is named after the entity at the bottom of the hierarchy.
The workspace
The following illustration shows Boards main environment.
Click the connect icon to connect to a Board server and view the list of existing Capsules and
databases.
The Toolbar contains all icons to access and work with datatabases and Capsules. Depending on the
Board license and on the users security privileges, some icons may be disabled. For example, to
access any database design function you must have the appropriate developer license (called FULL
license) and have designer privileges on the database. The design toolbar can be hidden or shown by
pressing the F4 key on the keyboard or by clicking the design icon.
The Navigator shows the list of Capsules and databases. To open a Capsule, click the desired
Capsule name,
Installation concepts
Installation concepts
This section provides an overview of the installation process, detailed instructions are provided in
subsequent chapters. To evaluate which architecture best suits your needs, we recommend having a
careful read through the chapter entitled ’Architecture, which illustrates in detail the technical
and functional characteristics of the various architectures.
The installation process requires going through the following four main steps:
Client-Master-Server (CMS), this is the typical multi-tier client/server architecture used in multi-user
environments. The Board databases and Capsules reside on a server where the BoardMaster
and BoardServer programs are installed. On users PCs, only the BoardClient program should be
installed. Users connect to the Board server which will carry out all the required processing on the
multidimensional databases. This architecture uses the servers resources only. Users can
connect to the Board sever through any type of TCP/IP network (a LAN, WAN, Intranet or the
Internet).
BoardClient users can access the Capsules environment and provided they have an appropriate
license, they can also access the database design environment.
Note! For a CMS installation a Board license of type CMS is required. The BoardMaster
program detects and verifies the licenses authenticity. For more details on licenses,
refer to the Licenses chapter.
WebServer, this architecture is similar to the CMS since the Board database resides on the server
and the processing also is carried out by the server, however users only need an Internet
browser such as Microsoft Internet Explorer or Netscape Navigator.
Internet browser users do not access Capsules, they navigate through a Board web site where
some Board analyses are found. It is not possible to access any database design functions such
as creating Infocubes, Entities and relationships, via the Internet browser.
Note! For a WebServer installation, a license of type CMS with E-Server users is
required. The BoardMaster program detects and verifies the licenses authenticity. For
more details on licenses, refer to the specific Licenses chapter.
run BoardClient installation program and follow instructions. This setup program only prompts the
destination directory (the default is c:\Board.Sys ) and installs BoardClient.exe and
KeyManager.exe programs.
2.
run BoardServer installation program, follow instructions and choose the same destination
directory used for the BoardClient program. This setup installs several programs including
BoardMaster.exe, BoardServer.exe and others.
3.
launch the KeyServer program to create and activate your Board license. Refer to the Licenses
chapter for details on how to create and certify your StandAlone license.
4.
run the BoardClient program by clicking the BoardClient icon from Windows Start menu or double
clicking the BoardClient.exe program file.
5.
The first time BoardClient is started, the Local Setup window opens automatically: define your
preferences such as the default user name, connection name, background colors etc.
You are now ready to start using Board. To run the BoardClient program, click the BoardClient icon
from the Windows Start menu or double clicking the BoardClient.exe program file.
run the BoardServer installation program. This will install BoardMaster.exe, BoardServer.exe and
KeyManager.exe programs.
2.
launch the KeyServer program to create and activate your CMS license.
3.
Run the BoardMaster program. Enable the CMS service checkbox located on the first tab, then
go to the Security tab to define user accounts: username, password and privileges.
4.
The server is now fully configured and ready to accept connections from Boardclient users.
On each of the client computers,
1.
2.
run the BoardClient program by clicking the BoardClient icon from Windows Start menu or double
clicking the BoardClient.exe program file.
3.
The first time BoardClient is started, the Local Setup window opens automatically: In the Host
field, type the IP address of the BoardMaster server, then enable the option ”Ask
password at logon (this step is detailed in chapter BoardClient).
2.
Run the BoardWebKit setup program. This will create Boards web site home directory.
3.
Launch the KeyServer program to create and activate your CMS license for E-Server users.
4.
Run the BoardMaster program. Enable the WEB service checkbox located on the second tab
(named Web), then go to the Security tab to define user accounts: username, password and
privileges.
5.
will
install
BoardMaster.exe,
The Board server is now fully configured. No configuration is needed on the users PCs.
8
We can identify four layers: BoardClient, BoardMaster, BoardServer and the Board databases.
9
To evaluate the optimal location for each component, it is important to consider the functional role of
each layer.
Several connection types can be established between each component as summarized in the
following schema:
10
Application architecture
Board applications (Capsules and databases) may be stored locally on the PC, on a server on the
LAN or hosted on a server accessed through a WAN. It is therefore possible to either centralize the
companys applications in a single site, or to decentralize applications but still provide every user in
the company access to any Capsule and database, regardless of where it is held (be it on a local or
remote server).
The two architectural options:
Several factors should be considered when planning the location of applications, such as: availability
of human resources with the required skills, hardware availability, and other organizational
considerations. It is important to note that this choice should not be driven by technical considerations;
users can access their Board applications regardless of their physical location.
Deployment configurations
11
Deployment configurations
There are two main types of installations:
Stand-alone: also referred to as Desktop installation, the processing takes place on the client
PC
Client-Master-Server (CMS): processing takes place on the server, the client only receives
the results
The following sections describe the different architectures available and aim to provide all relevant
information which may be necessary in order to evaluate and plan the architectures which best suit
your project.
Stand-alone installation
In a stand-alone (or desktop) architecture, the users PC calculates the reports and all other database
activities. This occurs regardless of the database location, which might reside on the PCs local hard
disk or on a network servers shared disk. The response time of reports and calculations is determined
by the processing power of the users personal computer. With a stand-alone architecture, the users
hardware is of upmost importance and must be proportional in size to the Board database and the
desired response times.
In a stand-alone architecture:
The BoardClient and BoardServer programs are installed on the same computer and
connected directly (local connection), without going through a BoardMaster
It is not necessary to install BoardMaster
The Board database can reside either on the local hard disk or on a shared network folder, in
the latter case the server will only act as a file server
This architecture does not optimize network traffic but does not require much processing workload
from the server (very little CPU and RAM resources are required for file sharing). This architecture fully
utilizes the processing power of the users PCs.
This is the preferred configuration option when:
12
Note! When comparing the stand-alone architecture to the CMS architecture (described
hereafter), consider that performance for the stand-alone solution is not substantially
affected by the number of users, but is dependent on the performance of the users PC.
Generally, PCs are less powerful than servers, the CMS architecture can leverage power
of the server, but the critical point in this architecture is ensuring stable performance as
the number of users grows. When evaluating the necessary hardware for the server, you
should estimate not only the number of users during peak hours but also the users
scalability (i.e. how much the number of users will grow by in the future?).
CMS installation
In the CMS architecture, the computer where BoardServer is installed executes reports and all other
database activities.
In a CMS architecture:
BoardClient and BoardMaster program are installed on different computers.
BoardMaster and BoardServer generally are installed on the same computer but may also
be on different computers within the same LAN.
The Board database should be stored on the hard-disk of the BoardServer computer, or in
a shared directory within the BoardServers LAN.
The BoardClient connects only to the BoardMaster.
On the server computer, several sessions of BoardServer must be executed to grant
parallel processing for simultaneous requests.
The BoardMaster program manages the incoming users requests then dispatches them to
the various BoardServers, providing dynamic load balancing.
13
The network traffic between BoardClient and BoardMaster is very low; this allows for an efficient
connection through a WAN or Intra/Internet. It is therefore possible for some users connect to the
BoardMaster from remote sites (e.g. from an affiliate company in another city or country) as illustrated
below.
14
Dimensioning criteria
Dimensioning criteria
In a CMS architecture, the centralized processing on the server is the critical factor that determines
performance. The servers hardware should have sufficient power to sustain satisfactory performance
during utilization peaks. It is important to benchmark not only the response times of the most
commonly used reports but also the response times when multiple users are working simultaneously.
The average number of simultaneous users and the maximum number of simultaneous users (referred
to as the utilization peak) also need to be estimated.
In case users need to access the Capsules from remote locations (through a WAN, Intranet, modem)
some techniques to minimize network traffic should be considered in the design of the Capsules and
databases. Tuning guidelines for remote access will be discussed in detail later. however, here is brief
example for illustrative purposes: embedding large pictures and background images in a Capsule may
generate high traffic and consequently affect performance; transfer times improve by reducing
embedded pictures.
When a Board user sends a request, BoardMaster assigns it to the first available BoardServer. If a
second request arrives from another user while the first one is executing, BoardMaster assigns it to
the next available BoardServer. Should all sessions of BoardServer be busy, the request is held in a
queue and will be executed as soon as a BoardServer completes its current processing. When a
BoardServer completes a request, it returns the result to the BoardMaster, which instantly returns it to
the user.
15
Note! Only multi-processor computers can grant true parallel processing of requests.
On single-processor computers, the parallelism of BoardServers is fictitious; it is
simulated by the operating system that assigns the unique CPU to the BoardServers on
a time-sharing basis. For this reason, using multi-processor computers brings
substantial benefits to CMS architectures.
16
The server where BoardMaster is installed is the primary server and remains the only address to
which users connect.
All users are registered only on the primary server that performs the user authentication
process.
The secondary servers are transparent to the users. No re-configuration is needed on the
BoardClient when a server is added to or removed from the cluster. The users cannot recognize
which server the requests are assigned, this is controlled by the BoardMaster on a loadbalancing basis.
The pool of BoardServers is managed with a dynamic algorithm. The assignment of requests to
a BoardServer is re-evaluated dynamically for each request in order to minimize response time.
Two requests from the same user could be dispatched to different servers since BoardServer
processes are state-less.
The secondary servers must be connected to the primary server through a 100 Mbps LAN
connection.
The number of BoardServer sessions to launch on each computer is not fixed; it should be
determined based on the hardware characteristics of the computer (single or multi processor,
size of RAM).
Note! When configuring secondary servers, it is necessary to specify where the Board
databases are stored (usually on the primary server). The secondary servers access the
database through a shared directory on the LAN. To maximize performance, it is possible to
create local copies of the database on the secondary servers. In doing so, all BoardServers
access the database from the local hard disk, resulting in better performance. This can only
be implemented when all users access the Board databases with read-only access (no writeback and no updates to the database are made by any user). Board does not synchronize
the local copies of the databases; this must be done with other tools external to Board. A
program that provides file copying is sufficient. We recommend copying the entire database
folder to all secondary servers after every database update (for example, when new data is
loaded from the datareader).
18
Notes! BoardClient is not supported on Windows 98, ME and XP Home Edition. Screen
resolution 800x600 does not allow you to correctly use BoardClient.
Note that the first time BoardClient is run, the local Setup window opens automatically.
To open the Setup window, click the icon highlighted in the following illustration,
19
User name
Password
Host IP Address
20
UserName
Password
Optional field to store the password for the user name (prior
field).
Note! This password is stored on the BoardClient. If this option
is used, it is strongly recommended that you enable the option
”Ask password at Startup to maintain a secure access
to your Board applications. For the most effective security, it is
recommended that you do not use this option and instead let
the user type the password every time they connect to a
BoardMaster.
Voice Port
Socket number for the voice traffic with the BoardMaster. Ask
your Board system administrator for the BoardMaster voice
port number. Voice transmission is only activated by the
Synchronous Collaboration function (formerly called Peer-toPeer). The default value is 8000 but it may be re-tuned as
desired by the system administrator.
Note! If there is a firewall between BoardClient and
BoardMaster, the TCPIP traffic on this port must be enabled.
21
Report Rows Upper Limit Sets the maximum number of rows for a report. The purpose of
this threshold is to avoid executing very large reports (runaway
queries).
Note that this value must not exceed the equivalent setting of
the BoardServer.
Buffer active when row
number >
Sets the report buffer limit. To allow exporting data to MSExcel, set a value greater or equal to 70,000.
Ask password at StartUp When this option is enabled, BoardClient prompts for a
password at start up. The program closes after three failed
attempts.
Ask password at LogOn When this option is enabled, BoardClient prompts for a
username and password when logging on to a BoardMaster. If
a default user name and password are defined, then they are
automatically displayed in the logon window.
Paper Size
Default BackColor
Board License Controller Specifies the Board license type. Select the type of license
available from the drop down list. Hardware licenses are
named with the prefix ”HL. For any standalone
software license, select the option ”Software Key. For
contemporary user licenses, choose the option ”Public
Key.
Note! In most cases the system automatically detects
the appropriate setting.
The Software Key option will be selected automatically when
a valid Board StandAlone license file is detected. The
StandAlone license file (a file with extension .KEY) should be
located in the same directory as the BoardClient program;
When a valid license is not detected, then the value will default
to OnLine License. This is the case when a concurrent-users
license is installed on the server, the BoardClient will only
obtain the license grant when connecting to the server.
F7 Export
Hardware requirements
Processor: Pentium 4 or above
Physical memory: minimum 256 MB RAM, recommended 512 to 1GB.
The following operating systems support BoardMaster and BoardServer:
Windows NT 4 with Service Pack 6
Windows 2000 Professional or Server Edition with Service Pack 3 (or later editions).
Windows XP Professional Edition with Service Pack1
Windows 2003 Server.
Note! For ODBC connections, MDAC 2.7 Service Pack 1 (or later editions) is required.
To install BardMaster and BoardServer, run the setup program and follow the on-screen instructions.
Note! A certified Board license file (KEY file), either StandAlone or CMS license, must be
present in the directory where BoardMaster is installed. When a CMS license is detected,
BoardMaster assumes the role of license manager.
BoardMaster configuration
BoardMaster configuration
The BoardMaster program has four configuration tabs.
CMS tab includes the configuration parameters needed to setup the CMS service (the ROAR
protocol), which is the service that allows BoardClients to connect to the BoardMaster.
WEB tab includes the parameters for the HTTP service, which is for access through a web browser.
Security tab, allows defining the user accounts and security privileges.
Monitor tab, shows the status of the CMS and HTTP services and the connected users.
Note! If BoardMaster does not detect a valid license file (KEY file), the Security tab does
not appear and it is not possible to define user profiles. In cases where BoardClient users
have their own StandAlone license, a zero users license should be installed on the
BoardMaster computer.
23
Activate
Enable this to option to activate the CMS service, allowing BoardClient users
to connect to the BoardMaster. When the Start button is clicked, a TCP/IP
service (using the ROAR protocol) is started on the port number defined by
the Local Port field.
Board Q Path
Unicode
24
BoardServer.exe Path
Type the full path and name of the BoardServer.exe file. This field
generally defaults to the correct value.
Nr.
Local port
Port number used to accept connections from BoardClients. This same port
number must be set on the BoardClient configuration (in the Setup window) as
BoardMaster port.
Voice Port
Port number used for voice traffic. This port number must be set on the
BoardClient configuration (in the Setup window) as BoardMaster voice port.
Time out
Network servers
This option allows you to set up a cluster of servers providing dynamic load
balancing.
In the first available row, type the secondary server address (using the IP
address or the UNC name), then the socket number and the number of
BoardServer processes running on that computer.
The Active checkbox must be enabled for the BoardMaster to include the
server in the load balancing server pool. When disabled, the secondary server
is considered off-line.
Note that the BoardServer sessions must be launched separately on the
secondary servers; the BoardMaster does not launch processes on other
computers.
25
Activate
Enabling this to option activates the WEB service. The web service is a HTTP
service that allows users to connect through an Internet browser. An appropriate
license for E-Server Users must be present in order to run this service.
BoardMaster can simultaneously run both WEB and CMS services. In this case,
the BoardServer sessions are dedicated to a specific service. For example, it is
possible to configure 5 BoardServer sessions for the CMS service and 3 for the
WEB service.
Base Path
HTTP
service
home
directory.
The
default
value
”C:\BoardPub”.This directory must be on a local hard disk.
is
Board Q Path
This parameter is also present in the CMS tab, refer to prior section for details.
Local Port
Port number of the HTTP server. The default value for HTTP services is 80, it is
recommended you use the default value unless this port is already in use by
another HTTP server running on the same computer.
Timeout
This time out parameter is the maximum time that the BoardMaster waits for a
response from BoardServer. If the BoardServer does not return the result to a
users request within the timeout, then a time out message is sent to the user.
Local Servers Nr
Database
26
Type the names of databases that should be made available through Board Web
server.
Password
protected,
type
the
database
Path
Type the full path of the folder where the BOARD Database is located. Note that
when the Board database is the standard \Board\Database directory (with
Main as the alias) then this parameter should be omitted (leave the field blank).
Alias
If the Board database is not located in the main database folder (alias is Main)
type the BOARD Database alias. Otherwise, when the database is located in the
standard main directory, leave this field blank as done in the prior field.
When this option is active, the left navigation menu of the Board Quick site is
refreshed every time the WEB service is started.
When the number of existing reports is high, refreshing the left navigator may
require several minutes, therefore, it may be useful to disable this option when
doing development work that requires frequent restarts of the service.
Similar to the Tree Query Menu feature, this option refreshes the Query Builder
page of published databases every time the WEB service is started.
Display c+d
When this option is enabled, all BOARD web queries display the code and the
description of any entity member, overriding the setup defined in the database.
27
It is recommended that you always enable this option because it grants complete
robustness to all features, even in cases where some entity occurrences have
duplicate names.
HTML Max Kbytes
Response Interval
Sets the rate at which the availability of the requested report is performed.
When a user requests an analysis (i.e. clicks a report name), the server instantly
returns a ”Please wait message page, and forwards the users request
to a BoardServer. After the number of seconds set by the Response interval
parameter, the users browser will automatically reconnect to the BoardMaster
and check whether the requested analysis is ready. If the result is ready then it is
returned to the user otherwise a new ”please wait message is returned
and a new connection will again be made after the interval has elapsed. This
technique allows for the handling of large amounts of simultaneous users by
minimizing the bandwidth and the BoardMasters resources needed by each
individual user.
This parameter should be calibrated depending on the number of simultaneous
users and the servers performance. For small to medium installations with up to
100~200 users set the interval in the range of 1 to 3. For larger installations with
hundreds of users, set the value in the range of 3 to 5.
Max Queue
Click Expires
Security
28
Minimal required time between two mouse clicks from the same user. This
feature prevents generating worthless workload on the server caused by a single
user clicking repeatedly without waiting for the response from the first click.
The Security tab allows is used to define user accounts and security privileges for users accessing the
Web and CMS services.
Access to this area can be password protected. To set a password, click the
the top left and set your password.
icon located at
It is possible to define a set of privileges and settings and save it as a User Group. When creating a
user account, it is possible to define the individual user rights or assign the account to a User Group
from which it will inherit all settings.
An account may belong to a single User Group (one only) or to none.
Related Topics
How to create a user account
How to create a user group
29
User Group
CMS
Enable the Allow Access checkbox if you want to allow the user to connect to
BoardMaster using a BoardClient (i.e. using the CMS service).
Assign License: Choose this option when the user doesnt have a standalone
license on his computer and a CMS-Contemporary Users license is installed on
the BoardMaster server.
Authorized Visitor: Choose this option if the user has a standalone license
installed on the computer running BoardClient.
License: Select the license type to assign to the user.
Note! When the user has a StandAlone license, this option allows you to demote
the license level. For example, selecting Lite license grants the rights of a Lite
license even if the user has a higher license such as Full standalone.
30
WEB
Enable the Allow Access checkbox if you want to allow the user to connect
using an Internet browser (i.e. using the WEB service). This checkbox can only
be enabled if an E-Server license is available on the BoardMaster.
Query builder provides access to the report builder page, which allows changing
the layout of a report or creating new ones from scratch.
Allow upload grants rights to save new reports or change existing reports. This
option should only be enabled if Query builder access is enabled.
Personal folder this option creates a personal reports folder that can only be
accessed by the user.
Select icon this option provides access to the Select function.
Capsules Folders
This group of settings allows you to define which Capsules a user may view. With
regards to confidentiality, we can identify three types of Capsules,
public Capsules that can be viewed by all Board users;
group Capsules, restricted to a particular user group such as a company
department or a project team and
private Capsules, these are users personal Capsules.
Note that the Capsule in itself does not contain any data but only analyses
definitions, which, when opened, will be populated with data filtered on the users
database security profile. The database security profile defines what portion of a
cube the user may view &endash; for example with regards to a sales cube, a
user may be allowed to view it entirely or have access partially restricted to a
state or a specific product group. A public Capsule may for example contain
some reports and key performance indicators that every Board user is able to
monitor (such as actual sales versus sales budget) but each user will actually be
looking at its own sales figures and its own performance indicators. A Capsule is
therefore public because it provides all users with the same evaluation criteria
and analysis methodology but not necessarily the same data.
Organizing Capsules into directories and sub-directories, then defining who can
view which folders, is a simple way of managing Capsules access. In all Board
installations there is always a default Capsules folder called Main, generally used
as the public Capsules folder. For each user group and for each individual user,
create a folder, using for example, the group name or the user name to store the
group Capsules and the private users Capsules. For example, if some Capsules
should only be available to the finance department users, create a directory on
the server where these capsules will be stored, then only grant access to this
folder to the finance department users (see below how to grant access to a
Capsules folder).
Allow access to local Capsules folder: grants access to Capsules located in
the Main folder, which, by default, is the directory
c:\Board\Capsules.
Allow Access to All folders: grants access to all existing Capsule folders.
Allow Access to Listed Folders: This option allows you to explicitly define the
names of Capsule folders that you want the user to be granted access to. The
folders list should be typed in the table just below, using the folders alias. For
example, to include the directory:
c:\App\Board\Finance\Capsules\ for which the alias Finance
defined, type Finance.
was
For details on what constitutes a folder alias and how to define it, refer to the
31
In the example above, users of this group will be assigned the security profile
named AREA1 for all databases except when accessing the databases named
Sales, Costs and Production for which the security profiles are ALL, PCENTER A
and GROUP34.
32
User Name
User PW
User Group
If the account privileges should be inherited from a previously defined user group,
select the User Group from the list box.
A user may be included in a single User Group only. When a User Group is
selected, all settings are inherited from the group. Changes made to the User
Group settings are inherited by all users in the group.
Other settings are identical to the User Group definition window.
In this example the following accounts are defined: 1 user with FULL license rights, 2 users with USER
license rights and 4 users with Web access. The BoardMaster has the following Contemporary User
licenses installed: 1 Full, 5 User, 10 Lite+, 10 Lite, and 25 Web users.
Contemporary Users displays the number of defined users (first column) and the maximum number
of contemporary users (second column) for each license type.
As previously discussed, there are two types of BoardClient users:
Users with a StandAlone license, defined as ”Authorized Visitor
Users that request a license from the BoardMaster at log-on, defined as ”Assign License. In
the latter case, a Contemporary User license must be installed on the server.
Given these two user types, the number in the first column may be higher than the number in the
second column. For example, if there are 20 users with StandAlone licenses and the BoardMaster has
3 Contemporary User licenses installed. You may define 25 accounts, where 20 are
”Authorized visitors and 5 ”Assign license, of these 5 only 3 may work
simultaneously.
Named Users displays the number of accounts with Web access (in the first column) and the
maximum number of Web users available (in the second column).
Monitor
34
Active Users window: displays the user name, IP address and connection status of the users
currently connected to the BoardMaster. When a user logs on, he/she is assigned to a slot. The
subsequent users requests (such as reports, or any other interaction with a database) are forwarded
to a BoardServer and identified by the users slot number.
Active Servers window: displays the BoardServers sessions which are running; the slot number is
shown while the BoardServer is executing a request for the user connected that slot. When
BoardServer is idle, the slot number field is cleared. The database field indicates which database the
BoardServer is working on or has last worked on.
Licenses and accounts window: displays the number of connected users by license type (Lic
column), the maximum number of Concurrent User licenses installed on the BoardMaster (Max
column) and the number of users connected as visitors (Vis column).
HTTP Traffic log window shows the http service log.
Options Tab
The options Tab contains a log windows used for troubleshooting and some self-recovery parameters.
The BoardMaster AutoResume feature allows the system to identify and fix cases of processes
which are not responding correctly to the BoardMaster. This feature allows you to eliminate or reduce
BoardMaster service down-time. The AutoResume feature is a watchdog that monitors the
BoardServers activity. When a BoardServer doesn't respond in a timely fashion, the BoardMaster kills
the dummy process and restores a fresh BoardServer process.
The CMS Log window (click the check box to start logging) traces all TCP socket activity going on
between the BoardClient<>BoardMaster and between BoardMaster<>BoardServer. This function can
be used to troubleshoot systems experiencing connection problems.
35
AutoResume parameters
Server Not Responding
Batch Processing
Maximum number of seconds that the BoardMaster waits for the "endof-stream" data once the transmission of a data stream is pending (or
in progress). This setting allows to resolve cases of lost data packets
due to unreliable data transmissions.
36
37
Unicode
Activate this option when you want the databases and Capsules to manage
double-byte languages such as Korean, Japanese, Chinese, Russian,
Greek etc.
This feature allows you to define directories which hold different Capsules
to the default Board\Capsules directory and assign an alias (i.e. a short
name) to the directory.
Type the full name of the directory in the More Capsule Folder [Path] field.
Type a short name in the Alias [Short-name] field as illustrated
This feature allows you to define directories which hold different Board
databases to the default Board\Database directory and assign an alias
(i.e. a short name) to the directory.
Type the full name of the directory in the More Database Folder [Path] field.
Type a short name in the Alias [Short-name] field as illustrated
Monitored Q Path
38
Port
Note! After changing any of the parameters, close and restart the BoardServer: in case
of a Standalone installation, closing your BoardClient the restarting it will automatically
close and restart the Boardserver; in case of CMS installations, stop and restart the
BoardMaster CMS service (click the Stop/Start buttons).
2.
Run the BoardServerSetup.exe program: this will install BoardServer in the same directory. If
prompted, shutdown and restart your computer. Note that this setup program will also install
BoardMaster.exe but this program in not needed in a standalone installation, you may delete it
if desired.
3.
Install and certify your Board StandAlone license; the KeyManager program (which is installed
by the BoardServerSetup program) allows you to create and certify your license. Refer to the
Licensing chapter for detailed instructions on the license certification procedure.
4.
Run your BoardClient program: from Windows Start menu, select Programs then Board M.I.
then click the BoardClient icon.
5.
The BoardClient setup window will open automatically (this only happens the first time
BoardClient is launched). You can accept all default values since in a standalone installation the
system is able to detect the correct settings to run. If you wish to accept the default settings click
the OK button to close this window.
39
Note! the first time BoardServer runs, it will create a c:\Board directory which
contains the Capsules and Database subfolders where capsules and databases are
stored. If you wish to move this directory, open the BoardServer program, click the
Setup button, then type the new location in the ”Local Board Location field. To
close this setup window click the OK button.
40
The server computer is now fully configured, BoardMaster is running and ready to accept connections
from users.
Installing the client:
Carry out the following steps on the server computer
1. Run the BoardClientSetup.exe program: this will install BoardClient on c:\Board.sys.
2. If you want to install a standalone license on the PC, create it and certify it; otherwise, if the
BoardMaster has a CMS-ContemporaryUser license, go to the following step. The KeyManager
program allows you to create and certify the standalone license. Refer to the Licensing chapter for
detailed instructions on the license certification procedure.
3. Run your BoardClient program: from Windows Start menu, select Programs then Board M.I. then
click the BoardClient icon.
4. The BoardClient setup window will open automatically (this only happens the first time BoardClient is
launched). Set the following parameters:
User Name field: type an existing user account (previously defined when configuring the
BoardMaster).
Host IP Address: type the IP address or host name of the computer where BoardMaster was
installed. Note that the system shows three predefined hosts, named Local Server, Local Master and
Demo Site. Delete these addresses if you want the user to connect to your BoardMaster installation
only. Connecting to Local Server and Local Master is only possible if a StandAlone license is installed.
It is therefore recommended that you delete these definitions if the user does not have a StandAlone
license.
41
Note! When configuring BoardClient (step 6), it is possible to store the users password,
however, if you need access to your Board applications to be secure, it is recommended
that you leave the password field blank and enable the ”Ask Password at Logon
option.
42
Chapter 4 Licenses
Licenses overview
The installation and activation of the Board license is a part of the software installation process. Two
license types exist,
the stand-alone license which must be installed on the client computer where BoardClient is
installed (client side license). This license type enables Board to run on a single computer only,
one license per computer is needed. This license is required for stand-alone architectures for
example for Board developers that need to work locally on their PC.
the CMS license which must be installed on the server where the BoardMaster is installed
(server side license). The CMS license, generally for servers, can enable a combination of
BoardClient users and Internet browser users. The Internet browser users licenses (called EServer users) follow a ”named user model meaning that you must purchase one license
for each user or person that will be using the software. The BoardClient users licenses can be of
type
CMS Concurrent Users, meaning that the BoardMaster counts the number of
BoardClient users that have logged on and allows only a certain number of
users to work simultaneously. For example a 50 concurrent users license
allows defining more than 50 user accounts and installing the BoardClient
software on more than 50 PCs but only up to 10 users can work
simultaneously. When the limit is reached, if an additional user attempts to logon, he receives the message ”Too many users and must wait until
one of the active users logs-off.
CMS Named users, meaning that the BoardMaster only allows defining a
number of user accounts equal to the number of purchased licenses.
In general, a combination of licenses is needed: some stand-alone licenses for the Board
administrators and for some key users; some CMS Contemporary Users or Named Users licenses for
the majority of BoardClient users and lastly some E-Server licenses for those accessing Board through
an Internet browser.
Different license levels exist, regardless of the license type (standalone or CMS) each providing a
different level of functionality:
Full : this is the highest level license, it allows you to create and edit Board databases a
capsules without restrictions. It is intended for Board administrators, developers and
power users.
User : this license provides unrestricted access to Capsules both for navigation and for
development purposes but does not allow to access any database design feature. This
license is for power users that do not need to modify the design of Board databases.
Lite Plus : this license provides access to Capsule navigation features but does not
allow you to design or edit a Capsule; access to the design mode is restricted. It is
intended for users that only need to open existing Capsules, including budgeting and
simulation applications, that have been designed for them by a user who has a Full or
User license.
Lite : this license provides the same functions as the Lite Plus license with the
exception that all data-entry features are disabled. It is essentially a ”read-only
license suitable for users that need to navigate existing Capsules with reports, charts or
any other data-presentation object but who do not need to enter data on the Board
database. This license does not permits you to run budgeting, forecasting or other
simulation Capsule requiring data-entry.
43
Create the half-KEY: this is achieved by running the KeyManager program on the computer
where the license is to be activated. The KeyManager prompts you for some information such
as the customer name, customer contract code and license type then creates the half-KEY
file.
2.
Send the half-KEY to the Boards web site: this is achieved by accessing a specific area of
Boards web site or alternatively by the KeyManager program.
3.
Receive the certified KEY: after processing the half-KEY and if the requested licenses are
available, the certified KEY file is immediately returned via e-mail.
4.
Place the certified KEY file in the directory where it was created in step 1.
Note!
Before reading this chapter read Chapter 1 - Welcome on Board, for a general introduction to
Capsules. Refer to Chapter 6 &endash; Database Design to familiarize with multidimensional
database concepts and the specific terminology.
Prerequisites
Before starting the license installation process, go through the following checklist:
You have already decided on your installation architecture (stand-alone, or CMS) and have
installed the appropriate software BoardClient and/or BoardMaster.
You know your companys contract code: when you purchase Board licenses, Orenburg or your
Board dealer provide you with a contract code which is a 7 character code (a combination of
letters and numbers).
You have access to e-mails of an authorized e-mail address: when you ordered your Board
licenses, you have provided Orenburg or your Board dealer with at least one e-mail address.
This e-mail address is registered on Boards web site as being an authorized e-mail for your
contract code. Certified KEY files are sent to authorized e-mail addresses only.
You have your username and password to access Boards web site support area. To obtain a
login to Boards web site, go to the support area on Boards web site at
http://www.board.com/lang_int/support_customers.htm, then click the link ”Click here to
register.
You have full access to the computer where you want the licence to be installed.
You have access to the Internet.
44
Chapter 4 Licenses
Launch the Key Manager program: click the shortcut located in ”Board M.I. group on
your Windows Start menu. Alternately, double click the program file KeyManager.exe.
located in your Board installation directory, usually c:\Board.sys .
2.
3.
4.
After clicking OK, a file named [User ID].key (where [User ID] is the name typed in the User ID
field) is created in the same directory where KeyManager.exe is located (usually c:\Board.sys).
This is the half-KEY which needs to be certified
This file needs to be saved to the same directory where BoardClient.exe and BoardMaster.exe are
located (i.e. c:\BoardSys). Note: You can only have 1 .KEY file in this directory.
46
Chapter 4 Licenses
Click the Browse button and locate your Key file, then click Send.
Wait until the confirmation message indicating the e-mail address where the certified KEY was sent is
displayed.
The following illustration is an example of confirmation message, indicating that the certified Key was
sent to johnsmith@orenburg.com.
Important! After viewing the confirmation message, delete the half-KEY file from your computer.
You can now open your e-mail program to receive the e-mail message with the certified KEY file.
If the certification is not successful, other messages will appear.
The following message indicates that you have sent the wrong file.
Click back, then click on Browser again and make sure you select your half-KEY file which has the
extension KEY.
The following message means that you typed a wrong Contract Code.
47
In this case recreate a new half-KEY and verify that your contract code information is correctly typed.
Some e-mail systems can alter the size of the certified KEY file while scanning incoming
messages. This causes the Key file to become unusable. The Key file will not be
recognized as being a valid license if its size is different from 1,400 bytes. When you
receive your certified KEY file, always verify that the file size is exactly 1400 bytes. Note
that it is not sufficient to view the file size in Kbytes because it is rounded, you must look
at the file properties to know the exact size in bytes.
You should now verify that the certified KEY is correctly installed and recognized by Board.
If the KEY file is a stand-alone license, launch your BoardClient program. When the KEY is installed
correctly, your companys name should appear in the message area as in the following illustration,
When the Key is not recognized to be a valid stand-alone license, then the text OnlineLicense
appears.
If the KEY file is a CMS license, launch the BoardMaster program. If the four configuration tabs are
displayed (CMS, Web, Security and Monitor) then the certified license is correctly installed. If the
BoardMaster program only displays the Security and Monitor tabs, then the license is not recognized
to be a valid CMS license.
Chapter 4 Licenses
run the Uninstall procedure (detailed hereafter) on the old computer
then install the license on the new computer.
Uninstalling a license
You should only uninstall a license if
You wish to uninstall the BOARD program and you will not need to use it on this computer in the
future, if you are exchanging it for a new computer, for example.
You need to carry out some sort of procedure that will change the hard-disk serial number. For
example, if you need to format the computers hard-disk or you are changing hard-disk,
redefining the partitions or changing the file system.
To uninstall a license,
1.
2.
Select the Uninstall option from the pull-down list located above the OK button.
3.
Click the OK button and confirm. This step will update your KEY file.
4.
Send the KEY file to Boards web site, through the licensing area. Follow the procedure
described in section Sending the half-Key for certification. This step is necessary to inform
Orenburg that you have uninstalled a KEY file and will consequently increase your licenses
credit.
5.
Shortly after this, you will receive an e-mail confirming that your uninstalled license has been
correctly received and processed.
You have now completed the license uninstall procedure. You may install the freed-up licenses on a
new computer following the standard installation procedure.
Upgrading a license
Upgrading a stand-alone license means increasing the license level. A Lite license can be upgraded to
Lite Plus, User or Full license. A lite Plus license can be upgraded to a User or Full license. A User
license can be upgraded to a Full license.
Upgrading a CMS license means increasing the number of users for any of the license levels. For
example, a CMS license for 1 Full, 10 User, 20 Lite can be upgraded to a CMS license for 1 Full, 12
User, 5 Lite plus, 30 Lite and 25 E-Server users.
Changing a stand-alone license into a CMS license is not an upgrade, it is a license type change. You
should uninstall the stand-alone license (follow the Uninstall instructions), then install a CMS license or
vice-versa.
To upgrade a license,
1.
2.
If upgrading a stand-alone license, select the new license from the licenses drop-down list. If
upgrading a CMS license, increase th number of users currently indicated.
3.
4.
Click the OK button. This step will create a new half- KEY file.
5.
Send the half-KEY file to Boards web site, through the licensing area. Follow the procedure
described in section Sending the half-Key for certification.
6.
Shortly after this, you will receive an e-mail with the new certified KEY.
7.
Delete the old certified KEY then detach the new certified KEY and place it in the Board.Sys
directory.
49
Reinstalling a license
If you have erroneously run the license Uninstall procedure on a computer and wish to re-install a
license (on the same computer), follow the standard installation instructions however, when creating
the half-KEY, select the Reinstall option from the drop-down list located above the OK button. Note
that you should run the re-install process as it will fail if all its steps of the Uninstall procedure were not
completed.
Important notes
You can recognize a half-Key from a certified KEY by looking at the file size. Using Windows Explorer,
right click on the KEY file and select Properties. The file size is displayed in bytes. The half-KEY files
are 1,201 bytes in size. The certified KEY files are 1,600 bytes in size.
Some e-mail systems can alter the size of the certified KEY file while scanning incoming messages.
This causes the Key file to become unusable. The Key file will not be recognized as being a valid
license if its size is anything different from 1,600 bytes. When you receive your certified KEY file,
always verify that the file size is exactly 1600 bytes. Note that it is not sufficient to view the file size in
Kbytes because this is a rounded figure, you must look at the file properties to know the exact size in
bytes.
If a certified Key file gets corrupted, it is possible to re-run the procedure to create the Key file on the
same computer that it was previously installed on and submit it for certification. The number of license
credits is not decreased. When two identical Key files are submitted for certification, the license credit
is only decreased once.
The procedure type you perform (install, uninstall, reinstall) is recorded in the KEY file on the client
computer and on Boards web site where a licenses management system is running. This system will
debit or credit your account depending on what type of action you select. If you try to perform two
identical installations on the same machine, your account will only be debited once because the
system recognizes that only one of these requests is valid. If you successfully complete an uninstall,
your account will be credited for the license type which you uninstalled. Similarly, if you successfully
complete an upgrade, you will be credited for the license type previously registered, and debited for
the upgraded license.
50
The BoardMaster plays a central role in the client/server architecture. It is the access point to which
end-users connect using either BoardClient or an Internet browser. The BoardMaster performs enduser authentication, receives the users requests (for report, charts, analyses) and dispatches them to
the BoardServers that will carry out the processing on the multidimensional databases.
BoardMaster role and features
-
Runs the CMS service (based on the ROAR protocol) which allows BoardClient users to
connect.
Runs the WEB service (based on the standard HTTP or HTTPS protocols), which provides
access through an Internet browser.
Manages user accounts: performs the user authentication and applies security privileges and
restrictions.
Manages the incoming requests queue and optimizes the assignment of tasks to BoardServer.
The queue optimization algorithm analyses the incoming request and dispatches the task to a
BoardServer session, minimizing the number of context-switches required.
Manages CMS licenses. For named user licenses, licenses are controlled by allowing you to
define a fixed number of accounts only. For concurrent-users licenses, the BoardMaster counts
the number of simultaneous users and permits or denies access accordingly.
51
Note that you must have administrators privileges to successfully install a Windows system service.
The BoardMaster service is installed with the following options:
Startup type = Manual
LogOn as = LocalSystem
To change settings use Windows System Management Console.
If the BoardMaster program is launched while the BoardMaster service is running, only two tabs are
shown; the Security tab, allowing to create and edit user accounts and the Monitor tab which displays
BoardMaster and BoardServers activity. To access and modify the parameters located on the CMS
and Web tabs, stop the Board Master service then run BoardMaster.
When BoardMaster is installed as a Windows system service, open Windows Computer Management
Console, select the BoardMaster service then click the ”start service icon
52
53
The database log file contains information on database design and database update actions such as:
definition of new entites, input of new entity occurrances definition of new InfoCubes, execution of the
database, dBVerify function, execution of datreader and datatflow procedures.
The database log file can be opened with a text editor or using BoardClient, clicking the Log File icon.
Note that it is possible to edit the log file (adding comments and notes); changes can be saved when
closing the BoardClient log viewer window.
Auto num.
Description
Incremental counter of BoardServers action number.
Note! It is not a unique record identifier.
54
11 &endash; 25
profile
36 &endash; 1
ro/rw access
37 &endash; 5
Ununsed
42 &endash; 25
BdB name
67 &endash; 100
BdB path
167 &endash; 25
InfoCube
192 &endash; 5
Version
InfoCube version.
197 &endash; 8
Date
205 &endash; 6
Time
211 &endash; 6
Unused
217 &endash; 1
Data access
218 &endash; 1
Layout id
219 &endash; 3
Unused
221 &endash;10
elapsed time
Record number
12 &endash; 8
21 &endash; 8
30 &endash; 30
User name.
60 &endash; 20
80 &endash; 40
120 &endash; 30
150 &endash; 20
170 &endash; 1
171 &endash; 1
172 &endash; 2
This field allows you to monitor how many times the Select
function is used. The value is set to ”1 when the
Select function is used, otherwise it is set to ”0
.
56
173 &endash; 1
This field allows you to monitor how many times the Drilldown function is used. The value is set to ”1 when
the Drill-down function is used, otherwise it is set
to”0.
174 &endash;1
This field allows you to monitor how many times the Master
function is used. The value is set to ”1 when the
user clicks on a master report link, otherwise it is set
to”0.
175 &endash; 1
This field allows you to monitor how many times the paging
function is used. The value is set to ”1 when a
report is regenerated after the user changes a page-by
selection, otherwise it is set to”0.
176 &endash; 1
This field allows you to monitor how many times the query
builder is used. The value is set to ”1 when the user
accesses the query builder (Layout) page. otherwise it is set
to”0.
181 &endash; 9
191 &endash; 9
201 &endash; 50
Folder and file name of the requested web query without the
TXT extension.
12 &endash; 8
Tab separator
57
Requirements analysis
design
back (and restart from top)
implementation
delivery
feed-
59
60
Some database design functions can be used through the DB Designer environment, which provides
a graphical environment for creating entities, hierarchies and InfoCubes. To access this environment
click the DB Designer icon.
Note, before trying to access a database design function, make sure you first open the desired
database by clicking on the database name as shown,
Relationships
InfoCubes
Rules
Define calculation rules on entity members, usually for profit and loss or
balance sheet entities where an entity member is calculated applying a
formula that refers to other members of the same entity.
Data Reader
Batch Reader
Security
Db Verify
Log File
Warning! Before copying or making a backup of a database directory, make sure that
all BoardServers are closed as these processes could keep some database files open and
interfere with the copy or backup process.
Warning! When restoring a backup copy of a database, firstly delete the existing
database directory (and all its contents), then restore the backup copy. Failing to do so
may create an inconsistent set of files; only files with the same name will be overwritten
but those files which did not exist when the database was backed-up will not be
removed.
Warning! By changing the name of the database, any existing Capsule linked to that
database loses its links and will no longer function, however you may redefine the link to
the renamed database.
Time range
Time range
To access the time range function, select the Time Range icon
This function allows you to define and manage the database time entities. When a new database is
created, the Time range definition opens automatically.
The time range definition window is illustrated hereafter
63
64
Note that clearing the time range automatically clears the contents of all InfoCubes structured by any
time entity.
yy-YY
yyyy to YYYYY
F.Y. yy-YY
Warnings!
- This option can only be enabled on database created using version 5 (or later), it
cannot be enabled for databases created using version 4.x.
- When fiscal year is enabled, only three custom time entities can be used instead of
four.
When Fiscal Year is defined, users can apply the Yearly Cumulated Value function either based
on the Fiscal Year or on the standard calendar year as desired (a selection check-box automatically
appears next to the Yearly Cumulated Value function).
Using Quarters
Click the Quarter check-box.
If Fiscal Year is enabled, you may choose to refer to Fiscal Yearquarters, rather than stick to the
calendar year, by clicking the related check-box.
65
Fiscal year
Qnn of YYYY
No
”Q1 of 2004
&ldots;etc&ldots;
Q.nn yy-YY
Yes
”Q.4
03-04
&ldots;etc&ldots;
”Q2
of
”Q.1
2004
04-05
Using Weeks
Click the Weeks check-box;
select the first day of the week;
then select one of the four conventions that defines the first week of the year:
Jan 1st
The first week of the year is the first week that has at least
four days in the new year.
Note! Selecting this option, week starting on Monday
corresponds to the ISO 8601 standard, widely adopted in
Europe (see below details on the ISO standard).
The first week of the year is the first full week of the year.
B.Prev.version
Selecting one of the first three options, the week description can be customized using the variables nn
representing the week number and YY representing year.
Format definition examples
Format definition
Week nn/YYYY
W.nn of YY
Week number
Desc = Date
"week, calendar: A seven day period within a calendar year, starting on a Monday and identified by its
ordinal number within the year; the first calendar week of the year is the one that includes the first
Thursday of that year. In the Gregorian calendar, this is equivalent to the week which includes 4
January."
This can be implemented by applying these rules for Calendar weeks:
66
Using Day
To enable the Day entity, click the Day check-box found on the Time Range window.
To create a custom time entity, double click on the Entity field and type the entity name, then define
other parameters,
Code width
Desc width
Sort by
Default sort option. Click on the cell to set one of the three available
options:
[none] , displays occurrences in the order in which they are
created,
code : sorts the entity members according to the code field.
67
Default entity field visualized in reports. Click on the cell to set one
of three available options:
desc : displays the entity description field.
code : displays the entity code field.
c+d : displays both code and description fields.
68
To create a relationship, click on the child entity (the row header column, with gray background)
then select all parent entities.
For example, to define Season as being a parent of the month entity, click on the Month row header
then select Season as illustrated.
Note that all direct and indirect relationships must be defined. A direct relationship is a one-level
child parent relationship. For example Day Month is a direct relationship. An indirect relationship is
a child grand-parent relationship, for example day year..
Lets consider the previous example, you just added Season as a parent of the Month entity. If the Day
entity is enabled for this database then Month is a parent of the Day therefore you must define also
the indirect relationship Day Season.
The following window allows you to insert new occurrences and delete existing ones.
The white area allows you to type one or more new members; the new members are added only after
you press the OK button at the top.
The yellow area shows the list of current members; click the Delete button to remove a member.
Note that you can modify both code and description for an existing member.
Assigning relationships
Each member of the child entity must have a parent from the parent entity. For example, considering
the Month Year relationship, each month (Jan.04, Feb.04, etc) is related to a Year (2004, 2005 etc).
When there is a missing child parent relationship, the item in the child entity is called an orphan.
Relationships between the standard time entities are managed by Board, which grants integrity and
absence of orphans. When custom time entities are used, you must make sure that there are no
orphans for all existing child parent relationship.
Relationships between members of a child and parent entity can be assigned either manually, one by
one selecting for each child member its parent, or through a DataReader that reads a file containing
the child code parent code information. Refer to the DataReader section for more details on loading
relationships from an external file.
To assign a relationship manually, go to the relationships window
70
On the child entity row, click the name of the desired parent entity. For example, to assign
Month Season relationship, click Season on the Month row.
Clicking the entity opens a window listing all child entity members with the related parent in case a
relationship already exists.
Select the child member you wish to define a parent for. In the illustrated example, we click on May.04
to assign it to a season.
The members list of the parent entity is displayed. Choose the desired item.
Note! After manually assigning relationships, click the Scan button to verify that all
members of a child entity are assigned to a parent. The scan function highlights in red
entities that have undefined relationships (orphan items).
To browse a relationship, click the desired parent entity name: a window showing the child parent
items opens.
The following illustration shows the Quarter Fiscal Year relationship in analytical mode.
72
To view the relationship, click the desired parent entity name: the parent items and the number of
related items from the child entity are displayed.
The following illustration shows the Quarter Fiscal Year relationship in summarized mode.
Using the Default access mode you can select a parent item for all orphans of an entity (refer to
Assigning a relationships to all orphan items).
73
Click the desired parent entity then select the item that should be assigned as parent for all existing
orphans.
Entities
Basic concepts
An entity generally is a set of homogeneous items by which data can be viewed and summarized. For
example, a Customer entity holds the list of customers and allows you to view such things as the
sales amount by customer. Items of an entity are called entity members or occurrences. An entity can
be used as a dimension of an InfoCube. Relationships can be defined between two or more entities to
form a hierarchy.
An entity is made of two fields, a code part and a description part. The code is a unique value that
identifies an entity member; two entity members cannot share the same code.
When an entity is created, Board creates an internal unique identifier (UID) for that entity. The UID is
then used to refer to the entity. Reports, procedures, datareader protocols and other objects all refer to
the entity using its UID. As a consequence, changing the entity name does not affect existing
Capsules (and its reports and procedures) or other database objects. There is however an exception
to this rule. Board Web queries use the entity name to reference an entity. The entity name is stored in
the Query script file, therefore changing the name will affect existing web queries which use the entity.
The maximum number of entities that can be defined is 999. Note that the entity definition window is
initially limited to 51 lines, however whenever you define an entity near the end of the page, the
number of rows increases automatically.
The Entities function allows you to
Create, remove or rename an entity.
Add, edit and delete entity members.
Monitor entities saturation.
Monitor sparse structures size and define the sparse management method.
To access the Entity function, click the Entity icon
Creating an entity
To create an entity click on an empty row, type the name of the entity
Code width
Desc width
Sort by
Default sort option. Click on the cell to set one of the three available
options:
[none] , displays occurrences in the order in which they are
created,
code : sorts the entity members according to the code field.
desc : sorts the entity members according to the description field.
Sorting is always in ascending order. Both code and description are
text fields therefore sorted according to the character string.
Display
Default entity field visualized in reports. Click on the cell to set one
of three available options:
desc : displays the entity description field.
code : displays the entity code field.
c+d : displays both code and description fields.
User view
Disabling this option excludes the entity from the database cache
(therefore reducing its size) but users will not be able to access the
entity in the Select window or set the entity in the Dynabar. Only
consider disabling it if you need to optimize the database for users
accessing through a low bandwidth connection.
By default, this option is enabled.
Note! Refer to section Understanding the database
caching for details on the purpose of this property.
Tip! The position where you define an entity is not relevant however it is good practice to define
entities belonging to the same hierarchy on continuous rows, leaving some blank rows between two
groups and defining stand alone entities (those not belonging to a hierarchy) at the bottom as
illustrated,
75
Desc width
Changing the max item number requires you to clear the entity.
Sort by
Display
User view
Deleting an entity
To delete an entity click the Delete button located on the entity row as illustrated
The ItemNr field shows the number of items currently contained in the entity. Deleting an entity clears
its contents too.
When an entity is deleted, all InfoCube versions structured by that entity are also removed. A red tick
to the right of the Delete button (see illustration below) indicates the presence of data in an InfoCube
version structured by that entity; deleting that entity also deletes the InfoCube version thus the data.
78
Note that there are several ways of loading members into an entity
79
Note! When an entity member is created, Board creates an internal unique identifier
(UID), which is used to reference it. All selections (stored into Capsules, procedures, and
security) use the entity members UID therefore changing the code or the description
does not affect existing Capsules (and its reports and procedures) and security profiles.
Warning! Board Web queries use the entity members code to reference an entity
occurrence. The code is stored in the Query script as a text string, therefore changing it
will affect existing web queries which have a reference to it.
Note! Deleting an occurrence does not reduce the saturation level of an entity. The
saturation of an entity is determined by the number of occurrences created. For example,
inserting and deleting 10 items for 5 times causes the creation of 50 items; if the entitys
max item number is of 100 then the saturation is 50%. The saturation is reset only when
the entity is cleared using the Entity / Clear function.
Clicking the Clear All button, deletes all entity members for all entities.
When an entity is cleared, all InfoCube versions structured by that entity are also cleared. A red tick to
the right of the Delete button (see illustration below) indicates the presence of data in an InfoCube
version structured by that entity; clearing that entity clears that version.
80
Relationships
Basic concepts
In a Board database relationships are always strictly hierarchical: a relationship defines an n-to-1
relationship between two entities that we therefore refer to as the parent entity and the child entity. For
example, State and City clearly are parent and child entities: a city can only be in one state and a
state includes several cities.
Entities and hierarchies provide views on InfoCubes (usually numerical data) at various aggregation
levels, for example, Sales by State or by City. Two entities, a parent and a child are also often
referred to as less aggregate or more aggregate entities: a view at a parent entity level is the
aggregation of the data from the child entity level.
Board supports multiple parallel hierarchies meaning that an entity can have multiple roll-up paths. For
example, the Customer entity could roll-up into the City and State (this is the first branch) and
independently roll-up into Salesman and Area Manager entities (this is another branch) and into
Channel (this is a third branch). Hierarchies are also referred to as trees. The following illustration
shows a Customer hierarchy made of three parallel branches.
Building the hierarchies is one of the key steps of building the multidimensional model. The hierarchies
must provide a truthful representation of the business model or the organization you are modeling. A
relationship between two entities should only be defined if there is an organizational rule or some kind
of constraint that enforces it.If we look at the State and City entities, it appears quite obvious that a
hierarchical relationship should be defined between the most aggregate, State (the parent) and the
less aggregate City entity (the child). Sometimes the choice is not so obvious; lets consider for
example the entities Customer and Salesman. Defining the hierarchical relationship
81
Defining a relationship
To create a relationship, open the relationships definition window, click on the child entity on the row
header column (with gray background), then select the parent entity or entities.
For example, to define City as being a parent of the Customer entity, click on the Customer row
then select City as illustrated.
Note that direct and indirect relationships must be defined. A direct relationship is a one-level
child parent relationship. For example Customer City is a direct relationship. An indirect
relationship is a child grand-parent relationship. For example Customer State is an indirect
relationship through City State.
Lets consider the previous example, if you define Customer City and City State, then the
indirect relationship Customer State must also be defined .
82
Warning!
Do not define cycles in your hierarchies: two entities that are not hierarchically related cannot have the
same parent entity. An example is shown in the following illustration.
Removing a relationship
To remove a relationship definition, click on the child entity on the row header column (with gray
background), then de-select the parent entity you wish to remove.
Assigning a relationship
Each member of a child entity must have a parent. For example, considering the Customer City
relationship, each Customer must be related to a City. When there is a missing child parent
relationship, the item in the child entity is called an orphan. Relationships are used when data is
aggregated (rolled-up) and orphans can cause data inconsistencies. For example, lets consider a
Sales Amount InfoCube, structured by Customer. If a customer is not related to any city, then when
this InfoCube is aggregated by city the data of the orphan customer does not roll-up into any city
giving an incomplete answer. It is therefore important to make sure that there are no orphans. Refer to
following paragraphs for instructions on how to identify and remove orphans.
Relationships can be assigned either manually, one by one selecting for each child member its parent,
or through a DataReader that reads a file containing child code and parent code information. Refer to
the DataReader section for more details on loading relationships from an external data source.
To assign a relationship manually, go to the relationships window,
83
Clicking the entity opens a window listing all child entity members with the related parent.
Select the child member you wish to define a parent for.
84
To browse a relationship, click the desired parent entity name: a window showing the child parent
items opens.
The following illustration shows the City State relationship in analytical mode.
To view the relationship, click the desired parent entity name: the parent items and the number of
related items from the child entity are displayed.
The following illustration shows the City State relationship in summarized mode.
85
Using the Default access mode you can select a parent item for all orphans of an entity (refer to
Assigning a relationships to all orphan items).
Click the desired parent entity then select the item that you want to be assigned as parent for all
existing orphans.
Each row indicates an indirect relationship showing the less aggregate, the more aggregate and the
middle entities (in the Through column).
To run a normalization, click the Go button on the desired line as illustrated.
To run normalization on several indirect relationships, select the Do tick-box then press the Go button
at the top.
To save the selected normalization options for re-running at a later time or for launching the
normalization from a procedure, click the Save Setup button.
Note that for an indirect relationship of three-levels (or more) you must select the middle entity by
clicking
the
Through
cell.
For
example,
considering
a
four
levels
hierarchy
Customer City State Country, the indirect relationship Customer Country can be
normalized through City Country or through State Country.
Note! The normalize function can be launched from a procedure using the Normalize
option of the Data Read action.
InfoCubes
Basic concepts
An InfoCube is the element of Boards multidimensional database that allows storing and retrieving
data using the multidimensional metaphor. An InfoCube has dimensions, providing different
perspectives on data. The dimensions of an InfoCube are entities or hierarchies. The intersection of
87
The number of combinations of the sparse structure is shown in the Item Nr column.
Clicking on a sparse structure displays the list of InfoCubes versions that utilize the structure and the
density. The following illustration shows the InfoCube versions using the Product-Customer sparse
structure.
89
Clearing all versions using a sparse structure clears the sparse structure too and resets the number of
sparse combinations to zero.
90
91
92
Creating an InfoCube
To create an InfoCube, open the InfoCube window, click on an empty row,
then type the name of the InfoCube and
select the data type as illustrated.
Click the Structure button and select the InfoCubes dimensions. The structure selection
window shows all stand-alone entities and entities at the base of hierarchies.
Define one (or more) InfoCube physical versions. Usually the most detailed version of the
InfoCube is defined in the first column. The most detailed version of the InfoCube is also
called the primary version. To add entities to a version click the version-entity intersection cell.
For example to define a version by Month-Customer-Product, click as illustrated.
93
Define the sparse structure as appropriate. Refer to the Sparse Structure paragraph for
guidelines. To define a sparse structure, click twice on the cells of the entities you want
include in the sparse structure. The second click converts the O into an X, while a third click
clears the cell., The following illustration shows how to define the sparse structure made up of
Customer-Product entities,
For MXC InfoCubes, you must declare the entity being counted by clicking on the entity
name; the symbol <> appears next to the entitys name. If the entity you want to count is not
explicitly declared, Board counts the entity with the greatest MaxItemNumber.
Warnings!
InfoCubes of type MXC, date and text can only have one version.
It is possible to define an InfoCube which is only structured by a time entity (single
dimension InfoCube), for example Month or Year, however all time functions (Previous
Period, Yearly Cumulated Value etc.), including the Data Readers Replace function are
ignored on these InfoCubes. For this reason, it is recommended that InfoCubes with the
time dimension have at least another dimension.
When an InfoCube is structured by a given time entity, using the same time entity for
any additional version defined is recommended. For example, consider an InfoCube
which is structured by Day (and some other entities). If multiple versions need to be
created, then they must all be structured by Day (not Month or Year); all versions use a
single entity as time dimension.
94
Tip! Hidden InfoCubes: if the first letter of an InfoCube name is the underscore character
”_ then the InfoCube is hidden; users cant view it when configuring a report,
chart or other data presentation objects. The InfoCube is only visible in the procedures
environment.
then right-click on the InfoCube to copy and, while keeping the mouse button pressed, drag and drop
the cursor to a new line where the new InfoCube should be created. Release the mouse button and
type the new InfoCube name when prompted.
A new InfoCube, with the same versions of the copied InfoCube, is created.
The Copy structure and Contents option creates a new InfoCube with the same structure and data
contained in an existing InfoCube.
Moving an InfoCube
When configuring a Layout, end-users select InfoCubes from a list. InfoCubes are listed in the order
they appear in the InfoCubes definition window (from top down). It is therefore recommended to place
the most commonly used InfoCubes at the top.
To move an InfoCube,
open the InfoCube window then select the Move option from the drop-down list
then right-click on the InfoCube to move and, while keeping the mouse button pressed, drag and drop
the InfoCube to a new line.
95
Note that the newly created versions dont contain data. Use the Align function to feed the new
versions.
To verify versions alignment, click the Verify button. The CheckSum column shows the grand total
value of each version, calculated summing up the values from all the cells.. A version is inconsistent
96
Clearing an InfoCube
To clear data contained in an InfoCube,
open the InfoCube window, then click the Clear button on the InfoCube definition row as illustrated.
Deleting an InfoCube
To delete an InfoCube,
open the InfoCube window, then click the Delete button on the InfoCube definition row as illustrated.
97
Left-click on an entity to view its members. Right-click on an entity to access the entity definition
properties.
Left-click on a relationship to view the parent-child relationships. Right-click to select the relationships
view mode (analytical, summarized, residual, default).
To add a new entity to a hierarchy, select the hierarchy from the drop-down list.
To create new InfoCubes or view existing ones, select All Trees from the tree selection list then click
the InfoCubes icon.
When the InfoCube icon is clicked, the workspace shows all entities: the time entities are on the top
left, the stand alone entities on the bottom left and the hierarchies are on the right.
98
99
To define a version, click on the white circle then draw a line to each of the dimension entities
as illustrated.
100
to define a sparse structure, click on the circle located on the dimension line as illustrated.
101
DB Designer Options
The Options window is show in the following illustration
Entities
Cut-Off : sets the entity cut-off parameter, refer to Entities for more
details.
Relationships
Click Scan to run the scan function. Relationships where orphans are
found become red.
Click Normalize to access the Normalize function.
Data Reader
Basic concepts
The Data Reader allows you to import data from text files or an ODBC source into Board entities,
relationships and InfoCubes. A Data Reader protocol defines how the external data should be
imported into Board database entities and InfoCubes; i.e. it defines what fields of a relational database
table (or file) should be imported into what entities and InfoCubes.
A Data Reader protocol can include a set of transformation formulas and validation rules to apply to
incoming data. These rules are defined using the ETL function.
The Data Reader also allows you to configure drill-through protocols. The drill-through function allows
end-users to drill from a Board report through to a relational database table. A drill-through protocol
102
Width
Format
Example
Day
DDMMYY
311204
Day
YYMMDD
041231
Day
MMMDDYY
DEC3104
Day
DDMMYYYY
31122004
20041231 recommended
8
DAY
YYYYMMDD
4804
Week
WWYY
0448
Week
YYWW
48-04
Week
WW?YY
04-48
Week
YY?WW
482004
Week
WWYYYY
200448 recommended
WEEK
YYYYWW
MMMDDYY
4
Month
Month
Month
Month
Month
MONTH
Bimonth
Bimonth
Bimonth
5
5
6
6
3
3
4
4
4
0412
MMYY
YYMM
MM?YY
YY?MM
MMYYYY
YYYYMM
BYY
YYB
BBYY
Bimonth
YYBB
Bimonth
XYYY
5
5
Bimonth
Bimonth
Bimonth
Bimonth
BIMONTH
Quarter
Quarter
Quarter
Quarter
Quarter
Quarter
Quarter
5
6
6
3
3
4
4
5
5
6
6
2
4
1204
12-04
04-12
122004
200412 recommended
204 (second Bimonth 98)
042
0204
0402
MA04
MA.04
22004
XY?YY
BYYYY
YYYYB
BBYYYY
YYYYBB
QYY
YYQ
QQYY
YYQQ
QYYYY
YYYYQ
QYYYY
20042
022004
200402 recommended
104
041
0104
0401
12004
20041
012004
200401 recommended
04
2004 recommended
Quarter
Year
YYYYQQ
YY
YEAR
YYYY
104
Board
type
Entity code
field
Description
OPTION
[blank]
The incoming record is only loaded if the value found in this field is the
code of an existing member of the entity; otherwise the entire record is
discarded.
This option is used to filter unwanted records.
Append
This option validates all incoming records; when the value from the data
source is not the code of an existing member of the entity, a new member
is created.
This option is used to populate entities.
Entity
description
InfoCube
[blank]
This option only loads the description if the current entity member
description field is not populated; therefore only descriptions for newly
created items are loaded.
Replace
This option overwrites the entity member description with the value from
the source file. It is recommended to always enable this option in order to
update entity members descriptions with changes that might occur on the
operational system master files.
[blank]
This option adds incoming data to the InfoCube; if the InfoCube already
contains values, then the new data is summed. Clearly summing of data
occurs only in case where the InfoCube is numeric; for date and text
InfoCubes, the current cell value is replaced with the source data.
Replace
This option replaces the InfoCube cells belonging to all time periods
found in the incoming data, with the new values. When this option is
enabled, the Data Reader performs the following actions
1. scans the entire source file and memorizes the time periods (i.e. the
values of the date field).
2. then clears the InfoCube cells belonging to the time periods found in
the source file.
3. then starts loading source data into the InfoCube.
For example, consider a file containing transactions for January, February
and March 2004. When loading this file, the datareader starts by
scanning the date field of all records and memorizes the dates. Then it
clears all InfoCube cells for January, February and March 2004 (across
all other dimensions) and finally, it reads the values in.
Note! The Data Reader cannot read text files exceeding 2GB in size. This limit only
applies to text files.
730
950
1200
840
Product 02
1400
1650
2050
1925
Product 03
850
740
976
752
107
Warning! The entity across cannot be a sparse entity for the InfoCube being read.
108
Click the ODBC source drop-down list and select the ODBC source name. Note that the
ODBC source (DSN) must be defined on the computer where BoardServer is running.
After selecting the ODBC source name, the available tables and views are listed in the table
underneath the ODBC source list. Select the table (or tables) you wish to imports data from
then click the OK button as illustrated.
After clicking OK, the table fields list appears. Click on the desired field, then, keeping the
mouse button pressed, drag and drop the cursor in the cell next to the entity or InfoCube you
want to feed, as illustrated.
109
Optionally, you can then edit a field and type an expression. You may, for example, wish to
divide or multiply a field. Double-click on the field you want to edit, then, using the commands
and syntax supported by the ODBC driver used, type in the expression.
If you have selected more than one table or view, click the Join button and set the join
conditions. Drag and drop fields from the source tables into the Join window. The join
statement generated is an equal join (natural join). If you need to define a different type of join,
for example an outer join or a right join, use the Edit button to edit the SQL statement (see
below).
110
For each field (except standard time entities), set the Append/Replace option as desired.
Click on the yellow cell to change setting. Refer to the paragraph Append and Replace options
for details.
Press OK to save the protocol.
Defining an ODBC Data Reader protocol generates an SQL statement. When the protocol is
launched, Board sends the SQL statement to the ODBC provider and waits for the results.. Note that
the SQL statement is run on the ODBC provider therefore the commands and syntax which are
supported depend on the ODBC provider you connect to.
It is recommended you test the SQL statement using the Browse function: from the protocol definition
window, click the Edit button, then click the Browse button. The query is executed on the first 200
rows and the result data is displayed in spreadsheet format.
Note that Board is not a SQL query generator, if complex queries are needed it is recommended you
use an ad-hoc query tool to create and test the SQL statement.
Editing and testing the SQL statement of an ODBC Data Reader protocol
To view, test and edit the SQL statement of a Data Reader protocol, open the protocol definition
window and click on the Edit button.
The upper text area contains the SQL statement generated by Board, based on fields selected in the
protocol definition window. The lower text area can be edited; you can type your SQL statement here
or click the Copy button to copy the text from the top to the lower text area, you can then make
changes as desired.
111
Click the Browse button to test an SQL statement on the first 200 rows of the source tables.
Note! The maximum length of an SQL statement is 3000 characters.
The Query Timeout field sets the maximum number of seconds available for a query. Typing the
value -1 sets the time-out to unlimited.
It is generally not necessary to define an ODBC connection string, when it is not set, Board uses the
minimal value as the connection string:
ODBC; DSN=[data source name]; PW=; UID=;
If a connection string is defined for a protocol then it is used for all protocols which share the same
data source name (DSN).
112
The formulas and validation rules defined in the ETL are calculated record by record on the incoming
data. An ETL formula can refer to any field of the record. The transformed record, i.e. the result of the
calculation, is the output ETL. This output is the data which is actually loaded into the Board database.
To define an ETL set of rules on a Datareader protocol, click on the gray cell in the ETL column.
The InfoCubes and Entities of the Data Reader protocol are displayed in columns A and B (Type and
Field). The ETL input (shown in column C) is the incoming external data from the source system (an
ASCII file or an ODBC data source). The ETL output, shown in column D, is the transformed data
(after applying the formulas) used to feed the Entities and InfoCubes.
113
The transformations defined in the above example are common spreadsheet formulas. The
expressions used are shown hereafter.
Lets consider the example in the above illustration. In the Month entity, the following formula is
defined: =E3&F3. This formula concatenates fields E3 and F3 on which other formulas are defined.
Cell E3 is calculated by applying the Year() function to cell C3; this function returns the year part of
the date specified in C3. Cell F3 is calculated by applying the Month() function (retuning the month
part) to C3. Cell C3 contains the field Sales.Date from the source table. The formula E3&F3 therefore
returns the date formatted as follows YYYYMM, which is compatible with Boards Month entity. The
Gross Sales InfoCube (cell D6) is calculated by multiplying cells C6 and C7 corresponding to the
quantity and price fields from the source table.
114
While a Data Reader protocol is running, a pop-up window shows the process progress.
This window show the Data Reader protocol name, the number of records read (in the example,
REC=6,700), the number of validated records (in the example, OK=6,720) and the number of
rejected records (in the example, REJ=0).
Note that this log window does not appear if the reading process only takes a few seconds to run.
Clicking the break button closes the log window but does not interrupt the data import process, which
is actually executed by a BoardServer.
115
Optimization tips
It is recommended that you load data in chronological order to obtain an optimized database
When loading large amounts, you can obtain significant loading performance improvements by firstly
sorting data on the date field, followed by the fields corresponding to entities with the smallest Max
Item Numbers. For example, lets consider a table with the following fields: Date, Customer, Product,
Sales Amount and with Month, Product and Customer as the corresponding entities. Supposing
the number of customers is greater than the number of products then the source data should be
sorted by date-product-customer fields If you are loading data through ODBC, use the ORDER BY
clause in the SQL statement to sort the data or create an index on the table.
Batch reader
Basic concepts
The Batch Reader allows you to define a sequence of Data Reader protocols.
A Batch Reader procedure can be launched
Interactively from the Batch Reader window.
From a command line, (from a tasks scheduler for example).
From a Board Capsule procedure.
To open the Batch Reader, click the following icon:
Click on a line and select the Data Reader protocol from the pop-up window.
Click the Do check-box to enable the protocol. Optionally, click the Log check-box: when
enabled, if while importing data some records are rejected due to a validation conditions or a
data type error, then a log file is created in the discarded records.
116
Optionally, enable the Normalize check-box. When set, after running a Data Reader
protocols that feeds a hierarchy, the Normalize function is launched using the settings saved
in the Relationships window.
Click the Save button to save the procedure settings.
117
- To launch a Batch reader procedure from a command line, run the following command:
[..]\BoardClient.exe [Folder]\[DBName]:[BatchReaderName]@[URL:Port]
where
[..] is the path where BoardClient is installed,
[Folder] is the alias of the database folder (usually Main),
[DBName] is the database name,
[BatchReaderName] is the name of the Batch reader procedure you want to launch
[URL:Port] is the BoardMaster address and port number.
This command can be launched from a task scheduler, while Windows is logged-off.
Example
c:\Board.sys\BoardClient.Exe main\Sales:NightlyUpdate@BoardMaster:7000
Drill-Through
Basic concepts
The Drill-Through function allows users to drill from a summary analysis through to data held in a
relational database. This function is useful when users need to investigate data to detail greater than
the lowest level of the InfoCubes.
Consider a typical Board database, the detail level of InfoCubes allows users to drill from summary
reports down to the individual InfoCube cell, for example Day, Product and Customer. If sales of a
particular product are exceptionally high, the user can firstly drill-down to the Customer level, then
select a particular customer that you wish to analyze, then finally drill-through and retrieve the exact
transactions from the accounting ledger for that particular day/product/customer.
118
Click the ODBC source drop-down list and select the ODBC source name that links you to the
desired relational database. Note that the ODBC source name (DSN) must be defined on the
computer where BoardServer is running.
After selecting the ODBC source name, the available tables and views are listed in the table,
underneath the ODBC source list. Select the table (or tables) you want to link to then click the
OK button as illustrated.
119
After clicking OK, the table fields list appears. Click on a table field corresponding to one of
the selected entity codes, then, keeping the mouse button pressed, drag and drop the cursor
in the cell adjacent to the entity, as illustrated.
Define the Join condition if required (refer to the paragraph Creating an ODBC Data Reader
protocol).
Edit the SQL statement to add other fields to the Drill-Through protocol: click the Edit button,
then click the Copy button and add other table fields after the existing fields needed to link to
entities. Press OK to close this window
120
A Drill-Through protocol only allows you to drill a report from an entity which is included in the protocol.
To be able to drill from a more aggregate entity you must define an E/R protocol that links the parent
entity to the child entity present in the Drill-Through protocol. For example, to be able to drill-through to
the invoices table by City, starting from an aggregate report, you must define an E/R protocol with City
and Customer entities (we are assuming that the invoices table contains a Customer field and
doesnt include a City field).
The E/R protocols must be defined in the E/R column; to configure a protocol follow the same
procedure described for Drill-Through protocols. Note that drilling-through from an aggregate entity
may return a large number of transactions, therefore it is not advisable to allow drilling-through from
highly aggregated entities.
Rules
Basic concepts
A Rule allows defining an entity member as the result of a formula based on other members of the
same entity. Rules are sets of formulas defined on members of the same entity. A Rule is associated
to an entity and can be used with (or applied to) all InfoCubes structured by that entity.
A typical example is that of a profit & loss statement (P&L) where some P&L lines are calculated from
other lines. Consider the P&L as being an entity in which the P&L lines are its members (as follows):
L01 Gross Sales
L02 Cost of goods sold
L03 Gross Income
L04 % on GS
121
L02 % on GS
Defining a Rule
Click the Rules icon.
In the rules definition window, type the name of the new Rule (in a white cell) and click the yellow cell
to select the entity on which the rule will be defined.
122
Note! The Rule definition window allows managing a maximum of 65000 rows.
123
124
Note that Rules generally include algorithms or formulas which cannot be aggregated (for example
percentages and ratios) it is therefore uncommon to apply Rules in DataFlow procedures.
Security
Basic concepts
This function allows you to define the database security profiles. There are two types of privileges that
can be set:
privileges on database functions: you can allow or deny access to the database design.
privileges on data access: you can define which InfoCubes can be viewed and how (read-only
or read/write mode) and restrict access to a portion of the InfoCube by defining which entity
members the profile is authorized to view.
To access the security profiles click the Security icon.
The first column of the security window (yellow background) contains the database features and the
database InfoCubes. Each profile is configured in a column. The column is reserved for the
administrators profile.
125
Database
INFOCUBES LIST
To restrict access to a sub-set of InfoCubes cells, click on the column header and define the selection
as desired.
Using this function you can define a security profile restricted to an area or to a set of cost centers or
another selection of entity members. When users with this profile run an analysis, they are
automatically restricted to the data within the authorized selection.
126
then, enable the Optimize option if desired and click the Go button.
It is strongly recommended that you make a backup copy of the database before running this
function.
The ”Optimize option completely re-writes the database files therefore, for large databases
comprising of several giga bytes, it may require several minutes or hours to run.
Log file
The database log file is a text file where some database actions are logged. The log files are located
in the directory DatabaseName.bmi\Log . To view the current month log file click the following icon:
The log file records database design changes (the definition of new entities and relationships), the
execution of data reading procedures (Data Reader protocol and number of records loaded) and the
execution of the DB Verify function.
127
128
Chapter 7 Capsules
Capsule basic concepts
Prerequisites
Before reading this chapter read Chapter 1 - Welcome on Board, for a general introduction to
Capsules. Refer to Chapter 6 &endash; Database Design to familiarize with multidimensional
database concepts and the specific terminology.
Capsule structure
A Capsule is a collection of screens and procedures. Screens contain objects such as spreadsheets,
charts, and buttons. A screen is linked to a Board database thus all objects and procedures of a
screen access InfoCubes and entities from the same database. A screen can be linked to a one
database only but different screens of the same Capsule can link to different databases.
A Capsule doesnt contain any stored data; it only contains the report definitions (the Layout) and the
definitions of data presentation objects (spreadsheets and charts). Whenever the Capsule is opened,
the data is freshly retrieved from the database.
A Capsule can have several screens; generally a screen contains buttons linking to other screens thus
guiding the user through the various analyses. For better clarity and easier maintenance, it is
recommended to limit the number of screens contained in a Capsule to no more than 30 or 40
screens. It is possible to create jumps from a Capsule to a different one.
A Capsule is a file, usually stored under the \Board\Capsules directory on the computer where
BoardServer is running. The Capsule file is a file having the name of the Capsule and extension cpx.
A typical Dashboard providing a high level view on some business metrics through graphical
representations.
129
130
Chapter 7 Capsules
Opening a Capsule
To open a Capsule, click the navigator tree icon to display the navigator,
The name of the current Capsule is displayed in the text area (located at the bottom of the
Workspace).
131
Note that the screen list and the custom links are active only while in runtime mode; design mode
allows to set the custom links by dragging screens from the screen list to the custom links. Different
custom links can be set on each screen.
The screen icon located at the top right (see illustration below) allows to:
go back to the previous screen (with a left-click),
jump to the main Capsule screen (with a right-click),
close the Capsule if clicked when you are on the main Capsule screen.
The navigator tree also allows navigating through screens. Right-click on the Capsule name then
select the desired screen from the list as illustrated.
132
Chapter 7 Capsules
Workspace features
The Workspace provides access to common features while in runtime or design mode.
The DynaBar: allows adding or removing a paging entity. When an entity is set in the DynaBar, you
can select an individual item and refresh the screen data; for example set Month in the DynaBar then
select January 2004 to obtain data from that month only. Refer to the DynaBar paragraph for details.
The Select function: allows defining selection criteria on entities. After selecting some entity members,
the screen is refreshed extracting data limited to the selected items. The Select is functionally similar
to the DynaBar but it allows selecting multiple items. For example you can select a range of months, a
selection of Cities and so on and the screen will be refreshed limited to the chosen items or ranges.
The maximize icon, allows to enlarge an object to full screen size.
The printer icon, allows printing an object.
The Design mode icon allows switching from runtime to design mode and vice-versa.
The Save icon allows saving the changes Capsule.
Note that the Design mode and save icons are displayed only if you have appropriate privileges.
Collaboration functions
Boards collaboration functions
Collaboration functions allow two or more Board users, located remotely, to share real-time navigation
of Capsules through a virtual meeting.
Board provides two types of collaboration functions, the Briefing and the Synchronous
collaboration.
In a Briefing session, there is a presenter and an audience. The presenter can open a Capsule,
navigate through screens working normally, and attendees receive the image of the presenters
computer screen. The presenter uses his BoardClient to run the session. The attendees can join the
session using BoardClient or an Internet browser.
In a Synchronous Collaboration session, all users have the same level of privileges. It is a
collaborative meeting where any user can take control over the Capsule, run a drill-down, make a
selection or click on a capsule screen button to run a procedure. When the first user opens a Capsule,
the same screen will automatically open on other users computers. Once the capsule has been
opened, when a user takes an action, the result of the action is replicated on other users BoardClient
133
Presenting a Briefing
To present a Briefing, click the collaboration icon then choose the Briefing / as Presenter option.
The meeting code is a password that the as a presenter you should communicate to all attendees in
order to attend the Briefing session.
Type a meeting code then click the Connect as Presenter button.
An icon in the bottom toolbar indicates you are projecting your screen image. Place the mouse over
the icon to view the list of attendees.
Note that while you are presenting, your mouse pointer is not part of the projected image. When you
open a capsule, a red arrow pointer automatically appears in the bottom toolbar. Click on the icon then
drag and drop it on the Capsule screen onto the object you wish to point at.
To end your Briefing session, press F4 keyboard key to view the toolbar, then go to the Briefing logon
window (click the Briefing / as Presenter icon) and click the Disconnect button as illustrated.
134
Chapter 7 Capsules
Attending a Briefing
It is possible to attend a Briefing using the BoardClient program or an Internet browser.
To attend a Briefing using an Internet browser, click the Briefing icon, as illustrated then when
prompted type the Briefing access code provided by the presenter.
A web page containing a Java applet will display the briefing images. The first time you access a
briefing, you will have to install the Java applet, follow your Internet browsers instructions.
Note that the Java Virtual Machine (JVM) is not included in the default installation of
some operating systems (for example some Microsoft XP configurations do not include
JVM). You must install JVM 1.2 in order to run the briefing applet.
To attend a Briefing session using BoardClient, press the F4 keyboard key to view the top toolbar,
click the collaboration icon then choose the Briefing / as attendee option.
A logon window prompting the meeting access code will appear. Type the meeting code provided by
the presenter, then click the Connect as Attendee button.
A white screen with three icons in the top right corner will appear and after a few seconds you will start
viewing the meeting.
135
136
Chapter 7 Capsules
Type the meeting access code in the Meeting Code field, select the BoardMaster address from the
address list box then click the Connect button to start the session.
An icon indicates a session is active and the connected users.
In a Synchronous Collaboration meeting, you can enable voice transmission by configuring the
following parameters:
Drop-down list
Blocks
Compression
Microphone Locking
These two sliding cursors allow you to tune the noise level
threshold that initiates the voice transmission. Voice is
transmitted whenever the noise level in decibels (shown in the
cell to the right of the Volume cursor) is higher than the
threshold set by the Peak cursor. The values must be tuned
depending on the room noise level and the microphone
sensitivity.
To fine tune Volume and Peak values: set the Volume level to
. Read the dB noise level in the room then set the Peak value
to 5-10 dB higher.
Fast Commuting
Voice transmission stops when the noise level is lower than the
Peak threshold. By disabling Fast Commuting, the
transmission continues for another sampling period, resulting in
a more fluent conversation. Disabling this option is
recommended when the speaker is primarily a single person
and other attendees do not speak frequently.
To start audio transmission, click the voice check-box. It is recommended using headsets when
enabling the voice transmission. Using the speakers and microphone commonly integrated on laptop
computers can produce echoes or resonance since the two devices are located relatively close one
another.
Before using the voice transmission, verify the connection quality to the BoardMaster using the Speed
Test; the value of the ”Net indicator must be greater or equal to 100%.
The Select
What is the Select function
The Select function defines the parts (a slice) of the InfoCube (or InfoCubes) to retrieve data from. A
selection on entity members reduces data extracted from the database to the chosen items only. For
example, by selecting the city of San Diego from the City entity, the data extracted from InfoCubes
will be limited to San Diego only. After making a selection, all screen objects showing data extracted
from InfoCubes are refreshed.
138
Chapter 7 Capsules
The selection is a property of the screen; when a selection is made, it applies to all screen objects,
including procedures launched from that screen.
When a selection is made on an entity part of a hierarchy it is propagates to all entities of the
hierarchy. For example by selecting the city of San Diego from the City entity, immediately the
selection is propagated to parent entities, for example the Sate of California and down to less
aggregated entities, for example all Customers of San Diego.
To access the select function, click the Select icon or the Tree icon.
The Tree icon displays the hierarchies representing the bottom-up relationships (excluding the time
hierarchy) and allows making selections on entities from a hierarchy only. The Select icon displays the
list of all entities of the database and allows making a selection on any entity.
In the Select window some entities may have a gray background; access to these entities has been
disabled by the database administrator (the User View option has been disabled from the Entity
window).
Making a selection
To make a selection,
Open the Select window by clicking on the Select icon or the Tree icon,
Click on the chosen entity name, a window with the entity members will appear.
Click on the desired entity members. To select a set of contiguous items, click and drag the
mouse down while keeping the button pressed.
Then click the Select button to select the highlighted items or click the Exclude button to
select all other items.
When a selection is made the Selected column indicated the number of selected items. The MaxNr
column indicates the total number of entity occurrences.
Resetting a selection
To reset a selection,
Open the Select window,
139
To reset a selection from the Tree window, drag and drop the reset icon onto the desired entity.
Note that resetting the selection on an entity of a hierarchy automatically resets selections for all
entities of the hierarchy. For example, if you select the July-2004 from the Month entity, the selection
propagates to year 2004 from the Year entity. Resetting the selection on the Month entity to all
existing months consequently resets the selection to all years of the Year entity.
This feature is not available on entities highlighted with a yellow background (non cached entities).
140
Chapter 7 Capsules
Note that whenever you click Find, the occurrences previously selected are reset.
141
To use the focus function from the Tree window, drag and drop the focus icon onto the desired entity.
The DynaBar
What is the DynaBar
The DynaBar allows to set paging criteria on a screen. The DynaBar can contain one or more entities
and like the Select function allows selecting entity members. When a specific occurrence is chosen,
the screen data is refreshed limiting the extraction to the selected occurrence only.
142
Chapter 7 Capsules
The DynaBar is a property of the screen; when a selection is made, it applies to all screen objects,
including procedures launched from that screen. The DynaBar configuration is saved when saving the
capsule.
The DynaBar object is located at the top of the screen area as show in the following illustration.
When adding two entities hierarchically related (child parent), it is good practice to add the parent
entity first then the child entity so that the order of entities goes right to left from the most aggregate
entities to the less aggregate. For example if you wish to set the Month and Year entities in the
DynaBar, include the Year first then Month.
To remove an entity from the DynaBar, drag and drop the entity to the trash bin as illustrated.
143
The DynaBar can be configured at runtime and design mode. Changes made while in runtime mode
are not saved. The DynaBar configuration is saved when saving the screen.
Click the No All option to removes from the occurrences list the ALL option that corresponds to
selecting all occurrences. For example, setting the City entity in the DynaBar, it is possible to select an
individual city or the ALL cities (giving the grand total on all cities). By enabling No ALL option the user
must select a single city and the total will not be available.
To remove all entities from the DynaBar, click the clear button.
Chapter 7 Capsules
to another screen having Month, State and Product in the DynaBar: the Month and State entities
will automatically set to July2004 and California, the selection made on the prior screen.
A drill-down floating window opens. It is possible drill-down from a drill-down window, nesting levels
down to the lowest detail level.
Click the Up button of a drill-down window to close it. You can drill-down on other rows using the
same drill path by clicking the row header with the left mouse button.
Drill-down paths can be saved for reuse. To save a drill-down path, save the screen. To reuse a saved
drill-path, left click on the report row header.
Note! it is possible to change the Layout of a drill-down window; right click to access the
Layout. Changes to the Layout of a drill-down window are saved when saving the capsule
screen.
It is possible to drill-down on reports allowing data-entry and the drill-down window will also allow dataentry. The Save and Undo data-entry buttons of the drill-down window are il the upper left corner as
illustrated.
145
How to drill-through
To drill-through on a report row: right-click on the row header, click the Query list button, select the
desired drill-through protocol and click the Go button. To avoid retrieving a large number of
transactions from the source system, it is recommended using the drill-down function to reach the
lowest detail level available in the Board database and then run the drill-through from that level.
Note! the printer icon is not available on drill-down windows allowing data-entry.
146
Chapter 7 Capsules
Capsules Management
Copying and Deleting Capsules
To copy a Capsule, open the navigator tree, right-click on the Capsule then drag and drop the mouse
pointer to the desired folder. You will be prompted the new Capsule name.
To delete a Capsule, drag and drop it to the Recycle bin found on the navigator tree. Note that
deleted Capsules files are not physically deleted from the server, they are moved to the
Board\Recycle directory.
147
To delete a Capsule screen or a procedure, drag and drop it from the screens list to the Recycle bin
found on the navigator tree.
Chapter 7 Capsules
Optionally if the procedure only contains actions that take place on the server side (for example a
sequence of Data Reader protocols and DataFlow calculations) then it is possible to add the
parameter unattended at the end of the command line so that the BoardClient triggers the
procedure on the server side and closes immediately while the procedure keeps running on the
BoardServer.
\BoardClient.exe [Folder]\Capsule@MasterAddr:Port unattended
To create a Capsule for batch processing, for example a Capsule that runs the database update
procedure,
Create a Capsule with a single screen,
Create the Procedure (sequence of Data Reader protocols and other actions)
Place a button object on the capsule main screen, link the procedure to the button and enable
the Auto go button property.
Note that it is possible to launch a Board BatchReader from a command line, refer to the BatchReader
documentation for details.
Capsules Design
Capsule design concepts and guidelines
Capsules can address a wide range of purposes. For example, a Capsule could be
An unstructured environment for ad-hoc analysis;
A highly structured application guiding users rigidly throughout a business process such
as a budgeting and forecasting application.
An EIS (Executive Information System) application providing dashboards and executive
reports.
A presentation analyzing or projecting a marketing campaign results, a product launch or
other business processes.
A recurrent analyses booklet.
A set of database maintenance tasks
&ldots;
Depending on the Capsules purpose and the type of users the Capsule is meant for, take into
consideration the following guidelines,
Organize you Capsules into folders: you can create folders visible to all users, folders visible
to user groups and private folders.
The Capsules main screen should explain the Capsules purpose and contents. Put some
introductory text and a diagram illustrating how the Capsule is organized.
Limit the number of Capsule screens to a reasonable number that allows users to well
understand and know the content of each screen. This simplifies navigation and
maintenance. A single Capsule should not have more than 35 to 40 screens. If more
screens are needed, consider creating a new Capsule (it is possible to create a navigation
going from a Capsule to another).
Avoid creating similar screens having very slight differences. For example, two identical
screens in terms or reports only having a different selection. This approach would cause a
proliferation of screens; all users must know how to use the Select, the DynaBar and the
drill-down features.
149
Chapter 7 Capsules
Type the Capsule name and select the folder where to save the Capsule.
Alternatively you can start developing your screen on the Workspace, then when you press the Save
button you will be prompted the Capsule name and folder.
Note! When you create the first screen of a Capsule you must link it to a database by clicking the
desired database from the navigator tree list as illustrated.
You can now start developping your Capsule screen by adding objects from the toolbox as desired.
Protecting a Capsule
You can restrict access to a Capsule design by setting a password. Open the Screen property window
and click the Capsule Locking icon and type a password or a list of passwords.
The Capsule Locking icon is show in the following illustration
151
When a Capsule is password protected, the navigator does allow viewing the screens and procedures
by right clicking on the Capsule name.
Screens
About screens
Screens are part of a Capsule. The screen is the working area where you can place objects from the
toolbox. A screen is usually split into vertical and horizontal lines, forming panes (rectangle areas)
each one containing an object from the toolbox. A screen can also contain floating panes that allow
creating areas with objects overlapping.
Chapter 7 Capsules
The Board database. A screen is linked to one Board database. All objects on the screen
present data extracted from the same database. The name of the linked database is usually
visible in the message area in the bottom toolbar (this text area might be used for comments
or messages).
The DynaBar. A screen can have one DynaBar configuration and the DynaBar applies to all
screen objects.
The Select. A screen can have one Select only, applying to all screen objects.
The Menu. Each screen may have a different Menu, linking to other screens.
Note! When you create the first screen of a Capsule you must link it to a database by clicking the
desired database from the navigator tree list as illustrated.
Screen properties
To access the screen properties box, click the Screen Properties found in the top toolbar.
153
Title
First Screen
ScreenSize
FontSize
Defines the default font size of the DataView and DynaSheet objects.
BackColor
Defines the screen background color. Click one of the available colors
or click the custom color icon.
ShowLines
While in runtime mode, displays the vertical and horizontal lines dividing
the screen into panes. The width of the dividing lines can be adjusted
using the cursor object. The Lines 3D option creates a 3D effect on
lines. When disabled, the lines width can be set to zero.
Comment
Text area. The text will be displayed at runtime in the messages area
located in the bottom of the toolbar
.
Capsule Locking
Hides the screen list from the Menu object, while in runtime mode. Note
that this setting applies to all Capsule screens, not just the current
screen.
Creating a screen
To create a new screen, click the new screen icon located in the toolbar.
To create a screen from an existing one, use the Save as function as illustrated
154
Chapter 7 Capsules
When you add a screen to an existing Capsule, the new screen is automatically linked to the same
database of the previous screen. You may change the database by selecting it from the navigator
database list as illustrated.
Saving a screen
To save a screen, click the Save screen icon located in the toolbar.
After saving a screen from design mode, the Save screen icon remains available in runtime mode as
well in the bottom toolbar.
Deleting a screen
To delete a screen, open the screen then click the Delete button found in the top toolbar as illustrated.
You can also delete a screen using the navigator tree: right click on the Capsule name to view the
screen list then drag and drop the screen to the recycle bin located on the navigator. Refer to
paragraph Copying and Deleting capsule screens and procedures for more details.
To add an object, click on the desired object and while keeping the mouse button pressed, drag and
drop the object to the desired pane.
To remove an object, click the Remove button of the ToolBox then drag and drop it onto the object to
remove.
Click the Clear all button if you wish to remove all objects from the screen.
156
Chapter 7 Capsules
The tool box objects
Screen size
157
Defining a Layout
158
Chapter 7 Capsules
This paragraph illustrated the main steps to define a Layout. Each step is examined in greater detail
later in this chapter.
Right click on the desired object to access its Layout configuration. For the DataView object
the Layout window opens immediately, for other objects select the Layout option from the
properties menu window.
The Data tab shows the columns list. To add a column, click on a line as illustrated.
Select the desired InfoCube from the Data selection list or other type a formula in the
Column algorithm field if you wish to define a calculated column or select and entity from the
Entities & relationships list. Refer to the Data settings paragraph for more details.
159
Click on the next row and define other InfoCubes or calculated columns as desired.
Click on the Axes tab to select what entities should be set in rows and columns. Drag and
drop the entities from the left list to the By Row and By Column fields as desired.
160
Chapter 7 Capsules
Optionally, click on the Filters tab and set sorting and filtering options as desired. Drag and
drop an InfoCube to the Sort by or to the Filter A or Filter B fields.
Optionally, click the Format tab button to define fonts, color and other format options (The
Format properties apply to the DataView object only).
161
Setting Data
The Data tab defines the Layout columns. A column may contain an InfoCube, a formula or an entity.
For each column you may apply optional settings, for example type the column heading, define the
display format, define alerts (i.e. red and green conditional coloring) or apply a statistical function and
other options detailed hereafter.
Layout columns, also referred to as data blocks, are identified by a letter ranging from a to z, found in
the row header.
To copy an existing column, right-click on the line to copy then drag and drop it to the desired new
line. To clear a column, right click the row to clear then drag and drop it to the bin.
To set a column, click on a line, the configuration window will open, then set one of the four data fields
as illustrated.
Data Selection
162
Chapter 7 Capsules
Click and select an InfoCube from the list. The drop-down list shows all InfoCubes on which the user
has read-only or read/write privileges.
Column Algorithm
Type a formula using row letters to reference other columns. For example to divide column a by
column b and multiply by 100 type the formula a/b*100.
A formula is a string containing numbers, operators, functions and references to other columns
(through the letter identifying the row).
The following table lists the operators.
Type
Operator
Description
EXAMPLE
Arithmetic
Addition
a+b
Subtraction
a-b
Division
a/b
Multiplication
a*b
Percentage
Text
Exponentiation
&
Concatenation
Comparison
Equal to
a=b
>
Greater than
a>b
<
Less than
a<b
>=
<=
Less
than
equal to
ora<=b
<>
Not equal to
a<>b
The following table lists the most common functions. A more comprehensive list of supported functions
can be found in Appendix A.
ABS(number )
Returns the absolute value of a number.
Example
ABS(a-b)
163
Chapter 7 Capsules
Exampe
a/gt(a)*100
Note! the above examples use the comma as list separator. The list separator character
may vary depending on your computers settings. The most common characters used are
the comma and the semicolon. The list separator is defined in your computers Control
Panel / Regional settings window.
An algorithm may return different data types. By default, it is assumed that an algorithm returns a
number, however the data type list box allows to select several data types: Numeric, Text, Date and
Picture. When the formula returns a text or a date select the data type option accordingly.
The Picture option, applicable to the DataView object only, allows displaying images the spreadsheet
cells. Define a formula that returns the name of a picture file then select the Picture option. The image
files must be located in the directory \Board\Images\Pictures. The supported file formats are
JPG, GIF, ICO, BMP (the bitmap format is not recommended as it generates significant network traffic
in comparison to other formats).
Ranking function
Select one of the available pre-built functions. Ranking functions are evaluated on the column prior to
where it is defined therefore you cannot set a ranking function in column a. To use a ranking function,
the layout must have one entity set by row.
These functions allow to quickly create 80/20 analysis.
Cumulated Vertical%
Counter
Row counter.
165
Cumulated Counter %
Cumulated Value
80-95 Ranking
Heading
Type the column heading. If omitted, the InfoCube name of the formula will be used as heading.
Decimal digits
Set the number of decimal places to display. Applies to numeric fields only.
Divide By
Divides the InfoCube values by the specified number. This option can be applied only on numeric
InfoCubes; it cannot be applied to column algorithms.
Summary algorithm
Sets how to calculate row and column totals.
When an InfoCube is selected, the options are:
166
Chapter 7 Capsules
Total: the totals are calculated by adding values.
No total: the totals are disabled.
When a Column algorithm is defined, the options are:
Total: the totals are calculated by adding values.
Calculated: the defined formula is re-applied on the totals cells of the blocks referenced in
the formula. This option must be selected for example on a percentage calculation or other
formulas involving divisions.
Note! The number of iterations for resolving recursive formulas is of three. There can be
cases of reports having a calculated column based on another calculated column where
the summary algorithm of the two columns are different (one being set to
”Calculated and the other to ”Total) showing an incorrect total when its
evaluation requires a higher number of iterations.
Row totals
Allows disabling the row totals. This option applies only when the Layout has at least one entity set by
column.
Allow Changes
Click this option to enable data-entry on the column. Note that activating this option alone is not
sufficient to enable data entry; other conditions must be met:
The user must have an appropriate Board license and security privileges allowing write-back.
For text and date InfoCubes data-entry is supported only at physical level not at on
aggregate views.
Data-entry is not permitted on MXC InfoCubes.
167
Hide zeros
When enabled, cells having value zero are displayed blank. This option applies to the DataView and
DynaSheet objects only.
Functions tab
The functions tab provides common time functions that can be applied to numerical InfoCubes.
168
Prev.Year
Previous year function: returns the previous year data for the
currently selected periods. For example if the current screen
selection is May 2004 to July 2004, the previous year function
will return the data for May 2003 to July 2003.
Value
Chapter 7 Capsules
Returns the cumulated value from the first period of the year.
For example, when applied to a monthly InfoCube, it returns
the cumulated from January of the currently selected year;
when applied to a daily InfoCube it returns the cumulated
value from the first day of the year.
Fiscal Year. The yearly cumulated function can be combined
with the Fiscal Year option to return the cumulated value from
the first period of the currently selected fiscal year. This option
is available only if the Fiscal year is defined in the Board
database time range definition (refer to the Database Design
chapter).
Trend
Forecast
Cycle
Note! The time functions are not applicable to InfoCubes having single dimension or
InfoCubes structured by a custom time entity.
Rule
Allows selecting an existing Rule to apply to the current data column. Refer to the Database Design
&endash; Rules chapter for details on Rules.
To apply a Rule, the entity on which the rule is defined must be set either by row or by column. If it is
set by row, it is possible include another entity by row but only if it is not hierarchically related to it and
as a grouping entity (set this entity first, then the one on which the rule is defined). For example, if a
Rule is defined on the entity ProfitAndLoss and then you can set the this entity by column or row. If
you set it by row you can also set another independent entity for example Month-ProfitAndLoss, but
not ProfitAndLoss -Month.
References tab
Reference functions can be applied to InfoCubes only.
The References tab is show in the following illustration.
170
Chapter 7 Capsules
Detail By
Allows selecting an entity by which the data column should be detailed across
columns. This option overrides the setting defined in the By Column axis of
the Layout.
Total By
171
Refer To
Allows referring the data block to a specific entity occurrence, overriding the
screen selection and the axes setting. Select the entity first from the white
drop-down list then select the desired entity member from the black list-box.
It is possible to set up to three refer to conditions on distinct and unrelated
entities.
Example: setting Refer to on the entity occurrence state of California, will
return the data for that state regardless of the rows, columns and selection as
illustrated.
The Refer to condition can also be used to create a total: referring to an entity
that is more aggregate than the entities by row or column, returns the referred
occurrence. For example, if a Layout where Month and City are set by column
and row, using the refer to function on Year or State entity returns the total
value for the referred year or state.
172
Chapter 7 Capsules
Alert tab
The Alert function allows defining two types of alert behaviors
Conditional coloring: based on two threshold values, the Red Alert Value and the Green
Alert Value, the cells containing values smaller than the red alert are colored red and those
with a value higher than the green alert are colored green.
Gauge: provided a set of images representing an alert status or value, the gauge function
displays the image representing the cell value out if the provided set.
Feature is disabled.
Figures
The coloring affects fonts. Values greater than the green alert are displayed
green and those smaller than the red alert are red.
Blocks
The coloring affects the cells background. Cells where the value is greater
than the green alert assume a green background and those where the value is
smaller than the red alert assume a red background color.
173
Blocks only
The cell background is colored and the cell values are hidden.
Note! If the value provided as a red alert is higher than the value set as green alert, the
coloring is reversed, cells having a value higher than the red alert are colored red and
cells having a value smaller than the green alert are colored green.
Gauge
The gauge feature displays a picture that varies depending on the cell value
and the red and green thresholds. Type the root name of the file set followed
by three ”? (question marks) characters and the file extension.
To use the Gauge feature, a set of image files must be present in the directory
Board\Images\Gauges. The supported file types are GIF, JPG and ICO.
All files belonging to the same set must have a name starting with a common
root and the last three characters changing. There can be two types of sets;
sets made of three files and sets with more than three files.
Sets made of three files are used for representing High, Medium, Low status.
For example, a set of this type could be made of face001.jpg, face002.jpg,
face003.jpg.
When using this type of file set, the first image is used when the cell value is
smaller than the red threshold, the second image for intermediate values and
the third image for values higher than the green alert threshold.
Sets of four or more files, these sets are used for representing a multi-value
alerts. For example a set of eleven files, representing a dial indicator in
different positions: Dials000.jpg, Dials010.jpg, Dials020.jpg, &ldots; to
Dials100.jpg. The files of this type of set must be named from 000 to 100
(common root and the last three characters changing).
When using this type of file set,
174
Chapter 7 Capsules
if the cell value is smaller than the red threshold, the first picture is
displayed,
if the cell value is greater than the green threshold, the last picture is
displayed,
if the cell value is in the [red; green] range, the displayed picture is
the closer to the cell value evaluated as a percentage on the [red;
green] range. The percentage is evaluated using the following
formula: (cell value &endash; red value)/(green value &endash; red
value) * 100 .
Example of a gauge function using a set of three files,
Corresponding setup:
Corresponding setup:
175
Note! The format settings are applicable to the DataView object only.
Select the Default option to inherit the DataView format settings. Select the Custom option to set a
font type, color, size and cell background color.
The Checkbox option changes the appearance of the cell to a checkbox. If the cell value is zero, the
checkbox is un-ticked; if the cell value is different from zero the cell value is ticked. This format option
can be set on a data-entry column for entering a Boolean value 1 or zero.
Setting Axes
The Axes tab defines the aggregation level of data by selecting entities to set by row and by column.
Click on the desired entity then drag and drop it to the By Row or By Column fields. To remove an
entity set By Row or By Column, click on the entity and drag it to the recycle bin.
176
Chapter 7 Capsules
Master
Indentation
When two or more entities are set By row, the entities by row are
indented as in the following illustration.
Allows setting what entity fields should be displayed; the code, the
description or both. Click on the field to change the setting.
Show all
This option displays all rows or all columns including rows or columns
with zero values. By default this option is disabled for entities by row,
automatically hiding rows containing only zero values, and enabled on
entities by column.
Collapse
Totals alignment
This option applies to the DataView object having at least one entity
by column and provides three options for defining the positions of the
row total columns.
Align horizontally orThis option applies to the DataView and DynaSheet objects. By
default, the data blocks are aligned horizontally across columns
vertically.
(column a is the first column, column b the second column and so on).
When no entities are set by row, it is possible to choose the Vertical
alignment as illustrated.
Setting Filters
Filters allow defining rows sorting and two filtering conditions.
178
Chapter 7 Capsules
The left window lists the Layout data columns. To define sorting or a filter, click on the desired field
then drag and drop it to the Sort by field or to a Filter field.
when two filtering conditions are defined, they can be combined using the logical operations :
AND: requires that both filter A and filter B conditions are true.
OR: requires that at least one condition, filter A or Filter B is true.
The Keep top option allows to display a given number of rows. For example Keep top 10 will only
display the first 10 rows.
The Keep Totals option shows the total of the visible rows only. For example activating this option on
a layout having Keep top 10, will show as column total the total of the top 10 rows only. If this option is
disabled, the column total will be the grand-total of all report rows, calculated before filtering the
unwanted rows.
To remove a filter condition, click on the data column and drag and drop it to the recycle bin.
Notes!
Sorting and filtering conditions can be applied to numeric fields only.
If the Layout has one or more entities set by column, sorting is evaluated on the row
total column.
Filters cannot be applied if a ranking function is used.
Filters cannot be applied if there are more than two independent entities set by row.
A red light indicates that the Layout cannot be executed: this may be
due to an incorrect configuration or an inconsistency between the
InfoCube structure and the axes.
A green light indicates that the Layout view is based on a physical
179
The Select
OK button
Button
The Button object
Buttons can be used to create links to other screens or to launch a procedure. The action associated
to a Button is triggered only at runtime; design mode only allows configuring the button object.
Creating a Button
Select the button object from the toolbox then drag and drop it to the desired screen area. Right click
on the button object to configure it.
Button Appearance
The Appearance properties allow setting the button style and label.
180
Chapter 7 Capsules
Caption
Picture
BevelWidth, Border
Tool Tip
Button Actions
The Actions tab defines the button behavior: the action to execute when the user click the button at
runtime.
To go to another screen, select the screen name from the Next Screen drop-down list. Alternatively
you can use the choose function and define a selection of screens the user can choose from. For
example, choose(screen1, screen2) allows the user to jump to screen1 or screen2.
To launch a procedure select a procedure name from the procedures list. Note that it is possible to
select up to three procedures that will be executed sequentially from top down.
181
Clicking the Procedures button opens the procedures designer environment, where you can to create
a new procedure or edit and existing one.
Button Options
The Options tab contains the following settings
Confirm message
Password
Comment
AutoGo
182
Chapter 7 Capsules
Picture
The Picture object
The picture object can be used to add pictures or text labels to a Capsule screen. The picture object
supports the following file formats: GIF, JPG, ICO, BMP, WMF, EMF. The picture object is embedded
in the screen, when creating a Capsule accessed by remote users (connecting through a WAN or the
Internet) it is recommended using small image files and compressed formats (such as GIF or JPG).
Note that the Viewer object also can be utilized to add an image or a logo to a screen. The Viewer
object visualizes an external picture file (as well as other file types) that does not affect the size of the
screen Capsule.
183
Folder
The Folder object
The Folder object creates folders that can contain other objects from the toolbox (except for another
Folder object). When two or more folder objects are found on a screen, the tabs synchronize
automatically; for example clicking on the second tab of a Folder automatically sets other Folder
objects on the second tab as well.
Creating a Folder
Select the Folder object from toolbox then drag and drop it to the desired screen pane. By default, two
folders, named Tab0 and Tab1 are created.
Right click on the folder tabs to access the properties configuration.
184
Chapter 7 Capsules
Increase or reduce the number of tabs using the TabsNr field. It is possible to define up to 10 tabs.
You can customize the object by selecting one of the available Appearance, Orientation and
Style options.
To rename a tab, type the desired text in the corresponding text area. You can set the tab background
and font color by clicking on the F and B icons.
DataView
The DataView object
The DataView object is the main spreadsheet object for the creation of analyses. The DataView object
supports data-entry and a rich set of Layout and formatting options.
Creating a DataView
Select the DataView object from the toolbox then drag and drop it to the desired screen pane. Right
click on the object to access the Layout configuration. Refer to The Layout object section for details on
how to configure a Layout.
Data-entry features
Different features are available depending on the data type of the data-entry column.
To enter a value in a numeric column,
Click or double-click on the cell then type the desired number.
185
Formatting options
The Format tab allows defining the font, the color and other display options of the DataView
spreadsheet.
Default
Set Board's default grid and font and color and styles.
Dynamic
Allows to select a font type, font color and cell's background color to apply
to all columns and rows of the spreadsheet.
To select a font type click the Font button
186
Chapter 7 Capsules
This option allows to define a font style, color and cells borders and color.
The Static style is linked to the individual row and column where defined
therefore this option is appropriate for reports where the number of rows
and columns doesn't vary.
Headers
Displays the column headers. Note that when the headers option is
disabled (row headers are hidden), it is not possible to right-click on a row
header to access the drill-down window however if a drill-down path was
saved, you may drill-down on a row by double-clicking on the desired row
or double click on the desired cell.
Vertical scrollbars
Horizontal scrollbars
Cell Focus
Vertical grid
Horizontal grid
Drill-down on a cell
Double-click on a data cell to drill-down.
187
Graph
The Graph object
The Graph object allows you to create and format a wide range of charts, including 2D, 3D, and
stacked permutations of Bar, Line, Area, and Step charts. It also includes XY, Polar, Radar, Gantt, HiLo, Pie, Doughnut, Elevation, 3D XYZ, and 3D Scatter charts.
The Chart Wizard visually guides you through the process to create a new chart or modify an existing
chart. Alternatively you can use the Chart Designer, an richer and more detailed environment that
allows you to set advanced charting options and fully customize the chart text styles, fill patterns,
marker styles, as well as 3D rotation, perspective, lighting, and more.
A Graph object can be,
DataView Child Layout: This type of graph displays data from a DataView object present on
the same Capsule screen. This type of graph is linked to a DataView object that acts as a
parent to the chart object: when you click on a DataView row, the chart will refresh and display
the data from the clicked row.
Stand-alone Layout: This type of graph includes a Layout defining the data that chart data.
188
Chapter 7 Capsules
If the screen contains one DataView only, the graph is automatically linked to that DataView.
If there are several DataView objects, select the desired DataView from the Bound
DataView list box.
The left window lists the DataView columns (InfoCubes and calculated fields). Select the
columns you want to draw on the chart and drag them to the right window.
Select the option Data Series By Row to chart the data in the DataView rows &endash;you
can select this option only if the DataView has an entity set by column. Select the option Data
Series By Column to draw the chart from a column of the DataView &endash; you can
select this option only if the DataView has an entity set by row.
Click OK to close the configuration window.
If you selected Data Series By Row, click on a row from the DataView to draw the chart.
If you selected Data Series By Column, click on the DataView column to draw the chart.
189
Chapter 7 Capsules
The Designer's tree view outline allows you to select multiple chart parts and set properties for all
selected parts at once. To select a single chart element, click once on the element in the tree view. To
select multiple chart elements, hold down the CTRL key while clicking once on each element you wish
to select. When you select multiple elements only common properties are displayed.
The options you select from all tabs are applied to the chart when you click either the Apply or the OK
button.
Changes are not applied to the chart as you move from tab to tab. Only the Apply button or the OK
button will affect the chart.
The following illustration show how to set identical font style and size for the chart title, footnote and
legend.
The following illustration show how to set common background color for all Axis labels.
191
To apply an existing chart template to a graph object: switch to Design mode, right click on the Graph
object then select Templates/Import Chart from the menu.
The chart templates can be used to format Board Web query charts.
Chapter 7 Capsules
The GDE object is often used in combination with a master DataView object allowing to enter data in
an InfoCube in two ways: through the graph, to create a seasonality curve, then through the DataView
spreadsheet to refine the numbers set through the chart. The GDE and the DataView objects are
constantly kept synchronized: each object instantly reflects the changes made using the other object.
Example
193
Using a GDE
To enter a value, point the mouse on the desired bar. A horizontal dotted line indicated the Yaxis value of the mouse position. Click at the desired height then to save values to the
InfoCube, press the Save button or the F10 key.
194
Chapter 7 Capsules
Click on the reference value shown in the blue bar to equalize the red bar height to the blue
bar height. To save values to the InfoCube, press the Save button or the F10 key.
Mapping
The Mapping object
The Mapping object allows you to create bubble charts for positioning analyses. On a Mapping object
bubbles represent Entity items. Three data columns determine the bubble position (X and Y axes) and
the bubble radius.
Example
195
Creating a Mapping
To create a Mapping chart,
Select the Mapping icon from the toolbox then drag and drop it to the desired screen area.
Right click on the mapping chart, select the Stand-alone Layout option from the menu and
configure the Layout.
Three data columns are needed to draw the bubble chart. When configuring the Layout Axes
tab, set the entity to display as bubbles by row. Optionally, you can add a parent entity by row;
bubbles will be colored by groups of bubbles having the same parent.
In the by column axis of the Layout you can optionally set an entity that will be used as a
paging criterion in a drop-down list as illustrated.
Select the layout Graph tab and set the three data columns: the X-axis, the Y-axis and the
radius.
Click the OK button to run the Layout and draw the bubble chart.
Chapter 7 Capsules
Bubble information
Master
Data-entry
Animation
Gauges
Zoom
To zoom, click then drag the mouse in a diagonal capturing the bubbles you want to zoom on. The
occurrences captured by the zoom area become a selection and other objects on the screen will be
refreshed restricted to the selected items. To reset the zoom, click on the gray title bar of the mapping
chart.
Bubble information
Place the mouse pointer over a bubble to display the entity occurrence in a tool-tip box. Right click on
the tool-tip box to view parent entities (if they exist) of the clicked item.
Master
A Mapping object can be defined Master: select the master option found in the Layout Axes tab.
Clicking on a bubble of a Master Mapping refreshes the data displayed by other objects on the screen,
restricted to the clicked item.
When the Master option is enabled, the zoom function is disabled.
Data-entry
The Mapping object supports data-entry on the X and Y axes columns: if data-entry is enabled on the
data columns used for X-axis and Y-axis, you can move a bubble to a new position then save the
values corresponding to the new X and Y coordinates to the InfoCubes.
197
Animation
You can animate Mapping objects having a paging entity (i.e. there is an entity set By Column in the
Layout Axes tab). Click on the Motion button found in the top left corner; the occurrences in the paging
list box will automatically scroll.
Gauges
The Mapping bubbles can be replaced by gauges images, including animated GIF pictures. Define an
Alert (selecting the Gauges option) on the Radius data column: when the Mapping chart is drawn, the
gauges picture files are used instead of bubbles.
When
the number of animated GIF images is greater than 20, images are animated one by one.
Cockpit
The Cockpit object
The Cockpit object represents a numerical value using a needle indicator or using images, including
animated GIF pictures.
The needle indicator is divided into three colored sections (red, yellow, and green) defined by two
threshold values: the red-yellow threshold and the yellow-green threshold.
198
Chapter 7 Capsules
When the gauges option is used, the gauge image is used for representing the value.
The following illustrations are two Cockpit objects using gauges.
Creating a Cockpit
To create a Cockpit object,
Select the Cockpit icon from the toolbox then drag and drop it to the desired screen area.
Right click on the object, select the Stand-alone Layout option from the menu and configure
the Layout.
One data column is needed for the Cockpit. When configuring the data column to be used in
the Cockpit, go to the Alert tab and set the two thresholds in the red and green alert fields.
To use the gauges option, select Gauges from the Alert tab and type the gauges file name.
Refer to The Layout object paragraph for more details on gauges.
199
Go to the Layout Axes tab and set the entity to display as cockpit objects by row.
In the by column axis of the Layout you can optionally set an entity that will be used as a
paging criterion in a drop-down list box.
Select the layout Graph tab and set the data column to use in the indicator.
Click the OK button to run the Layout and create the Cockpits.
One indicator per each occurrence of the entity set by row is created. While in design mode, you can
click on an object and reposition it as desired. Save the Capsule to save the objects position.
Using a Cockpit
The cockpit object provides the following features,
Cockpit information
Master
Animation
Cockpit Information
Place the mouse pointer over a cockpit object or over a gauge picture to display the entity occurrence
and the field value in a tool-tip box.
200
Chapter 7 Capsules
Master
A Cockpit object can be defined Master: select the master option found in the Layout Axes tab.
Clicking on a cockpit (or gauge) refreshes the data displayed by other objects on the screen, restricted
to the clicked item.
Animation
You can animate Cockpit objects having a paging entity (i.e. there is an entity set By Column in the
Layout Axes tab). Click on the alert field name fount in the top left corner; the occurrences in the
paging list box will automatically scroll.
Alert box
The Alert object
The Alert object allows you to represent a numerical value using different alerting methods
The standard alert is a colored box that can turn red, yellow or green depending on two
threshold values.
The Area options extend the functionality of the alert boxes allowing you to fill an area of a
background picture with the color of the alert box placed over it.
Example of a standard object where alert boxes have been arranged over a background picture.
201
Example of the area feature: the background picture areas are filled using the alert box color.
Creating an Alert
To create an Alert object,
Select the Alert icon from the toolbox then drag and drop it to the desired screen area.
Right click on the object, select the Stand-alone Layout option from the menu and configure
the Layout.
One data column is needed for the alert. When configuring the data column to be used in the
alert box, go to the Alert tab and set the two thresholds in the red and green alert fields.
202
Chapter 7 Capsules
Area
When using the Area options select a picture having closed areas delimited by borders
that create a fair color contrast with the surrounding colors.
Go to the Layout Axes tab and set the entity to display as alert box objects by row.
In the by column axis of the Layout you can optionally set an entity that will be used as a
paging criterion in a drop-down list box.
Select the layout Graph tab and set the data column to use in the indicator.
Click the OK button to run the Layout and create the alert boxes.
One box per each occurrence of the entity set by row is created. While in design mode, you can click
on a box and reposition it as desired. Save the Capsule to save the objects position.
Note that if you selected an Area option, the coloring takes place only at while in runtime mode.
Using an Alert
The cockpit object provides the following features,
Alert information
Master
Animation
Alert Information
203
Master
An Alert object can be defined Master: select the master option found in the Layout Axes tab. Clicking
on an alert box (or an area when the Area option is used) refreshes the data displayed by other
objects on the screen, restricted to the clicked item. The Master Layout option can be combined with
the Area alert options.
Animation
You can animate Alert objects having a paging entity (i.e. there is an entity set By Column in the
Layout Axes tab). Click on the alert field name fount in the top left corner; the occurrences in the
paging list box will automatically scroll.
DynaSheet
The DynaSheet object
The DynaSheet is a spreadsheet object supporting multiple worksheets and providing a designer
environment that appears and behaves much like a commercial spreadsheet application.
Each worksheet of a DynaSheet can either contain a Layout definition and therefore displays
InfoCubes and entities data or it can be used to work freely as you would on a spreadsheet
application.
The DynaSheet object differs to the DataView in the following characteristics
The DynaSheet object does not support data-entry on InfoCubes.
The DynaSheet designer (or sheet designer) allows to type formulas in referring to other
worksheets and using typical spreadsheet functions
The DynaSheet provides a greater control over cells and sheets formatting options, setting
fonts, colors, borders and other style options.
The DynaSheet object has a print preview function.
The DynaSheet allows to read MS-Excel files and write files to various formats including MSExcel 97, tabbed text and HTML.
A DynaSheet worksheet is limited to 65000 rows.
Creating a DynaSheet
To create a DynaSheet object,
204
Chapter 7 Capsules
Select the DynaSheet icon from the toolbox then drag and drop it to the desired screen area.
A workbook with three sheets is created by default.
To define a Layout on a worksheet, right click and select Layout option from the pop-up
menu. Note that once you have set a Layout on a sheet you cannot use the worksheet to type
formulas or edit it freely.
To work on a worksheet, click on a cell and type the desired text or formula.
The workbook document is embedded in the screen; save the Capsule screen to save the document.
The Sheet Designer environment provides the menus and functions that are typical of spreadsheet
applications. You can, for example, open and save files in various formats (such as MS-Excel), create
new sheets, insert and eliminate rows and columns, change the format and color of the characters and
cells, etc.
205
DynaSheet options
Formatting Sheets
Worksheets where a Layout is defined are generated with a format similar to the standard DataView
reports.
You can modify the cell format of a worksheet sheet containing a Layout: right click on the DynaSheet
object, select Sheet Designer from the menu and. The formatting options that are accessible through
the menu Format/Cells are the only options that can be modified, with the exception of options from
the Numbers tab.
To save your formatting options, close Sheet Designer, click with the right button of the mouse on the
sheet, choose the Lock Sheet Format option from the menu then save the Capsule.
DynaWrite
The DynaWrite object
The DynaWrite object can be used to add text documents to your Capsule screens.
DynaWrite is a word processor environment. With DynaWrite, you can create and format text, manage
various character types, and insert tables and pictures. You can also open and save files in various
formats, including Rich Text Format (RTF), plain text (TXT), and HTML.
206
Chapter 7 Capsules
Viewer
The Viewer object
The Viewer object allows to visualize external files or a web site. The file name or the Internet address
can be
Static: the Viewer displays a file or web site page specified when creating Viewer the object.
Dynamic: the text column of a DataView object (present on the Capsule screen) determines
the file name or the web site address to view in the Viewer object. When you click on a row of
the DataView object the file or web page changes.
The Viewer is a polymorph object: when you create a Viewer you must specify a file or a web site
address to view and depending on the file type the Viewer assumes a coherent form. The following
types are supported:
A web site address or a HTML page: the Viewer instantiates an Internet browser object.
PDF files: the Viewer instantiates an Internet browser object.
An image files (JPG, GIF, BMP): the Viewer instantiates an Internet browser object.
Text and Rich Text Format files (TXT or RTF): the Viewer instantiates a DynaWrite object.
Microsoft Excel files (XLS): the Viewer instantiates a DynaSheet object.
207
Type a web sites address (or a URL), without the ”http:// prefix. For example
www.MyCompany.com
Or type a file name, including the file extension. Files addressed by the Viewer object must be
located in the \Board\Desktop directory of the computer where the BoardServer is running.
If you type a file name with extension RTF, TXT or XLS, and the file is not found in the
\Board\Desktop directory then Board creates it.
Note! For files of type RTF, TXT and XLS, the Viewer allows editing the file: while in
runtime mode you can modify the workbook or the text document and save changes by
clicking the save button found in the bottom toolbar.
Flowchart
208
Chapter 7 Capsules
The Flowchart can contain up to four Layout definitions. The boxes (rectangles, ellipses etc&ldots;)
can display a value from one of these Layouts.
The flowchart object also provides a table object that can display plain text (manually filled-up) or a
data column from one of the Flowchart Layouts.
The box objects can
Display a fixed text or a picture.
Display a value from a Layout of the Flowchart: an InfoCube or a calculated column, including
text columns and gauges.
Contain other toolbox objects: a DataView, a Graph, or any other object except for the
following: Button, Picture, Folder, Viewer and Flowchart.
You can also associate an action to a box, jumping to another screen or running a procedure,
obtaining the behavior of a button object: when the user clicks the box the action is executed.
Example
209
Creating a Flowchart
To create a Flowchart object, select the Flowchart icon from the toolbox then drag and drop it to the
desired screen area.
Right click on the flowchart object to access its properties definition window.
To draw a box, click on the flow chart then keeping the mouse button down, drag the mouse pointer
in a diagonal. Right click on the box to set its properties: shape color, actions etc&ldots;
210
Chapter 7 Capsules
To draw an arrow, click on a box then drag the pointer to another box (an arrow links two box
objects). Right click on the arrow to access its properties.
To add a toolbox object onto a box, select the desired icon from the toolbox then drag and drop it to
the desired box. The following toolbox objects can be placed positioned on a box: DataView,
DynaSheet, Graph, Mapping, GDE, Cockpit, Alert, DynaWrite and STO.
Note! Once an object from the toolbox has been places on a box, it is not possible to
draw arrows originating from that box. Draw the arrows before placing the toolbox
object.
211
Back color
Sets the background color. Click the ”as screen button to select
the screen background color.
Picture
Allows you to select an image file to use as background. Click the Clear
button to remove the background image.
Scrollbars
Shadows
Layout
Allows you to define up to four Layouts. The Box and Table objects can
display data from one of these Layouts. Note that you can use the Alert
functions (color coding or gauges) on the Layout data columns displayed
in Boxes or Tables: the box background color changes according to the
alert rule or the gauge image is displayed.
Add Table
Creates a table object that can display data from a Layout text (the table
can be manually filled-up). The Table object allows you to draw arrows
pointing to a specific table cell; this is not possible if you are using the
DataView or DynaSheet objects embeded in a Box (the arrow can only
point to the box border).
The Table object is a light object, requiring a small amount of RAM
compaired to the DataView and DynaSheet objects.
The Table object is suitable for simple reports, with a limited number of
rows and columns. It does not support drill-down and data-entry. It
displays a fixed number of rows and columns.
Right click on the Table object to define its properties.
212
Chapter 7 Capsules
Set the number of rows and columns using fields Row Nr. and Column
Nr.
To display a data column in the Table, select the Show Value option,
then select the Layout number (from 1 to 4) and the data block to display
(one of the Layout columns from a to z).
Shape
Select the shape from the list. Available shapes are: Rectangle Ellipse,
Rounded rectangle, Rhombus, Polygon, Delay, Button Container.
213
Transparent
Text
Text label. Nota that if the box is configured to display a Layout column
(using the Show Value property) this field is ignored.
Use the Aligment and Font butons to define the text properties.
Back color
Border color
Border width
Picture
Allows you to select an image file to use as background. Click the Clear
button to remove the background image.
Show Value
To display a data column from one of the available Layouts, click the
Show Value check-box then select the Layout number (from 1 to 4)
and the data block to display (one of the Layout columns from a to z).
Action
214
Chapter 7 Capsules
Clicking the
environment.
Procedure
button
opens
the
Procedure
designer
215
Creating a STO
To create a Simple Transaction Object, select the STO icon from the toolbox then drag and
drop it to the desired screen area.
Right click on the header area then select the Entities/Relationships option from the menu.
Start by setting the entities that will be displayed in the header part of the STO object: drag
and drop the desired entities from the left list box to the Entity list table (see illustration
below). Start by selecting the most detailed entity (for example Customer or Product) to
which the users may add new members then set the parent entities that need to be related to
the member from the input entity.
216
Chapter 7 Capsules
Only the entities found one level up the hierarchy should be selected. For example, if you select the
Customer (the detail entity) and add the City entity (a parent of Customer) then you should not add the
State entity (a parent of City): the indirect relationships Customer State will be assigned
automatically through the City State relationships.
For each entity, configure the following options
Insert new
Numeric
Edit Desc.
Capitalized
Let move
Show list
Click to allow viewing the entity occurrences list. If the Insert new
option is enabled ad Show list is disabled then the user will be able to
create new occurrences but not search or view the full list of
occurrences.
Whole list
Click to displays the full members list (all occurrences) ignoring the
screen selection.
217
Layout Nr
Trigger
Interactive Selection
By <&ldots;>
sparsity
In the Message grid, type the warning messages to display when a validation rule is not met.
The row number will be used the message identifier when defining the validation fields.
The STO header section is now fully configured. You must now configure at least one Layout.
Right click the header section and select the Layout option.
218
Chapter 7 Capsules
Configure a Layout with data-entry columns as desired, considering that the most detailed
entity selected in the header section will act as a DynaBar (a paging criterion) for the STO
Layouts.
Optionally set the validation rules by clicking the Validation field checkbox (see illustration
below). A validation rule is a calculated field, usually with an IF statement, that returns the
zero if the rule is met (the input value is valid) or the warning message row number when the
criterion is infringed. Validation fields are usually hidden in the Layout; click the Hide This
Block option to hide it.
Note that it is possible to create complex validation rules by nesting IF statements or referring to other
Layout columns containing IF statements, and then combining the expressions using the logical
operators AND and OR.
Note that the validation formulas are evaluated only when the end user enters numerical data, not
when text is entered on a text InfoCube.
219
The Choose( ) function allows you to specify a fixed list of input values the user can choose from.
When the choose function is used, the user can only select one of the values from the list.
Syntax:
Choose(value1; value2; &ldots;)
Choose(entity_name)
Optionally you can define a default value by adding the character ”> before the desired value.
Example using a list of values: choose(10; 15; 20)
Choose(10; >15; 20)
Will give the user the choice to select one of the three listed values and will default to the
value 15.
220
Chapter 7 Capsules
When the user clicks on a cell to enter a value in the InfoCube, a list-box with the specified
values will appear. The user can only select one of the available values from the list.
221
When the user clicks on a cell to enter a value in the InfoCube, a list-box with the entity
members of the Value list entity is shown. The user can only select a value from the listed
ones.
222
Chapter 7 Capsules
If you type a text string in the code or in the description field and then click the entity list-box,
Board will display the occurrences matching the given text, facilitating the search for a
particular occurrence out of a large list.
If present, make a selection from the entity defined as interactive entity selection.
Enter the desired data in the InfoCubes then press the Save Values button.
223
Note! The DS&S allocates summary values based on the underlying data proportions. It
is not possible to enter a value on a summary cell if the summary value is zero. The
data-entry InfoCubes are usually initialized through a procedure that feeds it with data
224
Chapter 7 Capsules
using a defined criterion such as ”copy last year data or ”apply a
forecasting function or some other user defined method.
Note! That the DS&S feature is available on all objects supporting data-entry: DataView,
GDE, Mapping and STO.
Inverse algorithm
The inverse algorithm allows you to enter data to an InfoCube by typing a value on a calculated
column. The calculated column should contain two formulas, the standard one and the inverse formula
that defines the data-entry InfoCube column as a function of the calculated column.
The inverse algorithm is often used in conjunction to the DS&S feature.
225
Click the Allow changes check-box on the calculated column to allow data-entry.
Note! The inverse algorithm feature is available on all objects supporting data-entry:
DataView, GDE, Mapping and STO.
226
Chapter 8 Procedures
About procedures
A procedure is made of a sequence of actions that are executed sequentially. Board provides a wide
variety of actions allowing you to run database maintenance tasks or run data processing required by
your analytical application, for example running a cost allocation procedure or a planning simulation
and so on.
The elementary steps of Procedures are called actions. An action can run a Data Reader or a Batch
Reader, run a calculation on an InfoCube (a DataFlow action), print reports or broadcast reports via
email, extract some data from the Board database etc. Some action can require user interaction, for
example requiring the user to make a selection on an entity before running a calculation.
Procedures are stored into Capsules. A Procedure can be
Interactively launched by a user (clicking on a button linked to that procedure)
Executed automatically when a certain screen is opened
Executed as a batch process, launched from a command line or by a scheduler.
When a procedure is launched, it inherits the DynaBar and the screen selections.
Creating a procedure
227
Define the desired actions then click the Quit button to close the Procedure Designer.
Click the Save Capsule button to save your Procedure.
Moving an action
You can move Actions defined in procedures rows. Right click on the action to move then drag and
drop the curson on the new line.
Actions reference
228
Chapter 8 Procedures
Goto
Screen
Capsule
Exit Procedure
Exit Capsule
Select
230
Chapter 8 Procedures
The Select action allows you define a selection that will remain active until another Select action is
made. Each select action replaces the previous selection.
When a procedure is launched it inherits the Select and the DynaBar selections from the screen. Lets
suppose, for example, that a screen has been designed to enter a percentage for calculating sales
commissions and contains a button that runs the actual calculation procedure. The procedure consists
of a single process action that multiplies the Sales InfoCube by the Commission Percentage InfoCube.
If a selection is made before launching the procedure the process will run on that selection.
Select
Reset to Screen
Reset to All
Interactive Selection
Process
Allows you to
Define calculations on InfoCubes, for example to run a cost allocation model or a budgeting
simulation model that take as input some InfoCubes, apply a formula and store the result into
another InfoCube.
231
Data Flow
InfoCube Align
InfoCube Clear
Allows you to clear in InfoCube. All cells of the InfoCube are cleared,
considering the time selections only: selections on entities other than time
are ignored.
Entity Clear
232
structured by
by
(Year, Product)
by
Chapter 8 Procedures
To calculate the Cost of Goods Sold as a product of the Quantity sold times the Standard Product
Cost, define the following process:
(a) Quantity
(b) Standard Product Cost
(c) Cost of Good Sold = a*b
BOARD checks the structural congruency before running the calculation: the Quantity and Cost of
Products Sold InfoCubes are based on Month, and the Standard Product cost InfoCube is based on
Year. Board automatically uses the Month-Year relationship to perform the operation between
InfoCubes having a different structure.
The calculation will take place as follows:
”For each Month, Product, Customer combination, multiply the Quantity by the Standard
Product Cost for the relative Product in the Year to which the Month belongs.
The automatic use of relationships is not limited to Time Entities, and will be applied to any
relationship defined in the database.
The following rules apply to a DataFlow calculation:
The evaluation of the formula always takes place at the aggregation level of the target
InfoCube. If one or more InfoCubes involved in the formula have different structures than the
target, they will be brought to a congruent level before the formula is evaluated, according to
the following rules:
When a factor has one dimension that the target InfoCube doesnt have, it will be aggregated.
For example: The factor InfoCube is structured by Customer/Product/Month and the target
InfoCube by Product/Month. Before the calculation is run, the factor is aggregated for all
selected Customers.
When the target has a dimension that a factor doesnt have, the factor value is repeated for
each member of the exceeding dimension of the target. For example, if one of the factors is
Commission Percentage, structured by Salesperson/Month, and the target is Commission
Percentage, structured by Salesperson/Product/Month, the same Commission Percentage
value will be repeated for each Salesperson/Month for all Products.
When a factor is structured by a more detailed entity than the target, the factor is aggregated
to the same level of the target. For example, if one of the factors is structured by
Product/Month, and the Target is structured by Product/Quarter, then the factor will be
summed by Quarter through to the Month-Quarter relationship.
If a factor is structured by a more aggregated entity than the target, the value of the parent
occurrence is determined through the parent-child relationship. For example, one factor is
%Royalty structured by Product Brand/Year, the target is Royalty Value structured by
Product/Month, and there is a relationship Product Product Brand. The %Royalty value of
the Brand will be applied to each Product based on its Brand.
If the target InfoCube has a sparse structure, the calculation takes place for the existing
sparse combinations only. At least one calculation factor must be structured with either the
same sparse structure as the target, or a sparse structure that is more detailed than the
sparse structure of the target. For example, a sparse structure consisting of
Customer/Product/Depot is more detailed than the sparse structure made up by
Customer/Product.
The Dynamic Offset is a Data Flow function used to shift InfoCube values in time. The shift can be
absolute, based on a specific date (Absolute Offset option), or relative (Relative Offset option), shifting
values forward or backward for a given number of periods as specified by values in another InfoCube.
The Dynamic Offset function is located in the Advanced setup tab.
233
Based On &ldots; field: Choose the InfoCube that specifies the offset from the pull down list.
Relative Offset: Shifts InfoCube values in time based on the number of periods specified in the
InfoCube indicated in the Based On field. The time shift can occur either forward (Forth option) or
backward (Back option) from the previous period. To use the Relative Offset option, the Based On
field must refer to an InfoCube containing integer values.
Absolute Offset: Shifts values to the date specified in the InfoCube indicated in the Based On field.
Print
The Print action allows you to print an object present on the current screen. Select the desired object
from the list: a DataView, DynaSheet or Flowchart.
234
Chapter 8 Procedures
If an entity is present in the DynaBar you can select it from the Page Break option to create a printout
for each occurrence of the selected entity.
The Screen Hardcopy option allows you to print the Capsule screen to a printer or to a file (Bitmap
or JPG file). The files are created in the Board.Loc\Desktop directory.
Launch
The Launch action allows you to run a command.
Data Read
The Data Read action launches one of the following actions
Data Reader protocols
A Batch Reader procedure
Run the relationships Normalize function.
235
Data Reader
Select the protocol name from the list. If you select an ASCII protocol,
choose the file to read from the Path/File list box. Note that the files
listed are on the computer where BoardServer is running.
On error
Stop: causes the Data Reader protocol to stop in case a reading error
occurs.
Continue: the Data Reader rejects the violating record and continues
reading the next record.
File Missing
Stop: interrupts the procedure if the source file or table doesnt exist.
Continue: if the source file doesnt exist the process continues with the
next action.
236
Log File
Creates a log file with the rejected records; when all source records are
read successfully no log file is created. The log file is created in the
Board\Dataset\databasename directory.
Batch Reader
Normalize tree
Select a hierarchy from the list. This action runs the normalize function
on the selected hierarchy.
Chapter 8 Procedures
Xtract
File Printout
237
More
The More action tab contains miscellaneous actions.
Wait
Refresh Screen
Generates a screen refresh: all Layouts present on the screen are reexecuted.
Show message
238
Chapter 8 Procedures
239
240
241
Notes on Security
BoardMaster provides a standard HTTP service; it does not include a firewall. If you are installing
BoardMaster on a computer connected to your company Local Area Network (LAN), and accessible
via the Internet, it is strongly recommended to install a firewall (a hardware or software layer) to protect
the LAN from undesired external intrusions.
BoardMaster can run, use a standard HTML protocol or the HTTPS protocol providing data encryption.
Getting started
Installation and overview
The main steps to install and configure your Board Web server application are:
Run the BoardServer setup and the WebKitSetup installation programs. Note that this section is
not an installation guide; you must read the Installation chapter for details on the installation
procedure.
Install your Board license. Refer to the Licenses chapter for details.
242
243
244
Directory structure
Web navigator
Example:
Create the directory named Sales Location as a subdirectory of BoardPub\Root_WEB, and then
include a BOARD web query definition file named ”Sales by Territory.txt. Restart Board Web
service and the navigator will include the new folder and analysis names.
245
It is possible to hide a folder to a user group. Create a file named [UserGroup].out (where
UserGroup is the name of a user group) in a directory to hide that directory to the specified user
group. The user group is defined in the account definition, as illustrated.
For example, if you create the file Division1.out in the directory \BoardPub\Root_Web\Sales,
users of the group Division1 will not view the ”Sales folder. Note that you can include several
files with extension out in a directory to restrict access to more than one user group.
The Query Builder shows the definition of the last Board Web query that was executed or is blank. The
Query Builder page is illustrated hereafter.
Go to the Axes tab and set the entities to display by row, by column, by page and define the
drill-down paths
248
Go to the Options tab and type the title for the current table.
Go to the Chart tab and add a chart if desired. It is possible to define up to three charts per
Layout.
249
Click the Options button to set more options such as the main title, subtitle, comments and
the Main Selection, which is a selection applying to all Layouts of the Web query.
250
Type the query name in the Title field, select the folder in which to save the query and press the Save
button. Note that by default the query is saved to your personal folder. Saving the query in a different
folder will make it available to other users.
The New folder button will allow you to create a new folder.
The Edit button will allow you to view and edit the querys script.
Warnings!
After saving a new query, you may have to press the Refresh Tree function in order to
view it in the navigator tree.
Column algorithm
252
Ranking function
Entities&Relationships
Allows you to select an entity from the list. From the drop down
list to the right you can select the entity fields to display; the code
part, the description part or both.
Heading
Width
Dec digits
Divide by
No totals
Allow changes
Enables the data-entry on the InfoCube. Note that data entry can
be enabled only under the following conditions:
- The Layout should only have a single entity by row.
- data entry is permitted only at the InfoCube physical level.
- If the Layout includes more than one data column, there cannot
be entities set by column.
- If an entity is set by column, the Layout can only include one
data column.
- The query cannot be multi-table.
Recalc
Recalculates the totals using the formula. This option applied only
to column algorithms. Enable it for example when the column
contains a percentage formula; by setting this option the totals cell
is calculated applying the percentage formula to the totals cells of
the data columns used by the formula.
Sort
Sets the sorting option. The sort option can be set on one data
column only.
Function
Filter, allows you to define a minimum and maximum value for the
data column. Note that it is possible to set a maximum of two
filters on a Layout. When you define two filters (on the same data
column or one filter on two different data columns), you must set
the AND or OR operators defining how the two filtering conditions
combine.
Note that Filters can be defined on numeric data columns only:
numeric InfoCubes or algorithms.
The References tab holds the Total by, Detail by and Refer to functions.
Total By
Click the selection button and select the entities defining the Total
by condition.
Detail By
Click the selection button and select the entities defining the
Detail by function.
Refer To
Click the selection button and select the entity and entity member
to refer to. Up to three -Refer to- conditions can be defined.
The Alert tab sets the red/green alert thresholds and the gauges function. To enable the Alert function,
select the Color Coding or the Gauge options.
254
Blocks
Gauge
The Axes tab allows you to define the row, column and page entities.
255
Show all
Enable this option to view all rows of the report, including rows
where all values are null (or zero). This option is usually enabled
on data-entry queries.
Keep Top
Autorefresh
Title
Master
This option allows you to drill from one Layout to other reports. It
applies to multi-table queries only. When the query is executed,
only the master table is visible and by drilling-down on a row, the
other tables of the query are executed limited to the entity item
from master table.
Hide Table
Hides the table; this option is generally used when a chart has
been defined and you do not wish to view the table linked to the
chart.
Cell border
Title
Subtitle
Note
Backcolor
Style CSS
Picture
Allows you to select an image file to include into the query page.
Image
files
must
be
located
in
the
directory
BoardPub\Root_Web\Pictures .
257
Hyperlink comment
Menulist
Menulist Title
Selected Procedures
Metabody
Allows you to insert a text in the body tag of the HTML page.
Refer to the Board Web Script commands reference section for
details on the Metabody tag.
Metahead
Allows you to insert a text in the head tag of the HTML page.
Refer to the Board Web Script commands reference section for
details on the Metahead tag.
Display script
Displays the query script in the query page. The script appears in
a text area at the page bottom and can be edited online.
258
A page with the message ”Please wait&ldots; appears immediately: the BoardServer is
retrieving data. When the result is ready it will automatically appear in the main page.
Changing page
Queries can have one or more entities set as paging criteria. To change page, select the desired item
from the drop-down list then press the Refresh button.
259
Some queries can have an Autorefresh option which automatically re-runs the query on the item as
soon as the user has selected it. The Autorefresh option can be set from the Axes tab of the Query
Builder.
Changing selection
To change selection of a query, click the Select icon located in the lower part of the navigator.
The Select page shows the database entities list. To make a selection,
Click on the desired entity in the left column to view its members
Highlight the desired items from the entity members list. To make multiple selections, keep
the Crtl key pressed. To make a multiple selection of contiguous items, keep the mouse button
pressed and drag the mouse down
Click on the right arrow to add the desired members as illustrated.
260
After making the desired selection on all entities, press the Refresh button to re-run the
analysis.
Note! The entities having a large number of members may not be available. This occurs
for entities exceeding the Entity Cut-off parameter found on the BoardMaster Web
configuration.
Note that the MS-Excel file only contains data extracted from the Board database in a grid format.
Charts, images hyperlinks and other HTML content are not reproduced in the file. To save a query
with its entire HTML content, use the Internet browsers File/Save as menu option.
Note! To go back to the previous level, click the browsers Back button.
For drill-trough protocols three dots ”&ldots; are the prefix to the protocol name.
Printing a query
To print a query or a graph, use your Internet browsers printer icon or Print menu option.
Total value with proportional allocation. Enter a value in a row total, column total or grand total cell.
This value is then proportionally allocated to the lines using the existing proportions
(weightings)&endash; similar to the DS&S feature of the DataView.
262
Constant value options. On numeric InfoCubes, and only on data entry queries including a single
InfoCube, it is possible to insert values into the field named TOTAL, with the following syntax and
semantics.
= value
+ value
263
&endash;
value
* value
Multiplies the values of all cells of the report by the given factor.
Example: Typing *2 on the TOTAL cell multiplies all values of the report by
2.
Tip! To increase all values by a percentage factor n, multiply values by 1.n
Example, to increase values by 15%, type *1.15
/ Value
Divides the values of all cells of the report by the inserted factor.
Example: Typing /2 on the TOTAL cell divides all values of the report by 2.
264
265
By default, the template file is saved in the directory \Board.Loc\Templates\Chart (on the
computer running the BoardClient). In order to make the template available to Board Web users, copy
the template file in the directory \BoardPub\Templates\Chart of the computer where the
BoardMaster is running.
To use a chart template in a Board Web query:
open the Query Builder then go to the Chart tab and click the advanced chart options button
as illustrated
266
Note! Not all browsers support the space character in URL addresses, if the path and file
name include spaces, use the sequence %20 instead of the space character.
For example, dont use
/execquery.hdoc?id=/Sales/Month to date Sales
use the following syntax
/execquery.hdoc?id=/Sales/Month%20to%20date%20Sales
http://[BoardMsaterAdress]/SelectShow.hdoc
267
To call the Select function limited to time entities only use the following
URL
http://[BoardMsaterAdress]/SelectTime.hdoc
http://[BoardMsaterAdress]/DownloadXLS.hdoc
http://[BoardMsaterAdress]/DexA.hdoc?id=DatabaseName
HTTP://[BOARDMSATERADRESS]/BQS.HDOC
HTTP://[BOARDMSATERADRESS]/REFRESHTREE.HDOC
http://[BoardMsaterAdress]/WebBriefing.html
Tip! To simplify writing the query definition, use the online Query Builder to create the
desired query, then edit the script using a text editor and refine the script by adding the
desired commands and options that cannot be configured through the online Query
Builder.
Notes!
Script commands are not case sensitive; fonts are used to make a script easier to read.
In the examples, script commands and options are courier new bold.
Parameters included in square brackets [..] are optional, but do not type the brackets
when used.
Refer to the Board Web Script commands reference for the list of commands and commands syntax.
Master
Heading
Defines the table header (title displayed above the table in the
HTML page)
NoBorder GraphOnly
Graph,
GraphOnly,
QueryEdit, Preserve
Show,
Table
Dtb Sales
ByRow Product
Show Gross Sales, colhide sort
Show Vertical%, dec2
Keep Year=2001
Notes!
It is not possible to use have data entry tables or include procedures in multi-table queries.
The DrillBy command can only be used on a single table other than the Master table.
The Dtb command may appear in the first Table definition only, in this case the same
database is considered for all tables.
The command Master can only be set on the first table of a multi-table query.
Procedures
A Board Web query can include the run command to launch the execution of a Board Procedure
defined in a Capsule. It can be useful to combine a procedure to a data-entry query. For example, a
query that allows users to enter a budget quantity could include a procedure that immediately runs a
procedure that multiplies the Quantity and Price to obtain the budget amount.
Command syntax
Run ProcedureName
IMPORTANT! The procedure invoked must be defined in a Capsule located in the Main Capsule folder
on the server, and the Capsule must have the same name of the database.
Example
Dtb Sales
Run Increase Budget by 10%
Run Reduce Budget by 10%
ByPage -Year, State
Show Gross Sales
Show Budget
ByRow City
ByCol Month
A query script can include one or more Run command lines.
Three different execution modes are available. The execution mode is defined in the Opt line of the
query.
None
When no options are specified, the procedure is executed on the server and while
it is running the browsers ”waits for its termination; the mouse pointer
displays a small hourglass until the procedure is terminated. When the procedure
completes execution, the message ”Done is returned to the browser (or
”Error if some errors occurred).
Batch
This option can only be applied in conjunction to a Data entry query. The
procedure/s is/are launched automatically whenever the user enters (and saves)
data in a data-entry cell.
Trigged and Batch options can be specified both in a script, it combines the effect
of the two execution modes.
Procedures are executed within the range specified by the script (in the Select or Keep or ByPage
statements). If the procedure contains a Select action, it will prevail over the script selection. When
creating the Capsule on the server it is recommended to avoid defining selections on the Capsule
screen.
Note! A procedure that executed from a browser cannot include interactive actions, such
as Interactive Selection, Print or similar actions.
272
Object
BODY
BODY.Background
P.MainTitle
P.SubTitle
P.MenuList
SELECT.MenuList
TABLE.MenuList
P.PageBy
SELECT.PageBy
P.TextNote
IMG.Drill
IMG.Img01....Img09
IMG.MenuList
IMG.WebPicture
INPUT.Execute
INPUT.MenuList
INPUT.Refresh
INPUT.Reset
INPUT.Save
INPUT.Numeric
INPUT.NumericTotal
TABLE.Data
TABLE.Procedure
TR.ProcedureVA
TR.HeaderVA
TR.GroupHeadVA
TR.GroupTotalVA
TR.RowVA
TR.TotalVA
TD.ProcedureLogo
TD.ProcedureName
TD.ProcedureInput
TD.ProcedureExec
TD.ProcedureError
TD.HeaderName
TD.HeaderCol
TD.HeaderTotal
TD.Group1Head &ldots;..Group9Head
TD.Group1HeadName&ldots;&ldots;.
&ldots;..Group9HeadName
TD.GroupTotalName
TD.GroupTotalData
TD.GroupTotalTotal
TD.Hyperlink
TD.MenuList
TD.RowName
TD.RowData
TD.RowDataGreen
TD.RowDataGreenBlock
TD.RowDataRed
TD.RowDataRedBlock
TD.RowTotal
TD.SubTitle
TD.TotalName
TD.TotalData
TD.TotalTotal
(corresponding to a report)
HeaderCol column of each Table.Data
HeaderTotal column of each Table.Data
Header columns for groups 1 to 9
Title header column for groups 1 to 9
Column name of the total row, of the group.
Data column of the total row, of the group.
Column total of the total row, of the group.
Hyperlink style.
MenuList row text.
Column header name of the detail rows of a
report
Data column of the detail rows of a report
Data column of green cells deriving from the
alert function.
Data column of green cells deriving from the
alert on blocks function.
Data column of red cells deriving from the alert
function.
Data column of red cells deriving from the alert
on blocks function.
Totals rows of a report
Subtitle row
Header column of the totals row of a report
Totals row of a report
Grand total row of a report
A tree folder.
A tree item.
274
Optional parameter. Alias of the folder containing the database. When omitted
the value Main is assumed.
DatabaseName
Example:
Dtb main, Gamma
Select
Select EntityName = codes or description list
Synonym: Sel
This specifies the selection and must be followed by the name of an entity, then the equal or the space
character, and then the list of items to select separated by a comma. Both the codes or descriptions of
an entity can be used. The specified values are searched on the entity code field first then on the
description field.
Example:
select City=San Diego, New York
Selections on Month entity can use the format YYYYMM or MMM.YY:
Select month=200001
Select month=Jan.00
Note!
A script can include several Select lines.
On time entities, it is possible to select a range using:
Select FirstOccurrence to LastOccurrence
When using the to command, the time entity code must be used, i.e. for the Month entity, use
the format YYYYMM, for the Year entity use the format YYYY etc.
Example: to select months from January 2000 to June 2000
sel month =200001 to 200006
Show
Show InfoCube [, properties]
Show algorithm [, properties]
Displays an InfoCube, an algorithm or an entity. Can optionally be followed by the comma and a list of
properties to apply to the column.
Note! The order in which properties appear is not relevant.
275
Sort ascend
DecN
colhide
/nnn
ZeroOn
AsText, asDate
asPicture
DataEntry
276
@pp
@py
@ycv
@ymt
@yma
@trend
@forecast
Last Value
offset
Cycle
Filter(conditions)
DetailBy entityName
277
Width
Examples:
ByRow
ByRow Entity Name, &ldots;
Specifies which entities should be displayed by row in the report. Use the comma character as a
separator to specify more than one entity name.
Example:
ByRow Region, City
ByCol
ByCol Entity Name, &ldots;
Specifies which entities should be displayed by column in the report. Use the comma character as a
separator to specify more than one entity name.
Example:
Bycol Month, Quarter
ByPage
ByPage Entity Name, &ldots;
Specifies which entities should be displayed by page in the report. Use the comma character as a
separator to specify more than one entity. When two or more entities of the same hierarchy are
present, the parent entity should come first.
Example:
Bypage Year, Month
Drillby
DrillBy Entity1, Entity2, EntityN, .. Drill-through protocol&ldots;
Defines drill-down option paths. Use the comma character as separator to specify more than one
entity name. Drill-trough protocols can also be specified. To specify a drill-through protocol type
&ldots;protocol name.
Example:
DrillBy Region
Only one drill-down option (the entity Region) will be available to the user.
Drillby Region, City, Customer, Product Group, Product, &ldots;DrillThru-to-Invoice
The user will be given the option to drill-down to any of the listed entities and to drill-through using
the protocol DrillThru-to-Invoice.
278
Graph
Graph [type] [data series] [width] [height]
Creates a graph displayed above the report. By default, a line graph is created by plotting values from
the last row of the report (generally the Totals row).
Optional parameters
Type
When omitted, the default type is Line. The following types are supported:
Line, Bar, Pie, Area
2D
data series
When omitted, the data series for the graph are assumed to be by row. To create
a graph with data series by columns use the command:
OnColumn
Width N
Height M
Using
Specifies a chart template file that defines the chart style. The chart template file
must be located in the directory BoardPub\Templates\Charts
Detail
Creates a multi-line graph, plotting on the graph one data series for each row of
the report. This option can be used only on tables having one column, one entity
ByRow and one entity ByColumn.
Options
Opt [parameters]
Specifies optional parameters for the query, as follows:
AllRows
Displays all occurrences of entities set ByRow, including lines where all values are
null or zero &endash; by default, lines that have all null or zero values are not
displayed.
ShowAll
KeepTop
Filters lines of a sorted report and displays only the specified number of lines.
Example:
The following query orders Customers from high to low then displays the top 20
Customers.
Dbt Gamma
Show Sales Values, sort
ByRow Customer
279
Displays the query script in the results HTML page, under the report table or graph.
The script can be edited and the query can be re-launched but changes are not
saved to the server. To save changes, the Query Manager must be used.
EditQuery
Synonym of EditQuery
NoTable
Hides the table containing the report data. This option is generally used in
conjunction with the Graph statement. It is functionally equivalent to the GraphOnly
statement.
TableHide
Synonym of NoTable.
HideTable
Synonym of NoTable
Graphonly
Shows the graph only and hides the corresponding source table. This option can be
used only if the query includes a Graph command.
DataEntry
Run
run [procedure name]
Allows the user to run a Capsule Procedure. A query script can include multiple run command lines.
The specified procedure must be defined in a Capsule located in the Main folder and having the same
name of the database.
Backcolor
Backcolor [color]
Determines the page background color. Recognized values for this option are grey, lightgrey, white,
blue, and green.
MenuList
280
”comment
subtitle
Text that is displayed in black medium font under the main title.
textnote
Text that is displayed in small black fonts. The text can be multi-line text.
Note! This command must be the last command of the script.
webpicture
Specify the file name of a picture to include in the page. Image files must be
located in the sub folder \BorardPub\WebPic.
hyperlink
Includes a hyperlink to a URL. Optionally after the URL, type a comma followed
by the text for the hyperlink.
Example:
dtb gamma
byrow City
bycol Month
show Gross Sales
Select Year= 2004
maintitle Monthly Sales of 2004 per City
webpictire Logo.gif
subtitle Geography split by City
hyperlink www.mycompany.com
textnote Sales figures refer to invoiced value before returns
StyleSheet
StyleSheet filename
Allows you to reference a Cascading Style Sheet (CSS) file. The CSS file must be located in the
BoardPub\RootWeb directory.
MetaHead
MetaHead Text..
281
MetaBody
MetaBody Text...
Allows you to insert a text string within the body tag of a Board Web query HTML code.
For example, you may invoke a javascript function on the OnLoad event of your Board web query
page.
metabody onload="JavaScript:MyFunction();"
Open BoardMaster, go to the WEB tab and click the "SSO, SSL" button
On the SSO configuration window, click the button named "Create SSO File" as illustrated
283
A message box will indicate that the BoardSSO.txt file has been created. This file is the
private KEY used to encrypt the cookie content which you will need to copy on the server
performing the authentication. The file is a plain text file containing a random sequence of 65
characters. The BoardSSO.txt file is created in the System directory, which usually is
c:\WinNT\System32 or c:\Windows\System32.
You have completed the setup Board WebServer for SSO, you now need to set up the process to
create the BoardSSO cookie on the server that performs the user authentication.
Add to your Web application, a piece of code that, after the user has successfully
authenticated, will create a cookie with the following contents:
BoardSignOn = [the encrypted username and password];
Domain = [domain name, for example mysite.com];
Expires = [cookie expiration time in milliseconds];
Path =;
Note that instead of writing your own code you can use the Java Class or the ASP page
provided as examples in following sections.
To encrypt the username and password use the followign algorithm:
Example:
284
For each letter of the username, convert it to its ASCII value and add this
number of the ASCII value of the letter found in the same position in the
BoardSSO.txt file.
after encrypting the last letter of the username, add the character *
(asterisk) as a separator,
expires="
strID = Request.Form("ID")
strPwd = Request.Form("PASSWORD")
' Authentication
' If OK then calls Java class and writes the cookie
if ( strAuth = "ok") then
strParEnc = objBoardSSO.Encrypt(strID,strPwd)
%>
<SCRIPT LANGUAGE="JavaScript">
SetCookie('<%=strParEnc%>');
</SCRIPT><P>
<a
href="http://BoardWebServer.MyCompany.com"><h1>Redirect
WebServer </h1></a>
to
Board
<%
end if
%>
</FORM>
</BODY>
</HTML>
286
import java.lang.System;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
public class BoardSSO
{
public String Encrypt(String uid, String pwd) throws IOException
{
FileInputStream pKey = new FileInputStream("BoardSSO.txt");
int inBytes = pKey.available();
byte inBuf[] = new byte[inBytes];
int bytesRead = pKey.read(inBuf,0,inBytes);
String encode = new String(inBuf);
String pRes = new String();
String pCon = new String();
int base;
int shift;
int decode;
for(int i=0;i<uid.length();i++)
{
base
= (int) uid.charAt(i);
shift
= (int) encode.charAt(i);
= pCon +
decode;
= pRes +
decode;
}
pRes = pRes + '*';
for(int i=0;i<pwd.length();i++)
{
base
= (int) pwd.charAt(i);
shift
= (int) encode.charAt(i);
pCon
= pCon + decode;
= pRes +
decode;
}
return pRes;
}
public static void main(String args[])
{
/*
}
}
288
*/
Release Notes
Release notes for version 6.1
Upgrading to version 6.1 instructions
Client-Master-Server compatibility
The BoardClient version 6.1 must connect to a BoardMaster of the same version and vice-versa.
It is recommended to upgrade to version 6.1 the server running the BoardMaster and then deploy
BoardClient version 6.1 to all client PCs.
Notes
When upgrading a PC or a server from any earlier version you must not un-install the Board
license. All currently installed licenses (version 6, version 5 or version 4) are fully compatible
with version 6.1 therefore after running the BoardClient or BoardServer installation programs
you can start using version 6.1 immediately.
It is possible to run the installation procedures as a background process that doesn't require
any user interaction (this technique is referred to as "silent mode" install). Refer to the
following knowledge-base article for details: How to run Board Setup in silent mode.
289
290
Release Notes
The profiles list can be sorted by clicking the Sort button and searched.
To add a new profile, click on an empty row in the Profile table (left-hand side) then define the
profile settings on the right table.
To delete an existing profile, delete the profile name from the right-hand side table.
Note that if the username is not found in the chosen entity members then 0 members are
selected therefore all InfoCubes having a dimension linked to the dynamic selection entity
become inaccessible.
291
When word wrap in enabled, the row height is adjusted to fit the entire text contained in the
cell which would otherwise be truncated.
292
Release Notes
To import data from ODBO data source,
define the ODBO connection string using the OLE-DB Wizard and connect to the
ODBO data source,
the list of cubes present in the data source is shown in the RDB window (where the
list of relation tables is usually displayed for ODBC providers)
Select Board's InfoCube and entities to feed (or to map in case of an RDB
InfoCube). Note that it is only possible to feed (or map) a single Board InfoCube in a
protocol.
Drag and drop the dimensions and measures of the ODBO data source in the same
way you drag & drop table fields in an ODBC protocol.
the code part of a Board entity is populated by retrieving the unique ID of the
member from the corresponding MXD field,
the InfoCube must be the last field in the protocol definition and the MDX
statement must return one measure only,
if you include in the protocol both the code and description of an entity, they
must be one after the other.
293
Release Notes
It is also now possible to deny to users having a Lite or LitePlus license access to the
DynaWrite++ or DynaSheet++ environments, to do so, go to the Options tab of the
295
296
Security. An error that could cause the unauthorized access to the database security panel of users
having a Lite+ or Lite license has been fixed.
System robustness. The communication protocol between the BoardClient <--> BoardMaster <-->
BoardServer programs has been changed and optimized to provide stronger robustness. The
capacity of the BoardMaster in handling a large number of simultaneously connected users has
improved. The auto-resume function has also been improved in robustness and sophistication, the
system is now able to grant higher availability rates on highly concurrent systems.
STO. When, while entering data through an STO object, a validation criterion is not met (therefore
saving is refused), the STO data in the Dataview is no longer refreshed even if the "Refresh" option
is enabled, so that the data which has been input isn't lost and can be corrected.
Datareaders and MXC Infocube. An error caused by the execution of a Datareader having one or
more entites with Append and without Infocubes launched immediately after another Datareader
feeding an MXC Infocube has been fixed.
WEB. When using Board web Server with the HTML theme (this setting is located in the
BoardMaster's Web tab), the drill-down icon was incorrectly displayed also on the totals row (which
cannot be drilled) for databases where the time range language was set to any language other than
English.
WEB. An error of the data dictionary translation (Language DD) function in the Web environment has
been fixed.
BoardClient configuration window. The text field "Write program path" where to type the path
of the default word processor program has been increased in length.
New screen. When attempting to copy a screen from one Capsule to another, if the target Capsule
already contains a screen having the same name of the copied screen a warning message now asks
to confirm the action before replacing the target screen.
Procedures copy. An error provoked by the copy of a procedure between two Capsules having the
same name but located in different folders has been fixed.
Capsule save. A case of possible loss of the procedures, occurring when saving a Capsule after
accessing a database design function, has been fixed.
Capsule Tree. The very first Capsule created on a newly installed system, was not listed in the
Capsule Tree in case there were no subfolders of the Main capsule folder.
Capsule Tree. An error occurring after copying a Capsule through the right-click-drag&drop on the
Capsule Tree window and which was incorrectly displaying hidden folders, has been fixed.
Capsule Tree. An error occurring after multiple repeated copies of screens and procedures and
which could provoke instabilities of the BoardClient has been fixed.
Capsule Tree. Capsules which name starts with the underscore character, are not listed in the
Capsule Tree but are accessible through the "Goto Capsule" action of a procedure.
Dynawrite++. An error of the Current Selection function used in a Dynawrite++ document has
been fixed.
Dynawrite ++. An error in the Dynawrite++ object occurring after defining a header in the document
has been fixed.
FlowChart Value. An error in the display of decimal values on a FlowChart area and occurring on
systems having the comma as decimal separator has now been fixed.
Release Notes
Flowchart area. An error causing the following error message no HWD bound to this object,
occurring in design mode while overlapping a floating pane drag&drop onto a flowchart area has
been fixed.
Graph object Standalone Layout. Changing the header text of a column which was previously set
in the Graph tab, was clearing the setting.
Folder object: An error of the Capsule designer which could block removal of an empty tab of the
Folder object has been fixed.
Drill-to child screen. An error causing the loss of the master function of a Dataview and occurring
after closing a child screen has been fixed.
Drill-to child screen from a FlowChart. An error occurring upon closing a child screen and causing
the propagation of the child screen name to the parent has been fixed.
Drill-down on a Dataview cell. When drilling-down on a cell of a Dataview having the columns
Totals left aligned, the drill-down was incorrectly occurring on the item to the right of the drilled cell.
Dataview Dynamic Format. An error causing a crash, occurring after pasting a Layout on a newly
created Dataview and then immediately opening the Dynamic Format and clicking the OK button,
has been fixed.
DataView with collapse. An error of the Dataview object with the Collapse option, causing the
expand/collapse of rows to stop working immediately after having clicked on the total row, has been
fixed.
Dataview column sort. An error of the Dataview column sort occurring when attempting to sort a
text column (single click on the column header) and causing the Dataview rows to collapse, has
been fixed. Sorting on text columns is not supported.
Dataview header. An error of the @year function occurring in the Dataview header has been fixed.
DataView Layout. An error occurring when accessing the Functions tab of a column subsequent to
an empty column, has been fixed.
Dataentry on totals of a Dataview. Attempting to enter data on a total cell of a Dataview having the
save/undo option disabled was displaying an erroneous warning message.
Dataentry on a Dataview with 2 or more independent entities by row. Attempting to enter data
on a total cell of a checkbox column of a Dataview having the save/undo option disabled was
erroneously displaying a warning message.
Dataview with gauges and a header. In a Dataview report having a column using the Alert/Gauges
option, the use of the a Layout Header was preventing the display of the gauge on the totals and
subtotals rows.
Dataentry on a text or date Infocube. When entering data through a Dataview object on a text or
date Infocube, the inserted text or date was in some cases displayed (in green color, before saving)
in the cell above even though it was correctly saved against the desired entity member.
Control Mode
The Control mode delegates the validation of the username/password of existing Board user
accounts. Therefore when using this mode, you must first define your Board user account as
usual but in the password field type LDAP instead of the real password, as illustrated.
297
You have completed configuring the account. Note that you can still have other user accounts
defined as usual with their password saved in the BoardMaster users list. This is useful when
you need to define Board accounts for persons which are not registered in your network
domain.
In Control mode, when the user attempts to log-on the BoardMaster, the BoardMaster receives
the username/password then
looks up for the username in the list of registered users and if the username is not
found in the BoardMaster users list then the log-on attempt is turned down with the
error message "User not registered".
if the account's password field is "LDAP" then the BoardMaster sends the
username/password to the DC or LDAP server for authentication and finally if
the DC or LDAP server responds "authentication successful", then the
BoardMaster grants access
if the account's password field is not "LDAP" then the BoardMaster performs
the authentication as usual.
Append Mode
This mode dynamically creates the Board user account the first time a user logs-on the
BoardMaster and is successfully authenticated by the Domain Controller or LDAP server. New
Board user accounts are created automatically when the users log-in and are assigned the
privileges and settings defined in a generic Board User Group named "LDAP".
To use Append mode, create a Board user Group called LDAP and apply the settings and
privileges which you want to assign by default to new users, it is recommended to specify a
298
Release Notes
minimal level of privileges. When a user account is created by the Append mode, its password
is set to LDAP and subsequent behaviour is as per Control mode.
When running in Append mode, when the user attempts to log-on the BoardMaster, the
BoardMaster receives the username/password then looks up for the username in the list of
registered users,
the BoardMaster
1. creates a user account in the BoardMaster users list,
2. assigns to it the settings found in the LDAP User Group,
3. sets the password field value to LDAP
4. and immediately grants access.
Microsoft AD Authentication
When using AD Domain authentication, BoardMaster delegates the validation of the user's password
to the Microsoft Primary Domain Controller or Domain Controller. This option can be used only if you
are using a Microsoft Server for managing network users (such as Microsoft Windows 2000 Server or
later) and only if the machine running BoardMaster belongs to the domain of the domain controller that
perform the user's authentication.
To configure the Microsoft domain authentication, go to the BoardMaster Security tab and click the
LDAP AD button as shown,
299
then tick the Active Directory check-box, type your domain name in the AD Domain field (see picture
below) and finally set the Control or Append mode as desired.
The Test button allows testing the authentication of a username/password against the domain
controller.
Note
To run the BoardMaster service you must use an account that has a special Windows
privilege called SE_TCB_NAME set to "true" on the AD server or domain controller server .
This is because the BoardMaster program uses a Windows API called LogonUser which
requires (it is a Microsoft imperative requirement) this level of privilege to be invoked.
300
Release Notes
This privilege is defined in the domain policies, the "long" name is "Act as part of the
operating system".
For example you cannot use the LocalSystem account.
A way of doing this is the following:
- create a new account on the domain, just for the purpose of running the BoardMaster
service, for example "BoardMasterUser"
- make this account administrator of the computer where the BoardMaster is running,
- make this account administrator of the computer where the AD is running (or at least grant
the SE_TCB_NAME privilege).To do this, open the "Domain security policies" snap-in, select
the option "User rights assigments" and add the "act as part of the operating system"
privilege, refer to the attached screenshot.
- grant other necessary privileges to run the Boardserver programs, such as for example
access to network resources in case you need to read text files or ODBC connections from
other computers.
OpenLDAP Authentication
LDAP Authentication, allows to delegate the validation of the user's password to an LDAP compliant
server such as Microsoft Active Directory Services, OpenLDAP Server, Lotus Domino Server etc..
To configure the LDAP authentication, go to the BoardMaster Security tab and click the LDAP AD
button as shown,
301
then tick the OpenLDAP check-box, configure the LDAP parameters as explained hereafter and
finally set the Control or Append mode as desired.
Port :
set the TCP/IP port of your Ldap sever, conventionally the common value is 389.
Full Name :
is composed of a first part that describes the protocol ldap://, then the hostname where the
LDAP service runs and finally the RDN of the container that holds the entry with the different
parts that belong to the Domain component of the directory (dc).
Example:
Suppose that we want to authenticate the entries under container Account, so the complete
DN of the entry of Mr. Brian Arkills is: uid=barkills, ou=accounts, dc=mycompany, dc=com
Then the string in Full Name field should be:
302
Release Notes
ldap://server01.mycompany.com/uid=[un]
dc=mycompany, dc=com
ou=accounts,
The [un] string is a fixed value and is used by Board in the authentication challenge.
Board will replace the text [un] with the username keyed in the BoardClient logon prompt.
In the security folder the user must be defined as it appear in the entry LDAP attribute value of
his RDN.
Note! In the above examples, we have used the UID attribute of the entry, but the required
attribute may be different according to the schema used by your company. For example the
Windows Active Directory usually define sAMAccountName as the attribute for authentication
purposes.
For more information LDAP, refer to LDAP general concepts
Troubleshooting
The directory structure is not equal in all organizations or companies, actually it may
considerably vary, so the string used in Board LDAP configuration should be composed in
different ways accordingly.
Usually the directory structure, the LDAP schema, is well known by the system administrator
that should be able to provide the correct setting by deducing it from the examples given in
the current manual.
In case if you dont know the directory structure, you may try to browse the LDAP schema
using a tool such as LDAP Browser from Softerra (http://www.ldapbrowser.com/) to identify
the right schema that fit for you.
The Softterra LDAP Browser is a freeware tool that is able to browse and search within a
given LDAP Server.
You can also check the connection string by authenticate yourself over the LDAP server with
the username of a user involved in the authentication challenge.
To do this, in the wizard of LDAP Browser specify the complete DN of the user:
303
If you are not able to connect with LDAP Browser, check if port TCP 389 is open from and to
the server where Board Master is installed.
In some LDAP schemas you may find that users are defined across different OU containers.
In this case you should consider using the [un] parameter, to include the OU part of the DN.
Example:
Users splitted in two OUs, the OU= marketing and OU=account
The username string should be:
304
Release Notes
An LDAP directory tree often reflects various political, geographic, and/or organizational boundaries,
depending on the model chosen. LDAP deployments today tend to use Domain name system (DNS)
names for structuring the topmost levels of the hierarchy. Deeper inside the directory might appear
entries representing people, organizational units, printers, documents, groups of people or anything
else that represents a given tree entry (or multiple entries).
Example of LDAP directory that integrates within the DNS namespace with person and other part
DNs:
How do you reference an entry within my LDAP directory? Each entry in the directory has a unique
name known as the distinguished name (DN). Each entry also has a name local to its immediate
container known as the relative distinguished name (RDN). The RDN is unique among all entries in
that container. For now, think of a container as being similar to a directory or folder in a file system.
The DN of each entry is formed by concatenating the RDN of the entry with the RDN of the
containers between the entry and the directory root. There is a comma between the RDNs in the DN.
An entry can look like this when represented in LDAP Data Interchange Format (LDIF):
DN: uid=barkills, ou=people,,dc=mycompany,dc=com
cn: Brian Arkills
uid: barkills
sn: Arkills
telephoneNumber: +1 234 567 8901
mail: barkills@mycompany.com
objectClass: inetOrgPerson
objectClass: person
objectClass: top
The DN is the way to identify uniquely an entry in the entire directory, it's not an attribute nor part of
the entry. "cn=Brian Arkills" is the entry's RDN, and "dc=mycompany,dc=com" is the RDN of the
parent entry, where dc denotes Domain Component. The other lines show the attributes in the entry.
Attribute names are typically mnemonic strings, like "cn" for common name, "dc" for domain
component, "mail" for e-mail address, uid for user id and "sn" for surname.
305
A server holds a subtree starting from a specific entry, e.g. "dc=mycompany,dc=com" and its
children.
In the above picture example the container starting point from top to button is the DNS
(mycompany.com) DN (dc=mycompany, dc=com). Then there are some children container OU
(organization unit) like Customer, Account, People ect. Each container may hold another container
(white) or an entry (black), each entry may . To identify an entry in the above example you should
specify the full DN.
For example in a schema like the above one:
The entry under the account container may be identified by the DN:
uid=barkills, ou=Accounts, dc=mycompany, dc=com
the entry under the people container may be identified by the DN:
cn=Brian Arckills, ou=People, dc=mycompany, dc=com
Note: the cn or uid is not the name of the entry itself but an attribute of the entry
306
Release Notes
Tip! It is possible to run the installation procedures as a background process that doesn't require any
user interaction (silent installation). Refer to the following knowledge-base article for details: How to
install Board in silent mode
Optimizations
- The caching mechanism has been improved and made more robust and fault-tollerant. The
preparation of the database cache is now carried out independently by each BoardServer session.
The BoardClient is now able to more accurately detect inconsistencies in the local copy of the
database cache (inconsistencies caused by errors in the communication layer) and in case of
inconsistencies re-attempts the transfer of the cache.
- An optimization of the BoardMaster now allows to better and more robustly handle peaks in the
number of simultaneous connections to the BoardMaster with over 20 highly active BoardClients (i.e.
each executing a high number of small requests per second).
307
308
Release Notes
Capsules are not backward compatible: a Capsule which is created or edited (opened then
saved) with version 6.0 cannot be re-opened using any earlier version of Board.
Databases are backward compatible: it is possible to create or edit a database using version
6.0 and then open and edit it using a prior version 5.x however the new 6.0 features will
clearly not be available.
Client-Master-Server compatibility
The BoardClient program version 6.0 cannot connect to prior versions 5.x of BoardMaster
and vice-versa BoardMaster version 6.0 doesn't accept connections from earlier versions of
BoardClient,
it is therefore required to simultaneously update all PCs running Board.
Considering that BoardMaster 6.0 actively rejects connections from clients running earlier
versions (5.x), it is advisable to install the new version first on the server running the BoardMaster
and then deploy the BoardClient upgrade to all client PCs.
Notes
When upgrading a PC or a server from any earlier version you must not un-install the Board
license. Currently installed licenses (for version 5.x) are fully compatible with version 6
therefore after running the BoardClient or BoardServer installation programs you can start
using version 6.0 immediately.
It is possible to run the installation procedures as a background process that doesn't require
any user interaction (this technique is referred to as "silent mode" install). Refer to the
following knowledge-base article for details: How to run Board Setup in silent mode.
in the lower part, under the group Visualization, select the desired skin from the drop-down list
as illustrated
309
The radio buttons present in the Visualization group provide further customization of the look
and feel in combination to the selected skin.
Note that the skin is a configuration of the BoardClient program therefore each user can select
his preferred style and then change it at as desired.
To select a skin for the BoardMaster program, ,
Go to the Options tab of the BoardMaster program,
select the desired skin from the drop-down list located in the Visualization group.
The selected skin affects also the look and feel of the BoardServer program.
Release Notes
To open a document, click on the DynaWrite++ document icon. When the document is
opened, all Layouts of embedded Capsules objects (reports, charts and flowcharts) are
refreshed.
To create a new document, select File / New from the menu or click the New document
icon.
311
Synchronized mode
The Synchronized mode makes all Capsule objects (tables, charts, flowcharts) of the
document subject to a unique Select and Dynabar. To enable the synchronized mode, tick
the Synchronize check-box located in the toolbar (refer to picture 1 above). When the
Synchronize mode is enabled the Select icon and the Dynabar become active and can be
used by the end-user to navigate through the data.
When the Synchronize mode is disabled, each Capsule object has its own independent
selection which can be configured by clicking on the Select icon located in the object's
configuration window.
Release Notes
a pop-up window with a blank DataView opens,
then right-click on the DataView to access the Layout, configure and run the Layout,
click the OK button of the DataView window to close it,
the icon of the DataView is added on the page.
By clicking the icon the DataView report will open in the pop-up window.
To add a chart
Click the Insert Chart icon (see picture 1 above), or right-click on the document's
page and select Capsule Object / Graph from the pop-up menu,
a pop-up window with a blank Graph opens,
then right-click on the Graph object to access the its configuration properties,
configure and run the Graph,
adjust the width and height of the window to the desired size for the chart. The size of
the window determines the size of the image which is inserted into the document.
then press the OK button to close the chart configuration window,
the chart is translated into an image and inserted into the document's page.
To add a FlowChart
click the Insert FlowChart icon (see picture 1 above),
a pop-up window with a blank FlowChart opens,
draw the flowchart as desired and right-click on the FlowChart to access its properties,
adjust the width and height of the window to the desired size. The size of the window
determines the size of the image which is inserted into the document.
then press the OK button to close the FlowChart configuration window,
the FlowChart is translated into an image and inserted into the document's page.
Notes !
Some features of the FlowChart object available in the Capsules environment are not
supported: the FlowChart areas can't contain other toolbox objects and can't have a
background image.
To edit an object
To edit a table: click on the first cell (top-left) of the table to open the DataView pop-up
window.
313
To edit a Chart or a FlowChart: right-click on the chart or flowchart image to open the
pop-up window.
To edit a link to a DataView, click on the DataView icon.
To edit a Selection to an entity (Current Selection), place the mouse over the
selection text, the pointer changes shape then left-click.
314
Release Notes
The DynaSheet++ environment
To open a workbook, click on the DynaSheet++ workbook icon. When the workbook is
opened, all Layouts of the active sheet are refreshed.
To create a new workbook, select File / New from the menu or click the New workbook icon.
To save a workbook, select File / Save or click the Save icon. A file with extension DSH is
created.
DynaSheet++ workbooks can only be saved on the local hard disk, it is therefore
recommended to save your documents into the Board.Loc\Capsules folder (or in a sub-folder)
315
Notes
When a workbook is opened, only the Layouts of the active (foreground) sheet are
refreshed therefore if a worksheet contains formulas referencing cells of another
worksheet, you must activate all worksheets holding some Layouts to correctly
refresh the calculated cells.
When a Layout is defined on a given cell, the returned data is inserted in the
spreadsheet starting from that cell then down and across. If the number of rows and
columns of the report is subject to change, you should allow a sufficient number of
empty cells under and to the right in order to avoid overlapping with other reports or
other cells containing data.
The cells of a report cannot be formatted (such as font style and color, cells color,
borders and patterns etc..).
316
Release Notes
All reports which are on the same worksheet share a unique Select and Dynabar
configuration however different worksheets have independent Select and Dynabar settings.
The button cells can be used for different purposes, by clicking on a button-like cell, the user may
trigger a procedure, drill-down to a child screen or view a BLOB, in relation to the multidimensional
space identified by the clicked cell. For example, if a button-like cell is configured to fire a procedure
and the DataView has a dimension by row and another dimension by column, then by clicking on a
button-cell, the procedure will run with a selection on the entity members of that row and column.
317
In case the column headers of the object are not visible, click on the first row of the column to sort.
318
Release Notes
The BLOB InfoCubes are InfoCubes that can store in a cube cell documents of the following type: Text
(TXT extension), Rich text (RTF), MS-Word (DOC) or MS-Excel (XLS). The documents are
compressed and encrypted into the Board database InfoCube therefore can't be accessed from
systems other than the Capsule environment. As InfoCubes of other type, the BLOB InfoCubes are
subject to the Board database security therefore by assigning user access rights to the InfoCube it is
possible to assign read-write privileges to some users, read-only or exclude it to others.
The BLOB InfoCubes extends the capabilities of Board from the management of multidimensional text
to the management of multidimensional documents containing sensitive information.
319
With the DataView object, create a report using the BLOB InfoCube. Run the report, then
double click on a cell of the BLOB InfoCube: the spreadsheet or text editor program is
launched and the document contained in the clicked cell is loaded. Note that you may format
the BLOB InfoCube column to Button, in this case a single click on the cell triggers the editor
program.
If the cell is empty, a new document blank is created. You may edit the document, then when
you exit the program the document will be automatically saved into the BLOB InfoCube.
It is possible to use the Viewer object to view and edit the documents of a BLOB InfoCube,
With the DataView object, create a report using the BLOB InfoCube,
Add a Viewer object to the screen: drag and drop the Viewer object from the Toolbox onto the
Capsule screen,
In the pop-up window, select the option "MD BLOB" and type the name of the BLOB InfoCube
to view,
320
Release Notes
If the cell is empty, a new blank document is created. You may edit the document, then when
you exit the program the document will be automatically saved into the BLOB InfoCube.
Note that if the DataView report doesn't have entities by column, it is possible to click on an
entity member to view the relating document in BLOB Viewer.
Notes
To remove documents stored in a BLOB InfoCube use the InfoCube Clear action.
It is not possible to load documents in a BLOB InfoCube through the DataReader
It is not possible to extract the documents of a BLOB InfoCube through the Xtract action of a
procedure.
Data-entry Locking
The data-entry locking is a feature of the Layout object allows to lock the data-entry on a column on
the basis of another column of the Layout. This feature is designed for budgeting and forecasting
applications where there is a need to lock or unlock the data-entry dynamically, based on the rules of
the application workflow.
The following picture shows an example of a DataView object where the conditional locking is applied
to the Budget InfoCube. The cells having a colored background are locked, data-entry is allowed only
"Budget" cells with a white background. The adjacent column shows "Locking Condition"
determines which cells should be locked: if the value different from zero then the locking occurs.
321
Notes
The conditional locking is applicable to the Layout of any object supporting data-entry:
DataView, GDE, Mapping and STO.
When the conditional locking is applied, the data-entry on a row or column total cell is locked if
at one detail item is locked or if the summary algorithm of the data-entry locking column is set
to NoTotal (if the locking column is an InfoCube) or to Calculated (if the locking column is an
algorithm).
If you are using an inverse algorithm (see Inverse algorithm for details) to enter data on an
InfoCube, the same conditional locking column must be defined after the data-entry InfoCube
column and after the inverse algorithm column.
The column containing the locking condition can be a hidden column.
Release Notes
A child screen is a Capsule screen which appears similarly to a pop-up window, of a smaller size and
overlaying its parent screen. To create a child screen,
Create a new screen by clicking the New screen icon
While in design mode, click the restore icon of BoardClient's workspace in order to reduce it to
non full-screen size,
Resize and position the window as desired. Note that when a child a screen is opened by a user,
it retains the size and position defined during designing.
Then place the objects from the toolbar onto the screen and configure them as for standard
screens,
Save the screen then close it.
Notes
When designing a child screen, the size of the workspace is the same of the size of a full screen. The
size of the objects placed on the screen is absolute therefore it is not affected if the screen is resized.
This allows the screen designer to have an accurate control of the presentation layout.
When a user jumps to a child screen while navigating the Capsule from in runtime mode, the select
and Dynabar of the parent screen is inherited by the child screen therefore any selection saved on
the child screen while designing it is ignored.
323
The drill-down path or options can be saved (by saving the parent screen) and then reused through a
left click on the row header, as for the standard drill-down function.
Note
The entity from which the user drills-down in the parent screen is added to the Dynabar of the child
screen.
Note that it is possible to define the text label for the button with the following syntax : "Text Label,
Screen Name"
324
Release Notes
For example, to create a button with the label "Go to detail" which drills-down to the screen
named "Child screen", the text InfoCube or text algorithm should return the string "Go to
detail, Child screen".
Note that if the name of the child screen is modified, the existing links need to be updated to the new
name.
325
326
Release Notes
the automatic rule sums all the member having a code with a common root (the same left most
characters) into the item which code is the root. For example the entity member "4A01 40" is the sum
of members which start with "4A01 40" therefore of "4A01 40 01 01", "4A01 40 01 02", "4A01 40 01
03", "4A01 40 01 04" and "4A01 40 02".
The data should therefore be loaded on the detail members only, as in the following example,
the automatic rule calculates the members which are highlighted by summing all other members which
have a common root
This new function allows to view the selection which was saved on a screen or in a procedure.
a pop-up window opens displaying the currently active entities selection as in the illustration hereafter.
328
Release Notes
The DynaWrite object is now able to dynamically display the currently selected members of a chosen
entity or the entire screen selection. The DynaWrite object can be placed onto the Capsule screen for
the user to easily view or print the active selection of that screen.
To configure the DynaWrite object,
Insert a DynaWrite object on a Capsule screen, then right-click on it to access the designer
environment.
Type the desired text then right-click to insert the selection text,
Choose the Current Selection option from the pop-up window (refer to the illustration
hereafter) then
choose the option "Current Selection" to insert all entities and entity members on
which a selection is active
or choose one entity from the list if you wish to only view the active members of that
entity.
Exit the DynaWrite designer environment and save the Capsule screen.
329
It is possible to include multiple entities, for example: "The Year is @Year and the Regions
are @Region".
It is possible to insert this command in the Layout title instead of the header.
A carriage return (new line) character is automatically added after the members list of an entity.
iTunes
Royale
The Picture object, now supports all properties of the former Button object, including Actions. The
Capsule Button object of Board version 5.x is equivalent to the Picture object of version 6. When you
open a Capsule created with Board version 5.x the buttons are treated as Picture objects of version 6
in order to preserve all properties and behaviour therefore the skins do not affect the look and feel of
such objects.
On-screen-exit procedure
This new function allows to link to a Capsule screen a Procedure which is automatically executed
when the user exits the screen and has either entered data or ran a procedure on the screen.
To select the procedure to run when the user exits the screen, open the screen Properties window and
choose the desired procedure from the Trigger drop-down list as in the following illustration.
330
Release Notes
Note that the selected procedure is automatically launched whenever the user exits the screen but
only if the user has done data-entry or has ran a procedure on that screen - if the user only visits the
screen without modifying any data the procedure is not triggered.
The procedure runs when the user attempts to exit the screen, but before actually closing the screen
therefore the procedure context (the active Dynabar and Select) is that of the screen.
331
- Capsule Screen copy. Copying a Capsule screen or procedure from a Capsule stored in a Local
folder to a Capsule stored on the server is now disabled due to a disruptive malfunction provoking a
corruption of the target Capsule.
- Capsule Screen copy. A malfunction occurring when copying a screen containing an STO object
from one Capsule to another Capsule has been resolved.
- Capsules Tree navigator. The Capsules Tree window now manages 6 levels of subfolders (i.e. 5
more than prior versions) of the Board\Capsules folder. The window width can now be adjusted by
placing the mouse pointer over the right border. Note for developers! the width of the Capsules Tree
window affects the size of the database functions windows (such as Entities, InfoCubes
DataReader...), if the Capsules Tree window is too wide, the windows of some database functions
may become truncated on their right side. Should that happen, reduce the width of your Capsules
Tree window.
- A malfunction of the Capsule environment occurring after running a procedure on a screen with an
STO object and which was preventing to switch to design mode has been resolved.
- F7-Excel export. A malfunction of the BoardClient F7 function (export to MS-Excel) which truncated
the decimal part of numbers has been resolved.
- Keep Totals. A malfunction of the Keep Totals filter option occurring on Layouts containing an Entity
in a column has been resolved.
- Screen selection. A malfunction of the Procedure Designer environment occurring when opening a
procedure with a DataReader action and causing the screen selection to reset has been resolved.
- SQL-Builder. A malfunction of the RDB InfoCube designer environment occurring when attempting
to create a table on an Oracle or SQL-Server database to store an InfoCube of type double precision
has been resolved.
- FlowChart. An instability causing the BoardClient program to crash and occurring randomly when
clicking on a FlowChart area linked to another screen has been resolved.
- Select. A malfunction occurring when using the Focus function on an entity which exceeds the entity
cut-off threshold has been resolved.
- STO. A malfunction of the STO object occurring on a Layout with two or more validation fields has
been resolved.
- STO. An instability of the STO object which was causing the loss of the Layout configuration has
been resolved.
- DataFlow with Rule. A malfunction of the DataFlow occurring when calculating a Rule on an
InfoCube having complex multidimensional structure has been resolved.
332
Release Notes
- A malfunction causing the BoardServer to hang when processing a column algorithm containing a
syntax error due to an incorrect use of quotes has been resolved, the calculation with the error is now
ignored.
- FlowChart area with color coding. A malfunction of the color coding function of an area of the
FlowChart object has been resolved.
333
334
Release Notes
Upgrading from version 5.5 (or earlier)
It is required to upgrade all client PCs simultaneously. BoardClient version 5.5 (or earlier)
cannot connect to a BoardMaster version 5.6B and vice-versa. It is recommended to first
upgrade the server where BoardMaster is running to version 5.6B and then immediately
upgrade all PCs running BoardClient. Note that BoardMaster version 5.6B refuses
connections from BoardClient version 5.5 (or earlier) to grant integrity.
Capsules and databases created or edited with version 5.5 (or earlier) are fully compatible
with version 5.6B and do not require any type of conversion or change in order to be used
with version 5.6B.
Tip! It is possible to run the installation procedures as a background process that doesn't require any
user interaction (silent installation). Refer to the following knowledge-base article for details: How to
install Board in silent mode
336
Release Notes
- Web print preview. An error, occurring on the print preview page of reports without any column
totals (the Summary Algorithm is set to NoTotals on all columns) and causing the last row of the
report to be formatted as a totals row, has been resolved.
- Web Replicator. An error, in the creation of a BSP script occurring when translating a DataView
using color coding with red and green thresholds equal to zero, has been resolved.
- Web script in BSP page. A malfunction of the web script commands causing an error when defining
certain column headers on columns using a time function (such as Previous Year) has been
resolved.
- Print of a Web Page. An error occurring when attempting to print a Web report created through the
Query Builder has been resolved.
- Web Page print style. The format of the table corresponding to a Supertable's print preview can be
customized through the classes TABLE.DataPrn contained in the BoardStyle.css file. .
- Web Replicator. A malfunction of the Web Replicator, occurring when exporting a Capsule screen
containing a picture and using the Picture size "percentage" option has been removed.
- Alert box in Web Page. The SquareAlert class has been added to the BoardStyle.css file to allow
formatting of the alert boxes contained in a Board Web Server Page.
- Web Server HTML theme. An error causing some charts not to display correctly in a Board Web
Server Page when using the HTML theme has been resolved.
- Try and buy licenses: A malfunction that was preventing the use of Try&Buy licenses (licenses
having a time limit) on some systems has been resolved.
337
Release Notes
Notes
It is required to update all PC running Board simultaneously: BoardClient version 5.6
cannot connect to prior versions of BoardMaster and vice-versa the BoardMaster
version 5.6 doesn't accept connections from earlier versions of the BoardClient.
Board applications (databases and Capsules) created with prior releases (5.x) are fully
compatible with the current upgrade and do not require any migration or other change.
When upgrading a PC or a server from any earlier version you must not un-install the Board
license. Installed licenses are fully compatible with the current 5.6 release therefore after
running the BoardClient and BoardServer installation programs you can start using version
5.6 immediately.
It is possible to run the installation procedures as a background process that doesn't require
any user interaction (this technique is referred to as "silent mode" install). Refer to the
following knowledge-base article for details: How to run Board Setup in silent mode.
339
In the Designer environment, click on a row header to highlight it, then use the toolbar at the
top to select the desired font, color and cells border style,
Remarks
Font styles and color are defined per row, therefore applied to all columns of the report.
It is possible to select several rows then apply the same format to all: hold the shift key down
to select a range of contiguous rows or hold the Ctrl key down to select non contiguous row,
then define the format options (font, color and borders).
340
Release Notes
If the Layout definition contains more than one entity By Row, then it is possible to define the
format only for the most indented entity. When opening the Designer environment for such
reports notice that only the most detailed entity of the Layout is retained.
This feature is not compatible with the Layout options Indentation and Collapse.
Applying a format to multiple rows
It is possible to select several rows then apply the same format to all:
hold the shift key down to select a range of contiguous rows
or hold the Ctrl key down to select non contiguous rows; the selected rows are highlighted,
then define the format options (font, color and borders) through the top toolbar.
Another method for applying the same format to multiple rows consists in defining the desired format
for one row, then selecting the other rows to format and clicking the Apply button located in the top
toolbar (see image below).
DataView Header
Allows to add a header row to a report built using the DataView object. The header can contain an
image file (a logo) and some text, including some computed text such as the current date and time,
the name of the Board database and Capsule. This feature has been designed to improve the
reporting capabilities to meet statutory reporting requirements.
Example of a DataView report with a header
341
The header is always made of two cells, the first cell which may contain either some text or an
image (usually the company logo or brand logo) and the second cell which may contain text
only.
Type the text in the desired text areas: the First Cell Text area and/or the Second Cell Text
area. Multi-line text is supported.
To include an image into the first cell, click the Picture button and select the desired image file.
342
Release Notes
returns the name of the Board user (the user account logged-on BoardClient).
@screen
@capsule
@database
Set the text font style, color and background color and alignment
343
Cockpits enhanced
New styles and options designed to support creating dashboards. You can now choose the style of
your cockpit object from a gallery of different angular gauges as well as some vertical and horizontal
indicators. For any of the available indicators it is also possible to set the color sequence to redyellow-green or reverse it to green-yellow-red.
To select the cockpit style,
Open the Layout of a cockpit object, go to the Graph tab
Then select the style from the Appearance drop-down list and choose the orientation as
desired
Angular 1
Angular 2
344
Release Notes
Angular 3
Angular 4
Angular 5
This is the style of prior versions.
Horizontal 1
Horizontal 2
Vertical
Vertical NoLabel
This style doesn't display the entity member
name.
345
346
Release Notes
The translator environment opens. Type a language name or identifier in the top left table
which is titled Languages, as in the following example
For each language identifier defined, a new column will appear in the main translation table.
The column heading displays the language identifier to which it refers.
The first column of the main translation table contains the complete list of InfoCubes and
Entities of the Board database. InfoCubes names are highlighted with a yellow background
while entities are displayed on a grey background. Type the desired translation in the
corresponding cell as shown in the following example,
Note that it is not necessary to translate all terms in a given language. If the name of an
InfoCube or Entity is not translated then the default name is used.
When the translation is completed for all desired languages, click the OK button to save your
work.
Configuring the language for a user
To set the language for a user,
Open the BoardClient program and go to the Setup window.
347
In the Data Dictionary Language ID field type the language identifier which has been defined
in the translation environment.
Notes
When setting a language for the first time or when changing a configuration you may need to
close and restart the BoardClient program to make changes effective.
The translation of InfoCubes and Entities applies to the Capsule environment only. Whenever
a database design function is accessed (such as Entities definition, or InfoCubes definition)
the language setting is ignored and the actual name of the InfoCubes and Entities is
displayed. This feature is designed to support end-users working in the Capsules
environment, not for Board developers needing to frequently change context between the
Database and the Capsule environments.
Capsule Themes
This feature allows to set the style for all buttons (Button theme) and for all DataView objects
(DataView theme) of a given Capsule. Three Button themes and three DataView themes exist.
To select a theme, open the Capsule's Screen property window.
348
Release Notes
Button Themes
The Button themes are Classic, Silver and Office. The Silver and Office themes add a shaded effect to
the buttons and make the button change color when the mouse is placed over it. Note that choosing
the Silver or Office themes will affect all buttons of the Capsule and the new color prevails over the
button's color property.
Tip: the Silver and Office themes are best combined with setting the screen lines width to zero,
disabling the Show Lines property and setting the buttons BevelWidth property to zero.
DataView Themes
The DataView object themes are Grey, Sand and Blue. The theme settings apply to all Capsule
screens. The Shadowed Labels check-box option allows to set the colouring of the first column of the
DataView - i.e. the column holding the entities.
Example of a DataView using the Grey theme:
349
350
Release Notes
351
Export to MS-Excel
The Export to Microsoft Excel feature (pressing the F7 function key) has been modified: when opening
an Excel file created from an export from Board, the first Sheet of the workbook (Sheet1) is now
displayed instead of the last Sheet of the workbook.
Modifying the Max Item Number of an Entity
It is now possible to modify the Max. Item Number of an entity without having to clear its content as
long as there are no InfoCube versions structured by that entity which contain data. When there is at
least one InfoCube version structured by an entity and containing data, a red flag appears in the
checkbox column marked with an asterisk. Therefore it is possible to modify the Max Item Number of
entities for which the flag is not present.
Considering the example hereunder, it is possible to change the Max Item Number of the entity City
but not of entities Customer or State.
352
Release Notes
threads is not a limit, if all threads are allocated and an additional one is needed then it is dynamically
created (and will be destroyed when released).
This optimization can be significant for Board Web installations where the number of simultaneous
users is high (on average or during utilization peaks). It improves the server's performance and the
degree of parallelism it can handle.
The number of process threads is set through the MaxThreads parameter found on the BoardMaster
WEB configuration tab.
A value ranging from 25 to 50 may be suitable for small to medium installations with a number of
named accounts of a few hundreds. For lager installations with peaks of hundreds of simultaneous
users, you may increase the threads number to 200, 400 or more. However, setting a too high number
will deteriorate performance and slow down the start-up of the BoardMaster HTTP service.
Finding the optimal configuration requires an empirical approach since this type of behaviour is largely
dictated by the hardware characteristics. Multi-processor servers and CPUs with Dual-core technology
are designed for managing a high processes parallelism and can therefore handle a higher number of
process threads compared to servers with a single processor.
353
a user's menu or a user group menu, click on the Web Menu button found on the user
account row,
An arrow icon on the Web Menu button indicates that a personalized menu exists for that account.
The Web Menu Designer environment opens (see below).
354
Release Notes
Define the menu level: press the Level Down button to indent an item (or press Level Up to
remove the indentation),
If desired you may click the Preview tab to have an instant preview of the menu, then click
the Designer tab to switch back to the design environment,
355
To associate an action to a menu item, select it then choose one the three available action
types,
File
Folder
Native
Function
356
Select
Download
Refresh
Query
Builder
Save as..
Edit
Briefing
Release Notes
Home
Note that you must first run a Board Web Server page before being
able to access the above Board functions - except for Home and
Briefing.
You may customize the menu icon by selecting a picture file from the Icon field. Note that
the
picture
file
must
be
located
in
the
directory
\BoardPub\Root_Web\_Web_Sys\MenuDat\Images.
You may add a help text which will be displayed when the user places the mouse over the
menu option by typing it into the ToolTip field.
Click the Save button to save the menu.
Notes
The menu definition is saved in a file having the user's account name (or user group) and
MNU extension in the directory \BoardPub\Root_WEB\_Websys\MenuDat . For example
the Web menu for the user account Ronald is a file named Ronald.mnu . To back-up menu
definitions
save
all
the
files
with
MNU
extension
found
in
the
\BoardPub\Root_WEB\_Websys\MenuDat directory.
If you rename a user account or a user group, you should rename the corresponding menu
file accordingly.
Customizing the Web Menu
The Menu properties
Use the options located in the top part of the Menu Designer to customize the menu properties. Click
on the Preview tab to view the effects on the menu as you change its properties..
Mode
Menu Icon
Page Icon
Highlight
BackColor
Sets the text font color and background color applied when
the mouse is placed over the item.
ForeColor,
Border
Font Size
Icon Size
Spacing
X Offset, Y Offset
Copying a Menu
When creating a new menu or editing an existing one, it is possible to copy the menu definition from a
previously defined one,
open the Menu Designer
click the Copy From icon and select the menu name to copy settings from.
apply the desired changes then click the Save button.
Since the menu definition is saved in a file having the user's account name and MNU extension in the
directory \BoardPub\Root_WEB\_Websys\MenuDat, you may also copy a menu by copying the
MNU file. For example, if you wish to copy the menu of the user Robert and apply it to the user Hellen,
simply copy the file Robert.mnu into Hellen.mnu using Windows Explorer.
358
Release Notes
XP
This style changes the button color when the mouse is placed
over it.
Classic
HTML
360
Release Notes
Picture size
Position
Current
All
As is
Resize
Percent
Pixel
the
Percent
Pixel
size:
Table
Target
First Item
as default
More
options
Show Print
icon
Drill-Down
Path
[Entities list]
Select the entities which should be made available for drillingdown on the Supertable objects of the Board Web Server
Page. Note that the drill-down list of entities is applied to all
Supertables present on the BSP page (i.e. to all DataViews
present on the Capsule screen).
Insight
When the Web replicator is launched,
it creates in the target folder a sub-directory using the Capsule name to store the page
definition files
it creates a text file named ScreenName.bsp to store the Board script commands that
will be generated
it analyses the Capsule screen, identifies the objects which are supported by the Web
Server environment and translates them by creating
some script commands which are inserted into the bsp file,
362
Release Notes
See also the Guidelines for developing BSP pages and Supported Objects and Features.
363
Release Notes
Insight
The Board script command for charts is
CHART using "..\Chart_Template" at{..position and size..}
bycol Entity
show InfoCube
...
end CHART
Example
CHART using "MyCapsule\Chart_Template" at{32px;107px;782px;446px}
byrow Division
bycol Year
show Sales
end CHART
Picture
The Picture object is translated into a JPG file which is the original embedded picture converted into
JPG format.
Insight
The Board script command syntax for pictures is
Picture File="..filename.." at{..position and size..}
Example
Picture file="MyCapsule\MainMenu\Logo_P01.jpg" at{36px;184px}
DynaWrite
The DynaWrite object is converted to an unformatted text area in the HTML page.
Insight
The Board script command syntax for the DynaWrite is
Textarea="..text.." at{..position and size..}
Example
Textarea="Hello world" at{10px;60px;100%}
365
FlowChart
When converting a FlowChart object from a Capsule screen into a BSP page it is subdivided into
different parts:
The drawings (areas of different shape, text, arrows and pictures) are translated into a JPG
image using the technique describes for the Picture object.
The embedded DataViews, Graphs and Pictures objects are translated as described above.
The click-able areas for which the Shape property is set to "Button" and that are associated to
an action (a link to another screen or a link to a procedure) are translated into buttons using
the technique described for the Button object.
FlowChart areas that are linked to an InfoCube value (through the area property "Show
Value") are translated into single-cell tables that supports color-coding. This feature effectively
creates the equivalent of the Alert object.
The FlowChart object can therefore be used to create
a drawing (the flowchart) with embedded buttons that link to other BSP pages or that launch
procedures
the equivalent of a Capsule Alert object as in the example hereafter. To do so, create a
FlowChart, define one or more Layouts in the FlowChart then add boxes to the flowchart and
link them to the desired Layout column using the "Show Value" property of the FlowChart
boxes.
Insight
The Board script command for single-cell table is
ALERT
show
InfoCube,
red[value]
green[value]
at{..position..}
...
end ALERT
366
block
alert
Release Notes
Example
ALERT
show
Sales,
RefTo(Sate=FL)
at{425px;327px;36px;18px}
show
Sales,
RefTo(State=CA)
at{29px;201px;36px;18px}
....
end ALERT
red20
green20
block
Square
red20
green20
block
Square
Button
The Capsule Buttons that are supported in the Web environment can
link to other Capsule screens through the Next Screen property
or launch one Board Procedure.
The style of buttons in the BSP page is managed from the BoardMaster, refer to Web Button Themes
for details. The Capsule button color, font, tool tip and the Options properties (the Confirmation
message, password, comment, auto-go) are not supported and are ignored by the Web Translator that
generates the BSP page. The buttons in the BSP page can launch one Board Procedure only,
therefore when creating a Capsule for the Web environment, link the buttons to one (and one only)
Board procedure or to another screen through the Next Screen property.
Insight
The Board script command syntax for Buttons is
button
caption="..label.."
at{..position and size..}
action="..screen
or
procedure
name"
Example
button caption="Go to Menu" action="MyCapsule\MainMenu" at{400px;160px}
Procedures
The Capsule Procedures can be launched from a button of a BSP page. When translating a screen
that contains a Button which is linked to a Procedure, the Web Translator creates the HTML button
object and links it to the procedure name.
Note that the procedure itself (the actions) is defined in the Capsule, the BSP page only contains a link
to the Capsule and to the Procedure name to run.
Example of a script that launches a procedure
COMMON
dtb delta
cps MyCapsule
end COMMON
Button action="MyProcedure"
After translating a Capsule with a procedure to a BSP, you should not delete, move or rename the
Capsule and you shouldn't rename the Procedure otherwise the BSP page will not be able to run the
procedure. If you need to move the Capsule or rename the Capsule or the Procedure you should
either re-run the Web Translator or amend the BSP script command to reflect the changes.
Note
Not all Board Procedure Actions are supported in the Web environment, only those that are executed
by the BoardServer can be run from a BSP page. The following Procedure Actions are not supported:
Go to screen and Go to Capsule
Reset to screen and Interactive selection
367
Release Notes
Drillby Label
Label = Folder/Analysis
Example, consider the following Board script BSP file
COMMON
dtb Delta
ByPage Division
Drillby Year, Month, Product, Customer
end COMMON
...
to add a drill-down option to the BSP page MyDashboard.bsp, modify the script as follows,
COMMON
dtb Delta
ByPage Division
Drillby Year, Month, Product, Customer, jump to my
Dashboard
jump to my Dashboard= MyDashboard
end COMMON
...
Notes
The drill-down statement of a BSP page may include several links to other existing BSP
pages.
This new syntax replaces the former OnDrillby statement which is now obsolete and is no
longer recognized as a valid command.
369
Release Notes
Tip! It is possible to run the installation procedures as a background process that doesn't require any
user interaction (silent installation). Refer to the following knowledge-base article for details: How to
install Board in silent mode
Other changes
SQL statement of the Drill-through is now hidden
The SQL statement generated by the drill-through function is now always hidden while in runtime mode. The SQL statement can be viewed only while in design mode and can be edited
only by a user having a Developer license.
371
Release Notes
DrillBy City, Customer, Product
OnDrillBy Product
table
dtb delta
Show Gross Sales
Show Sales Packs
Note that it is possible to specify several OnDrillBy statements in a query script. For example,
a report which displays Gross Sales by Month, can change to Gross Sales and Discount Value
when drilling-down by Customer, and change to Gross Sales and Sales Packs when drillingdown by Product.
OnDrillBy ANY allows to define the drill report structure for all drill-down entities which are not
mentioned in specific OnDrillBy statement.
For example, the following query runs a given report when drilling-down by Product and a
different report when drilling-down by any other entity.
table
dtb Delta
show Gross Sales
DrillBy City, Customer, Product
OnDrillBy Product
table
dtb delta
Show Gross Sales
Show Sales Packs
OnDrillBy ANY
table
dtb delta
Show Gross Sales
Show Budget Dollars
Tip! To test the above query scripts on your Board WebServer installation, install the "Delta"
sample database available in the download area of Board's Web site or on the installation CDRom.
Data-entry on Text InfoCubes
When entering text in a Text InfoCube, pressing the return keyboard key now enters the text,
previously the return key would move the cursor to a new line. This change applies when the
report rows height are at default size (which usually accommodates a single line of text). To
enter multi-line text you should increase the report's rows height to accommodate two or more
lines of text.
This variation applies to the DataView and STO objects.
Tree diagram: improved display of complex trees
In some cases, with hierarchies made of a large number of entities, the "Tree diagram" view
shows entities overlapping when they can't all be fitted onto the screen. Now, by moving the
mouse over an entity it is brought in foreground making it easier to read its name.
Writing of the Web log file can be disabled
It is now possible to disable writing of the client Web log file (located in the folder
c:\BoardPub\Weblog\Client), thus improving performance of Board WebServer during
peaks or when several hundreds of users are simultaneously connected. To disable writing of
the Web Log file, un-tick the checkbox named Web Log File located on the WEB tab of the
BoardMaster program.
373
374
Release Notes
- DataView with data-entry and left aligned totals. A malfunction occurring when entering data on a
drill-down window of a DataView report having the totals left aligned has been resolved.
- WebQuery Select function. A malfunction of the Select statement allowing to specify a range of
dates (for example Select Year= 2000 to 2005) in a Board WebQuery has been resolved.
- Web Queries better support multi-frame pages. Support for multi-frame Web pages with
embedded Board WebQueries has improved: cases of multi-frame pages where the queries result
would occasionally swap position have been resolved.
- Custom Time Entities. A malfunction of version 5.5 which was preventing loading custom time
entities through the DataReader has been resolved.
- Broadcast settings test. The Broadcast.exe program now has a "Test Settings" function which
allows to verify configuration parameters by sending a test e-mail to a given address. The Broadcast
program is installed by the BoardClient setup program and it is usually located in the C:\Board.Sys
folder. To learn more about Board's broadcasting capabilities refer to The Broadcasting function.
- Time Range and weekly InfoCubes. A malfunction occurring when increasing the database time
range on databases having InfoCubes structured by week and using the Board 4.x weeks convention
has been resolved.
- DynaSheet with charts. A malfunction occurring on DynaSheet objects having an embedded chart
and causing the chart to be populated after clicking on the object has been resolved.
- Objects position on Capsule screens. A malfunction that was occasionally provoking an instable
positioning of the objects embedded on Capsule screens has been resolved.
- Cases of database corruption. A malfunction generally occurring after defining a new entity and
provoking a corruption of the database has been resolved.
- ODBC protocols. A malfunction of the query builder provoking a program crash and occurring when
attempting to design an ODBC protocol on a computer having a high resolution wide screen has been
resolved.
- FlowChart procedures list. The list of procedures shown in the Flowchart could sometimes include
some blanks, this malfunction has now been resolved.
- Support for multi-library data sources. The ODBC DataReader and RBD InfoCubes protocols now
have a better support for queries involving multiple libraries (or catalogs).
- Algorithm on Date InfoCubes. A malfunction of a report or DataFlow Layout occurring when
defining a simple algorithm involving a Date InfoCube has been resolved.
- DB2/AS400 erroneous date value. A data conversion error occurring when connecting to a
DB2/AS400 table having a date field with the value 01/01/0001 has been resolved.
375
376
Release Notes
Prior releases of Board could only handle multidimensional InfoCubes physically stored into the Board
database. This capability is now referred to as the M-Engine. When upgrading a prior Board
installation to version 5.5 it is immediately enabled as an M-Engine license. An M-Engine installation
can be upgraded to a Dual-Engine in order to be able to handle the relational InfoCubes through a
license upgrade.
All end-user functions and features available in the Capsules environment are delivered by all three
types of engines regardless of the type. All features such as creating any type of Layout, charts, using
data-entry, split & splat and DataFlow procedures are supported on both types of InfoCubes.
RDB InfoCubes
An RDB InfoCube is an InfoCube for which data (the InfoCube cells) is physically stored in a table of a
relational database and not into the Board multidimensional database. The RDB InfoCube definition is
a protocol that maps fields of a relational table to the dimensions and the measure (in most cases a
value filed) of the InfoCube.
Whenever a user views the InfoCube in a report, an ODBC or an OLE DB connection to the external
relational database is established and data is retrieved from the relational table through a SQL
statement.
An RDB InfoCube accesses data from a relational database on the fly when.
In order to create, edit or view an RDB InfoCube it is necessary to have an R-Engine or a DualEngine license.
More details on RDB InfoCubes
Parent-Child databases
This feature allows to navigate from one database (the parent) to another one (the child) that has one
or more entities in common in one of the following two ways:
Drill-down: allows the end user to drill-down from the parent Board database to the child
database.
377
Go-to screen: allows the end user to navigate from a screen linked to the parent database
to another screen linked to a child database while preserving the selections made on the
parent database screen.
The purpose of this feature is to allow creating separate Board databases for storing information at
different levels of detail which facilitates database administration, development and maintenance,
however preserving the ability to navigate down and across databases as a unique environment.
Databases can be linked through a 1-to-N hierarchical relationship: a database, the "parent", can
have one or more "children" databases.
More details on Parent-Child databases
Named Selections
A named selection is a selection of entity members saved under a given name. The named selection
can be used in the Capsules environment and applied to analyses or applied in Procedures. For
example you can create a named selection called Summer Promotion Products which is made of
a set of items from the Product entity, then refer to the name Summer Promotion Products
whenever you need to use it in a Capsule screen or in a Procedure.
More details on Named Selection
Release Notes
Notes
It is required to update all Board programs simultaneously: BoardClient
version 5.5 cannot connect to prior versions of BoardMaster and
BoardServer programs and vice-versa the BoardMaster and BoardServer
version 5.5 doesn't accept connections from earlier versions of the
BoardClient program.
Board applications (databases and Capsules) created with prior versions
are fully compatible with the current upgrade and do not require any
migration or other change.
When upgrading a PC or a server from any earlier version you must
un-install the Board license. Licenses are fully compatible with
current 5.5 release therefore after running the BoardClient
BoardServer installation programs you can start using version
immediately.
not
the
and
5.5
Any existing license, created for Board version 5.0 (or earlier
versions) is an M-Engine license. Should you wish to utilize the new
Relational Engine technology, you must upgrade it to a Dual-Engine
license. Contact your Board reseller or distributor for more
information.
licenses
CMS-
379
Important notes
If you are upgrading from Board version 5.0 to version 5.5 you must not un-install your Board license.
The license KEY files created with prior versions of Board are fully compatible with the current 5.5
release therefore after running the BoardClient and BoardServer installation programs you can start
using version 5.5. immediately.
The new MASTER LICENSE (equivalent to the CMS-CONTEMPORARY USERS license) is not tied
to the directory where it has been created but only to the computer on which it is created, as for stand
alone licenses.
The half-KEY files created with KeyManager version 2 are 1,201 bytes in size. The certified KEY files
are 1,600 bytes in size.
Parent-child Databases
About Parent-Child databases
This feature allows to navigate from one database (the parent) to another one (the child) that has one
or more entities in common, in one of the following two ways:
Drill-down: allows the end user to drill-down from a report build on the parent Board
database to the same report but based on the child database.
Go-to screen: allows the end user to navigate from a screen linked to the parent database
to another screen linked to a child database while preserving the selections made on the
parent database screen.
The purpose of this feature is to allow creating separate Board databases for storing information at
different levels of detail which facilitates database administration, development and maintenance,
however preserving the ability to navigate down and across information residing in different
databases as a unique environment.
Databases can be linked through a 1-to-N hierarchical relationship: a database, the "parent", can
have one or more "children" databases.
The child database must have one or more entities in common with its parent database and
optionally some common InfoCubes. A child database can itself be the parent of another database.
Example 1
A typical example is that of an aggregate and a detail database. Consider for example an aggregate
database containing monthly information at Product Group and Sales Rep levels; the hierarchies
are illustrated in the following picture.
380
Release Notes
The child database, more detailed, stores the same information but at daily detail per single SKU and
Point of delivery - where SKU is a the most detailed level of the Product dimension and Point of
delivery is the most detailed level of the Customer dimension.
The following picture shows the hierarchical structures of the child database and highlights the
common entities.
381
By defining a child database relationship between the two databases, end users are able to drilldown to the InfoCubes stored in the detail database from a report made on the parent database or to
jump from a Capsule screen linked to the parent database to a screen linked to the child database
while the selection made on entities which are in common is retained across the screens.
Example 2
Another example is that of a corporate-subsidiary structure. Consider a corporation which owns three
companies: a commercial (Company A), a production (Company B) and a services company
(Company C). You need to design a Board application for financial controlling and management
reporting. Each of the subsidiaries has its own internal organization which significantly differs from
the others due to their different natures. For each subsidiary the specific data models (and
subsequent Board databases) needed for controlling differ however at a more aggregate level some
common structures exist. The corporate Board database holds data per Company and Corporate
reporting code level, where Company is an aggregation of profit centers and Corporate
reporting code is an aggregation of the chart of accounts. The structure of the corporation is
illustrated in the following picture.
382
Release Notes
The Board database for each subsidiary holds data a more detail level but can be rolled-up into an
entity which is also part of the corporate Board database. The corporate Board database can be
linked to the three subsidiaries databases thus allowing end users to navigate from the topmost view
down to the detail subsidiaries data.
Go to a Child-DB screen
Whenever navigating from one Capsule screen to another screen linked to a child database, the
selections made in the Dynabar and in Select, are retained from the first screen to the next one.
Note that this feature is generally more applicable than the drill-down from a parent to a child
database since it allows to synchronize screens containing reports structured differently, involving
different InfoCubes and only having some entities in common.
This feature is always enabled: whenever navigating from one screen to another, Board verifies if the
target screen is linked to a child database and consequently synchronizes entities selections.
383
Drill-down to a child-DB
To drill-down to a child database (Child-DB),
right click on the row to drill from: the drill-down window opens. A drop-down list displaying
the list of linked databases is available in the lower part of the drill-down window. Note that
this selection list-box only appears when Board detects a child database.
select the desired child database: the list of entities from the child database will be shown.
Named Selection
A named selection is a selection of entity members saved under a given name. The named selection
can be used in the Capsules environment and applied to analyses or applied in Procedures. For
example you can create a named selection called Summer Promotion Products which is made of
a set of items from the Product entity, then refer to the name Summer Promotion Products
whenever you need to use it in a Capsule screen or in a Procedure.
Note that named selections are dynamic: if the members set is updated or changed, then the
change will reflect immediately on all Capsule screens and Procedures which refer to that named
selection.
It is possible to define named selections on time entities, for example to define the current month
however you may also use the predefined Dynamic Time selections.
384
Release Notes
switch to design mode, and select the Selections icon from the database design functions
menu as illustrated
type the name of the selection in the first column, then click on the second column to select
the entity on which you want to define the named selection
Click on the Current Selection button to select the desired items then press the OK button
to save your named selection.
open the desired Capsule screen then switch to design mode (by pressing the F4 function
key),
385
the list of existing Named Selections and the predefined Dynamic Time Selections
appears,
Note that the list of Named Selections (white background) is preceded by the Dynamic
Time Selections.
If you wish to apply the selection immediately, click the button to the right of the checkbox,
otherwise close the select window, in which case the selection will be applied only after the
screen is reloaded or after pressing the F5 function key,
386
click the Select button then click the Selection button found on the Select window
Release Notes
Note that the list of Named Selections (white background) is preceded by the Dynamic
Time Selections.
Previous Month
Year to Current
Month
Year to Previous
Month
Today
Selects today.
Yesterday
Selects yesterday.
Year to Date
Selects the days from the first of January to the current day.
Year
yesterday
to
Note that it is also possible to use Named Selections on time entities to define other types of
selections not included in the above list.
open the desired Capsule screen then switch to design mode (by pressing the F4 function
key),
387
the list of existing Named Selections and the predefined Dynamic Time Selections
appears,
enable the desired Dynamic Time Selection by clicking on the corresponding checkbox,
If you wish to apply the selection immediately, click the button to the right of the checkbox,
otherwise close the select window (in this case the selection will be applied only after the
screen is reloaded or after pressing the F5 function key)
388
Click the Select button then click the Selection button found on the Select window
Release Notes
389
To select an entity or an InfoCube either click the checkbox or drag and drop it onto the
Main tab as illustrated.
Note that when you select an InfoCube, all entities which are one of the InfoCube's
dimensions are automatically selected. For example, if you select the InfoCube Gross Sales
which is dimensioned by Customer-Product-Month, then the entities Month, Product
code and Customer code are automatically added to your fields selection since they are
necessary in order to load that InfoCube.
For each selected field you must define the starting position and field width field to read
from the file. To do so you may
or click on starting position in the lower window which displays the text file
record, then highlight the entire field (keep the left mouse button pressed) and
filannyl drag and drop the mouse over to corresponding entity or InfoCube to
feed as illustrated in the following picture
390
Release Notes
The column with a blue background shows a preview of the data from the first
record of the text file. You may scroll records by clicking the arrows at found
in the lower left part of the window,
For each Entity and InfoCube field (except standard time entities), set the Append or
Replace option as desired. Click once on the yellow cell to select the desired option. Refer to
the paragraph Append and Replace options for details.
The Divide by field is optional and only applies to numeric InfoCubes: it divides incoming
data by the specified value. For example, type 1000 to divide values in the source file by 1000.
Note that you can easily define complex transformation formulas using an ETL
protocol.
Press OK to save the DataReader protocol.
Note! The DataReader cannot read text files exceeding 2GB in size. This limit only
applies to text files.
391
Select the entities and InfoCubes to feed: the list window located on the right displays all
entities and InfoCubes of the current Board database.
To select an entity or an InfoCube either click the checkbox or drag and drop it onto the
Main tab as illustrated.
Note that when you select an InfoCube, all entities which are one of the InfoCube's
dimensions are automatically selected. For example, if you select the InfoCube Gross Sales
which is dimensioned by Customer-Product-Month, then the entities Month, Product
392
Release Notes
code and Customer code are automatically added to your fields selection since they are
necessary in order to load that InfoCube.
Select the data source connection: the RDB drop-down list only shows the recently used
ODBC and OLE DB connections.
To select an existing ODBC connection which is not listed in the RDB list, click the
connection icon as illustrated
then select the ODBC Data Source Name (DSN) from the ODBC drop-down list as shown in
the following illustration,
If required, type the user name and password to log on the source relational database in the
corresponding fields.
Select the RDBMS type from RDBMS the drop-down list. If the relation database you are
connecting to is not listed, set the type to General.
After connecting to the data source name, the tables and views of the relational data
source are listed in the RDB area (see illustration below).
Select the desired table or view: either click on the table check box or click on the
table then drag & drop it onto the white area as illustrated.
393
Drag and drop the table fields in the cell next to the entity or InfoCube you want to feed, as
illustrated.
You may double click on the table title bar to view the fields data types and a sample
record. Refer to ODBC DataReader options for details on how to configure the automatic data
type conversion of the table fields to Board's internal data types.
394
Release Notes
Optionally, you can then edit a field and type an expression. You may, for example, wish to
divide or multiply a field. Double-click on the field you want to edit, then, using the commands
and syntax supported by the ODBC driver used, type in the expression.
Note that if you need to define complex transformation formulas you may use the ETL
module.
If you have selected more than one table set the join conditions by dragging and dropping the
fields to be joined. The Join window shows the defined conditions. The join statement
generated is an equal join (natural join). If you need to define a different type of join, for
example an outer join or a left join, you may edit the SQL statement (refer to Editing and
Testing an SQL statement for details).
Note that by changing the Join option, you can alter the syntax used for writing the Join
statement.
To define a Where condition click the Where tab and type the desired condition. Note that you
may drag&drop a field from the selected table onto the text area to avoid retyping.
395
For each field (except standard Board Time entities), set the Append/Replace option as
desired. Click on the yellow cell to set the option as desired. Refer to the paragraph Append
and Replace options for details.
Defining an ODBC Data Reader protocol generates an SQL statement. When the protocol is
launched, Board sends the SQL statement to the ODBC or OLE DB provider and waits for the results.
Note that the SQL statement is entirely executed by the ODBC or OLE DB provider therefore the
commands and syntax which can be used in the SQL statement entirely depend on the ODBC or OLE
DB provider used.
It is recommended to test the protocol SQL statement using the Browse function: click the Browse
button as shown is the illustration. The query will be executed on the first 200 rows and the resulting
data is displayed in spreadsheet.
Note that Board is not a SQL query generator, if complex queries are needed it is recommended you
use an ad-hoc query tool to create and test the SQL statement.
396
Release Notes
type the connection name in the Name field then click the OLE-DB Wizard button.
397
Note that the list of OLE DB providers listed will vary depending on your computer's settings.
Select the desired OLE DB provider and follow instructions for configuring the connection.
The configuration parameters and setup steps will vary depending on the chosen OLE DB
provider.
When the configuration is finished, press the OK button. The OLE DB connection wizard will
close and a connection string will automatically appear in the Connect String field as in the
following example.
Optionally, select the RDBMS type. If the relation database you are connecting to is not
listed, set the type to General.
If required, type the connection user name and password to log on the relational database
provider.
Click the Save & Connect button to save the connection definition and connect to the data
source.
Release Notes
Click the Add button and follow the instruction for configuring other required parameters.
After you have created a new ODBC connection, you must close and restart Board in order to view
the newly created ODBC connection in the RDB drop-down list.
399
Sets the maximum number of seconds for a query. Typing the value -1 sets the timeout to unlimited.
Join
Syntax
Sets the syntax used for Join conditions. The "Where" option defines the join
conditions using the WHERE clause, the "Join" option uses the INNER JOIN clause.
Note that the result of the query is the same, regardless of the syntax used however if
you need to define an OUTER JOIN (or other type) it is recommended using the Join
option and then changing the INNER JOIN clause only (click the Manual tab to edit
the SQL statement) instead of completely rewriting the statement generated by
Board.
Data
type
By setting this option to Convert the system will automatically apply a transformation
formula whenever the data type and format of the source table fields differs from data
type and format expected by the Board.
This option is applicable only if the RDBMS field of the ODBC or OLE DB connection,
which indicated what is the relational database you are connecting to, has been set to
one of the available options other than General.
Date
Format
This option applies to certain RDBMS types only, it specifies the physical format of a
date field. This option is automatically enabled when applicable.
Set it to
Number, when date fields of the relational database are in the format of a
serial number.
Text, when date fields of the relational database are in text format.
RDB InfoCubes
About RDB InfoCubes
An RDB InfoCube is an InfoCube for which data (the InfoCube cells) is physically stored in a table of
a relational database and not into the Board multidimensional database. The RDB InfoCube definition
is a protocol that maps fields of a relational table to the dimensions and the measure (in most cases
a value filed) of the InfoCube.
Whenever a user views the InfoCube in a report, an ODBC or an OLE DB connection to the external
relational database is established and data is retrieved from the relational table through a SQL
statement.
An RDB InfoCube accesses data from a relational database on the fly when.
400
Release Notes
In order to create, edit or view an RDB InfoCube it is necessary to have an R-Engine or a DualEngine license.
Then click the Query Builder icon to access the protocol definition window,
The protocol definition window shows the InfoCube's dimensions and measure that must be
mapped to the relational table. Select the ODBC or OLE DB connection from the RDB dropdown list. The RDB drop-down list only shows the recently used ODBC and OLE DB
connections.
401
To select an existing ODBC connection which is not listed in the RDB list, or to create a
new OLE DB connection, click the connection icon as illustrated
then select the ODBC Data Source Name (DSN) from the ODBC drop-down list as shown in
the following illustration,
If required, type the user name and password to log on the source relational database in the
corresponding fields.
Select the RDBMS type from the RDBMS drop-down list. If the relation database you are
connecting to is not listed, set the type to General.
Click the Save & Connect button.
For details on how to create and configure a ODBC or OLE DB connections refer to paragraph
Defining an OLE DB or an ODBC connection.
After connecting to the data source name, the tables and views of the relational data
source are listed in the RDB pane.
Release Notes
refer to Creating a new table to store an RDB InfoCube
Drag and drop the table fields in the cell next to the entity or InfoCube you want to feed, as
illustrated.
403
You may double click on the table title bar to view the fields data types and a sample record.
Refer to ODBC DataReader options for details on how to configure the automatic data type
conversion of the table fields to Board's internal data types.
Optionally, you can then edit a field and type an expression. You may, for example, wish to
divide or multiply a field. Double-click on the field you want to edit, then, using the commands
and syntax supported by the ODBC driver used, type in the expression.
If you have selected more than one table, set the join conditions by dragging and dropping the
fields to be joined. The Join window shows the defined conditions. The join statement
generated is an equal join (natural join). If you need to define a different type of join, for
example an outer join or a left join, you may edit the SQL statement (refer to Editing and
Testing an SQL statement for details).
Note that by changing the Join option, you can alter the syntax used for writing the Join
statement.
404
To define a Where condition click the Where tab and type the desired condition. Note that you
may drag & drop a field from the selected table onto the text area to avoid retyping.
Release Notes
It is recommended to test the SQL statement using the Browse feature: click the Browse button as
shown is the illustration. The query will be executed on the first 200 rows and the resulting data is
displayed shown.
WARNING
If you plan to write-back on the RDB InfoCube, through manual data entry or
through Dataflow Procedures, refer to the section RDB InfoCube setup options
to understand how the table update methodologies work and choose the correct
record update strategy.
A new table having all dimension fields of the InfoCube and a value field is created.
The primary key of the table is the combination of all dimension fields and one index is created on
each dimension field of the table.
To allow Board creating a table in the source relational database system, the ODBC or OLE DB
connection utilized must have sufficient privileges to do so.
Optionally, and only if the RDB InfoCube will be utilized for data-entry or for DataFlow
calculations, you may add up to three additional fields as follows:
User_ID
Writes the user ID of the Board user that has created or modified the
table record.
Date_Created
Writes the date and time (time stamp) of when the record is created.
Date_Modified
Writes the date and time (time stamp) of when the last record update.
Note that these additional fields are not part of the InfoCube dimensions and are primarily meant
for auditing and monitoring purposes.
406
Release Notes
By enabling this option, Board will change the SQL statement adding a SUM operator on the value
field and a GROUP BY clause the dimension fields as in the following example:
SELECT ...., SUM(OrderDetails.Quantity) FROM ... GROUP BY DeliveryDate,
CustomerID
To optimize performance of the RDBMS make sure that the dimension fields of the table are indexed.
Referring to the above example, the fields DeliveryDate and Customer should be indexed.
Optimizing the SQL statement: setting the WHERE conditions rules
When an RDB InfoCube is used in a report, in order to retrieve data from the relational table Board
generates an SQL statement with a WHERE condition that limits the table records accordingly to the
selected entity members. For example if the user makes a selection on the entity Month, then a
WHERE condition on the field corresponding to the date dimension is dynamically added to the SQL
statement. The way the WHERE conditions are written affects the response time of the SQL queries.
There are two parameters that allow to tune the efficiency of the SQL queries generated by Board.
In some cases the selection made on entity members may determine a WHERE condition with a very
high number of items. Suppose the user sets a selection on an entity located in the upper levels of a
hierarchy, for example Region=North America, then this selection will propagate down to the
CustomerID entity and embrace a very large number of customers, for example several thousands.
An SQL statement with a WHERE condition that looks up thousands of codes can be inefficient and
may easily exceed the maximum command length supported by the ODBC or OLE DB provider driver
you are using.
The parameter Where IN( ) Buffer size defines the maximum number of items that are added to
a WHERE condition of a single SQL command. When this threshold is exceeded, instead of running a
single SQL command with a very large WHERE clause, Board runs multiple SQL commands each
with subset of conditions; the results of the SQL queries are then merged by the BoardServer engine
and aggregated to the required view.
The IN( ) option (see illustration below) allows to completely disable the feature that dynamically adds
the WHERE conditions to the SQL statements. This option should be enabled only on the entities that
have a small number of occurrences or entities on which the number of selected members is always
high in percentage (for example if 70% or more of the total number occurrences are always embraced
by the user's selection).
407
Clear/Update
This option is suitable when the relational table contains other fields than those
which are mapped to the dimensions and the measure of the RDB InfoCube.
When this option is chosen,
when data is saved to a cell of the InfoCube corresponding to an existing
record then the record is updated through an UPDATE.
when data is saved to a cell of the InfoCube which does not correspond to
any existing record then a new record is added to the table through an
INSERT command.
when an existing cell of the InfoCube is cleared (or set to zero), the
corresponding record is updated by setting the value field to zero.
Note that using this method, Board either adds new records or alters existing
ones, it never removes records from the relational table, therefore preserving the
status of other fields.
Delete/Insert
This option is to be preferred when the relational table exactly matches the
structure of the RDB InfoCube: each field of the relational table is mapped to a
dimension of the InfoCube or to the InfoCube measure, and the table primary key
is the set of fields which are mapped to the InfoCube dimensions.
When this option is chosen,
when data is saved to a cell of the InfoCube corresponding to an existing
record then the record is updated through an UPDATE.
when data is saved to a cell of the InfoCube which does not correspond to
any existing record then a new record is added to the table through an
INSERT command.
when an existing cell of the InfoCube is cleared (or set to zero), the
corresponding record is deleted from the table.
To set the Record Update Method, click the Options tab then select the desired option.
Other options
Details about the following other options: Query time-out, Data Type, Join syntax and Date
Format,
are documented in the ODBC DataReader options section.
Release Notes
To access the Dynabar Period Option configuration, right click on the Dynabar.
Forecast function
When using the Forecast function in a Layout, it is now possible to exclude from the historical base
used to calculate the forecast figures, the current period data. This is particularly useful when
applying the Forecast function to an InfoCube structured by Month which is loaded with data on a
daily basis and therefore the current month is generally not statistically significant as it only contains
partial data (i.e. data from the first day of the month up to the current day).
409
If the user clicks Yes, the procedure continues running (the next action is executed), if the user clicks
the No button the procedure terminates.
To create a Yes/No pop-up message, enable the Yes/No check box found in the configuration panel
of the Show Message action as illustrated.
Release Notes
Microsoft(r) Excel
HTML format
XML format
Text file with character delimited fields
Text file with tab separated fields
To save a DataView report to a file,
- drag & drop the printer icon from the bottom toolbar onto the DataView,
- click the File tab and select the desired file format as shown
Note that the Microsoft (r) Excel format supports up to 36 thousands rows only therefore if you select
this option make sure that the DataView doesn't exceed this limit. Other formats do not have this size
limit.
When selecting the character delimited fields format it is possible to define the separator character.
Drill-triggered Procedures
It is now possible to trigger a procedure by clicking on a the row heading of a DataView report or
double clicking on a cell (in a similar way to the drill-down), the procedure is executed with a
selection on the entity member on which the user clicked.
This new feature is useful when, in a Board application, you want to let the user choose a Board
Procedure from a list and run it on range of cells. Let's consider for example a Board application that
performs a cost allocation: the Expenses InfoCube holds monthly costs from the accounting system;
the user should allocate these costs to the various Cost Centres applying different allocation criteria.
Each allocation criteria corresponds to a different Board Procedure. The user wants to be able to
freely select the allocation criterion for a given expense depending on the expense nature and other
considerations.
In the following illustration a DataView object shows the Expenses InfoCube (first column) and the
Allocated Expenses InfoCube (detailed by Division) which is the result of the allocation process. By
clicking on a row header the user is shown a list of procedures and can choose which one to run for
that particular expense only.
411
highlight the procedures that the user may choose to run. Note that if you select one
procedure only, it will be executed immediately when the user clicks on the row header.
Note that when the user triggers a procedure by clicking on a row (or by double clicking on a cell)
the procedure is started as if the user made an selection (through the Select function) on the entity
member which is by row.
412
Release Notes
For example, consider a Board database with a Customer hierarchy, a Product hierarchy and some
InfoCubes having a sparse structure Customer-Product. After having selected one or more
Customers, it is possible to use the Customer-Product sparse structure to propagate the selection to
the Product entity.
To enable a selection to propagate through a sparse structure, open the Select function and click on
the Sparsity icon located in the lower right corner.
The list of existing sparse structures is displayed. Click the checkbox of the sparse structures that
should be enabled for the selection propagation.
Then select one or more items of an entity part of the chosen sparse structure, the selection is
propagated to other entities part of that structure.
413
414
Release Notes
Type the Capsule Designer password then to define a User password, type user=
[password] as in the following example,
In the above example the Designer password is HGDTS and the User password is ABC.
Note that the password protection applies to the entire Capsule and not a single screen.
415
416
Release Notes
The Capsule screens list window appearing when clicking the Menu icon has been resized and
now displays a larger number of screens as illustrated in the following example.
Drill-Through
417
New Features
Online Help
Pressing the F1 function key now invokes the Board Help. The Board Help must be installed by
running the Board Help setup program available in the download area.
Folder object
The appearance of the Folder object can now be customised. It is possible select different
shapes and colors. The new configuration settings are illustrated hereafter,
418
Release Notes
Refer to the online help for more details on the self-recovery parameters, click Options tab.
420
Index
0
02 of 04 ...............................................................66
24
10
considering ..................................................... 88
deleting ............................................................79
24x500x1000 ..................................................... 88
10 Lite .................................................................34
10 User ...............................................................49
100
meaning ........................................................153
10px;60px .........................................................366
100,000
1003x ................................................................336
12 User ...............................................................49
32px;107px;782px............................................ 366
15
default ...........................................................219
400px ................................................................366
36px ..................................................................366
29px;201px;36px ..............................................366
425px;327px;36px ............................................366
1GB .....................................................................22
20
exceeding ......................................................311
20 Lite .................................................................49
200
number ..........................................................354
2000
selects January .............................................275
2002.2006
shift ..................................................................64
2004
maintitle Monthly Sales .................................281
Q1....................................................................65
Q2....................................................................65
10px;50px;600px ..............................................363
800x600 ..............................................................19
A
A rapid application ............................................379
A value ..............................................................225
Acme .................................................................. 63
A& .....................................................................163
A&b ...................................................................163
A/b.............................................................163, 225
A/dt....................................................................163
A/gt....................................................................163
A/rt ....................................................................163
A1......................................................................308
A2......................................................................308
124,
210,
239,
332,
421,
127,
213,
271,
333,
422,
A3......................................................................308
A31....................................................................308
A32....................................................................308
Activate .............................................................. 23
CMS ............................................................... 23
ABC...................................................................414
Able to ...............................................................379
Enable ............................................................ 40
Index
City ................................................................216
Dynabar .........................................................324
entity members..............................................140
JavaScript .....................................................274
JavaScript functions ......................................274
new version .....................................................95
State ..............................................................216
WHERE .........................................................411
Additional ..........................................................411
Address ...............................................................92
Admin ................................................................121
Administrative ...................................................401
Administrator's ............................................52, 125
Administrator's Board .......................................242
Administrator's PC ..............................................59
Advanced ..................................................232, 251
Adventure Works ..............................................289
Alert131, 158, 162, 173, 176, 196, 199, 200, 201,
202, 203, 204, 210, 211, 251, 272, 297, 324,
336, 363, 366, 373, 422, 424
150,
176,
229,
260,
283,
326,
352,
379,
152,
178,
230,
262,
289,
327,
354,
382,
Creating .........................................................202
Using .............................................................203
Alias ....................................................................36
Aligment ............................................................213
Use ................................................................213
Align ............................................. 95, 96, 264, 421
Use ..................................................................95
Align Vertically ..................................................421
Aligning ...............................................................96
Aligning InfoCube versions .........................96, 231
Alignment ..........................................................180
All1, 2, 5, 7, 9, 12, 13, 15, 16, 25, 28, 29, 32, 35,
39, 40, 43, 50, 53, 54, 59, 60, 62, 63, 64, 68,
70, 73, 74, 77, 78, 79, 80, 83, 86, 87, 88, 89,
90, 92, 93, 96, 97, 99, 100, 102, 104, 105, 106,
108, 112, 121, 122, 129, 130, 131, 133, 134,
Enable .............................................................29
BoardClient .....................................................23
AllRows .............................................................279
Analytical ......................................................71, 85
Choosing .......................................................... 7
Architecture allows ............................................... 7
Architecture requires ............................................ 7
Board license of................................................ 7
Architecture uses ................................................. 7
server's ............................................................. 7
Area ......................................... 188, 202, 203, 279
Area & Value .................................................... 202
Area Manager .................................................. 289
linked ............................................................ 289
Area Manager entities ................................ 81, 289
Area Manager entity item ................................. 289
Area option............................................... 201, 203
AREAMGR ....................................................... 289
Args .................................................................. 285
String ............................................................ 285
ARIMA .............................................................. 168
Arkills ............................................................... 305
AS400 erroneous ............................................. 375
AS400 table ..................................................... 375
ASCII ................................ 106, 235, 283, 375, 392
number ......................................................... 283
ASCII file .......................................................... 112
AsDate ............................................................. 275
Ask ................................................................. 8, 19
Ask Password .................................................... 40
ASP .................................................................. 241
ASP file ............................................................ 356
ASP page ................................. 244, 283, 285, 356
Index
AsPicture ..........................................................275
Assigments .......................................................300
Assign License....................................................34
Assigning ................... 34, 70, 73, 83, 86, 127, 215
CustomerCity ................................................83
Product Group ...............................................215
refer ...........................................................73, 86
relationship ..........................................73, 83, 86
relationships ....................................................70
security profile ...............................................127
AsText ...............................................................275
At any ................................................................224
Attendee button ................................................135
Attending ...........................................................135
Briefing ..........................................................135
August 2003......................................................168
July 2004 .......................................................168
August 2004......................................................168
Authentication and ............................................299
Authentication as ..............................................299
BoardMaster performs ..................................299
Authentication successful .................................299
Authorized ...........................................................34
Authorized Visitor..........................................29, 34
Auto...................................................................148
enable ...........................................................148
Auto num ............................................................54
Autofit ................................................................336
AutoGo ..............................................................182
AutoGo option ...................................................182
button having.................................................182
Automatic roll-up rule ................................308, 327
Autorefresh ...............................................251, 363
Autorefresh option ............................................259
AutoResume .......................................................35
AutoResume Enable .........................................354
AutoResume feature ...................................35, 424
Autosize ............................................................315
enable ...........................................................315
Autosize function ..............................................315
Blue ...................................................................352
Bmd.....................................................................59
426
Index
Board sends..............................................108, 395
Board StandAlone...............................................39
Board Toolkit.........................................................2
allowing .......................................................... 23
Cases ........................................................... 335
causing ......................................................... 333
clicking .......................................................... 7, 8
closing ............................................................ 53
configuring ................................................ 36, 40
deploy ........................................................... 309
installing ................................................... 19, 43
number ........................................................... 16
provoking ...................................................... 307
restart ........................................................... 349
run ................................................................ 133
upgrade ................................................ 289, 309
used .................................................................. 7
BoardClient 5.6 ................................................ 354
BoardClient computers ........................................ 9
BoardClient configuration .................................. 23
BoardClient configuration window ........... 297, 372
BoardClient environment ......................... 333, 366
BoardClient F7 function ................................... 333
BoardClient icon................................... 7, 8, 39, 40
clicking .......................................................... 7, 8
BoardClient installation ........ 8, 289, 309, 340, 382
BoardClient on c .......................................... 39, 40
BoardClient User.............................................. 372
Redirect .........................................................285
SSO ...............................................................283
427
BoardClientSetup..........................................39, 40
BoardCSS .........................................................366
Board-Management Intelligence...........................1
Installing ..........................................................52
start ................................................................ 25
Internet ............................................................17
stop .................................................................53
stopping ...........................................................53
260,
340,
BoardMaster counts......................................43, 51
BoardMaster delegates.....................................300
stopping ...........................................................52
cause .............................................................. 53
kill ................................................................. 116
number ........................................................... 15
restart ............................................................. 36
428
Index
BoardServer completes ......................................15
Changes ........................................................332
Creating .........................................................180
C 7, 25, 29, 36, 39, 40, 45, 48, 53, 59, 62, 63, 67,
74, 106, 112, 117, 163, 225, 232, 241, 243,
267, 283, 327, 339, 375, 383, 392, 422, 424
C_YYYYMM ....................................................... 55
Index
Refresh Tree .................................................267
Save ..............................................................267
CALL THE JAVA CLASS ..................................285
Cannot be ...........................................................59
Capsues Tree Navigator ...................................336
Capsule design concepts .................................149
Capsule Designer .............................................414
Capsule Designer environment ............................2
Capsule Locking ...............................................153
Capsule Locking icon................................151, 414
Capsule name...................................................335
clicking ..........................................................335
Capsule object model .......................................131
Capsule procedures79, 115, 117, 148, 251, 280,
366
Capsules2, 5, 7, 11, 12, 15, 19, 29, 36, 39, 40, 43,
44, 53, 55, 59, 63, 74, 77, 79, 80, 87, 115, 117,
129, 130, 131, 133, 134, 142, 145, 147, 148,
149, 150, 151, 152, 153, 154, 155, 157, 158,
182, 183, 188, 199, 202, 204, 206, 207, 208,
227, 228, 229, 234, 239, 241, 242, 251, 264,
265, 271, 280, 289, 297, 307, 308, 309, 310,
311, 315, 320, 324, 329, 332, 333, 335, 336,
339, 340, 341, 344, 349, 352, 362, 363, 366,
372, 373, 375, 379, 382, 383, 386, 387, 390,
414, 422, 424
generated from ............................................. 362
Go ................................................................. 366
Opening ................................................ 131, 148
Protecting ..................................................... 151
Understanding .............................................. 150
Capsules having .............................................. 297
Capsules made .................................................... 2
Scheduling ....................................................148
picture ...........................................................336
129,
153,
241,
336,
383,
130,
183,
271,
339,
386,
131,
188,
289,
344,
387,
133,
204,
320,
352,
390,
134,
206,
324,
362,
414,
changes to.....................................................333
deleting ..........................................................147
Capsule structure......................................129, 150
Capsule Themes.......................................339, 352
Capsule Tree Navigator ....................................336
Capsule use ......................................................148
Capsule User Password ...................................336
CapsuleA ..........................................................229
CapsuleB.......................................................229
return .............................................................229
CapsuleB ..........................................................229
CapsuleA.......................................................229
CapsuleName ScreenName .............................264
BoardClient................................................... 335
inconsistencies ............................................. 307
Standalone ..................................................... 36
Web Replicator ............................................. 363
Cause ..................................... 48, 50, 53, 297, 333
BoardClient................................................... 333
BoardServer ................................................... 53
Dataview....................................................... 297
Key file ...................................................... 48, 50
Cell67, 74, 76, 86, 87, 88, 91, 92, 93, 96,
106, 108, 112, 115, 118, 119, 122, 126,
140, 163, 166, 167, 168, 173, 176, 186,
204, 205, 206, 211, 219, 224, 231, 251,
271, 272, 275, 289, 297, 308, 311, 315,
320, 322, 324, 335, 339, 341, 344, 349,
366, 379, 392, 395, 405, 407, 411, 414
104,
136,
187,
262,
318,
363,
Cell D6 ..............................................................112
name .............................................................. 63
Cell E3 ..............................................................112
Cell F3 ..............................................................112
Channel.............................................................. 81
time ...............................................................104
computer ........................................................ 16
CENTER ...........................................................285
verify ................................................................48
Certify .................................................................40
CMS ................................................................40
CFG ..................................................................237
Change depending .............................................90
Change existing ..................................................29
Change existing Procedures ............................414
Changed from ...................................................333
Changes15, 19, 23, 29, 32, 36, 40, 49, 52, 53, 55,
59, 63, 65, 71, 74, 77, 79, 87, 90, 104, 106,
108, 111, 126, 127, 130, 133, 136, 142, 143,
145, 154, 155, 158, 167, 173, 176, 190, 192,
205, 207, 208, 211, 244, 251, 259, 260, 264,
272, 279, 285, 289, 297, 307, 308, 310, 311,
315, 332, 333, 335, 336, 340, 341, 349, 352,
354, 356, 362, 366, 372, 373, 375, 382, 387,
395, 404, 407, 411, 414, 421, 422, 424
Button ............................................................332
Changes according ...........................................211
Changes included .....................................336, 414
Changes made ...................................................32
Changes to .......................................................333
Capsule screen .............................................333
current screen ...............................................333
432
Index
Child-DB relationship ........................................386
Child-DB screen................................................386
Child-to-parent ..............................................71, 85
Choose6, 7, 19, 29, 65, 70, 76, 78, 83, 134, 135,
136, 176, 181, 206, 219, 224, 232, 235, 261,
289, 311, 324, 326, 329, 332, 347, 352, 356,
379, 387, 390, 407, 411, 414
architecture .......................................................7
Validation...................................................... 216
Citrix ....................................................................19
City4, 81, 82, 83, 87, 105, 119, 133, 138, 166,
170, 216, 269, 278, 281, 289, 329, 366
add ................................................................216
Customer .........................................................83
include ...........................................................119
Stop ................................................................ 36
Undo icon ..................................................... 158
CMS7, 8, 9, 12, 23, 25, 28, 29, 36, 40, 43, 44, 48,
49, 51, 52, 382
activate ........................................................... 23
Customer .......................................................105
certify .............................................................. 40
CityState ...........................................................86
define .............................................................. 40
Enable .............................................................. 8
Classic ..............................................................352
purchased....................................................... 40
Clicking ............................................................80
press .............................................................115
stopping .......................................................... 36
Upgrading ....................................................... 49
Clear function......................................................79
CMS architecture ......... 12, 13, 15, 16, 36, 40, 127
Clear/Update.....................................................411
Clearing ..............................................................97
InfoCube ..........................................................97
Clicking7, 8, 36, 44, 45, 46, 62, 80, 108, 119, 158,
216, 229, 289, 297, 333, 335, 341, 363, 414
Apply .............................................................341
BoardClient ...................................................7, 8
BoardClient icon ............................................7, 8
Capsule name ...............................................335
Clear ................................................................80
FlowChart ......................................................333
No ..................................................................414
Codeparent .......................................................70
ColorCoding ......................................................424
BoardMaster ................................................... 36
Colouring ..........................................................352
Company.......................................................... 383
Complete ............................................................ 50
uninstall .......................................................... 50
Component connections ...................................... 9
entities ...........................................................352
characteristics ................................................ 16
Column Nr .........................................................211
new ................................................................. 48
Columns34, 68, 76, 82, 83, 86, 89, 90, 93, 95, 96,
106, 107, 112, 119, 122, 123, 124, 125, 126,
139, 140, 158, 162, 163, 165, 166, 167, 168,
170, 176, 178, 179, 186, 188, 189, 193, 194,
195, 196, 199, 200, 202, 203, 205, 206, 207,
208, 209, 211, 213, 216, 219, 224, 225, 237,
239, 247, 251, 260, 262, 269, 272, 275, 278,
279, 289, 297, 307, 308, 311, 315, 318, 319,
320, 322, 324, 333, 335, 336, 339, 341, 349,
352, 354, 356, 366, 372, 375, 387, 392, 405,
414, 421, 424
434
Index
Thursday .........................................................66
Contemporary User............................................ 34
following ......................................................... 34
number ............................................................34
Confidentiality .....................................................29
regards ............................................................29
ContemporaryUsers ........................................... 40
ODBO ............................................................289
press .............................................................112
24 ....................................................................88
Month ............................................................414
Sales .............................................................105
Considerl .............................................................76
Country .............................................................. 92
Containing a......................................................335
email ..............................................................239
username ......................................................282
Cpz....................................................................150
Creating7, 29, 32, 44, 45, 50, 59, 62, 74, 92, 93,
95, 106, 108, 116, 119, 151, 154, 155, 180,
183, 184, 185, 188, 189, 193, 194, 196, 199,
202, 204, 206, 207, 208, 210, 211, 216, 227,
247, 268, 283, 289, 356, 366, 395, 401, 405,
411, 414
3D ..................................................................211
Alert ...............................................................202
BOARD .........................................................268
BoardSSO .....................................................283
Button ............................................................180
Cockpit ..........................................................199
datareader .......................................................92
DataView .......................................................185
Drill ................................................................119
Drill-Through protocol....................................119
436
Dimensioning.................................................. 15
Criteria corresponds......................................... 414
CRM ............................................. 17, 61, 102, 379
CRM application............................................... 282
Crtl key ............................................................. 260
keep .............................................................. 260
Css ........................................... 241, 272, 281, 366
CSS file .................... 251, 272, 274, 281, 336, 366
edit ................................................................ 272
pages use ..................................................... 272
CssFileName ................................................... 272
Ctrl key ..................................................... 190, 341
hold ............................................................... 341
Cumulated Counter .......................................... 165
Cumulated Value ............................................. 165
Cumulated Vertical........................................... 165
Current ..................................... 297, 311, 329, 387
add ............................................................... 311
Current Month .......................................... 379, 390
Index
Current Period ..................................................414
Customize .......................................................... 65
Quarter ........................................................... 65
changes to.....................................................333
Cutt .................................................................... 25
Curson ..............................................................228
drop ...............................................................228
Cyrillic ................................................................ 23
Custom time ......... 61, 65, 67, 68, 69, 70, 168, 375
Defining ...........................................................67
Custom time entity 61, 65, 67, 68, 69, 70, 168, 375
level ...............................................................383
Data1, 2, 4, 9, 16, 17, 19, 25, 29, 35, 36, 43, 53,
54, 59, 61, 62, 63, 64, 65, 66, 74, 76, 77, 78,
79, 80, 81, 83, 86, 87, 88, 90, 91, 92, 93, 95,
96, 97, 102, 104, 105, 106, 107, 108, 111, 112,
114, 115, 116, 117, 118, 119, 123, 124, 125,
126, 127, 129, 131, 133, 136, 138, 142, 144,
145, 146, 147, 148, 149, 150, 152, 157, 158,
162, 163, 167, 168, 170, 176, 178, 179, 185,
186, 187, 188, 189, 192, 193, 194, 195, 196,
199, 200, 202, 203, 204, 208, 209, 211, 213,
215, 216, 219, 222, 224, 225, 227, 231, 232,
235, 237, 239, 241, 242, 247, 251, 258, 261,
262, 264, 269, 271, 272, 275, 279, 289, 297,
305, 308, 311, 315, 322, 327, 332, 333, 335,
336, 339, 349, 354, 356, 366, 375, 379, 383,
392, 395, 401, 404, 405, 407, 411, 414, 424
loading .............................................................76
read ...............................................................105
Loading......................................................... 107
use ................................................................414
Customer Category...........................................224
CustomerCity ..............................................82, 83
assign ..............................................................83
CustomerCityState..........................................86
CustomerCountryState .....................................4
Data model......................................................... 91
CustomerState ..................................................82
CustomerID .......................................................411
Defining ...........................................................67
Custom time entity Season .................................68
Customer4, 36, 59, 76, 81, 82, 83, 87, 88, 89, 92,
93, 105, 106, 108, 116, 118, 119, 166, 216,
232, 269, 278, 279, 305, 326, 339, 354, 366,
375, 383, 392, 395, 405, 411, 414
City ..................................................................83
City relationship.............................................105
exclude ............................................................59
involving ........................................................216
Deleting .........................................................115
Interrupting ....................................................116
Running .........................................................115
Data resulting....................................................158
Dataview....................................................... 297
Data staging......................................................102
approach .........................................................59
Accessing ........................................................60
Datatabases ......................................................... 5
438
Index
DataView93, 149, 153, 158, 163, 168, 176, 185,
186, 188, 192, 193, 204, 206, 207, 208, 209,
210, 211, 224, 225, 234, 237, 239, 262, 264,
289, 297, 307, 308, 311, 318, 319, 320, 322,
324, 329, 335, 336, 339, 341, 344, 352, 354,
363, 366, 372, 373, 375, 414, 421, 422, 424
causing ..........................................................297
Creating .........................................................185
Dataentry.......................................................297
Datreader ........................................................... 53
enable ............................................................. 67
occurring .......................................................336
importing....................................................... 375
translating......................................................336
DayMonth......................................................... 68
Dataview cell.....................................................297
Dayyear ............................................................ 68
list ..................................................................239
DB relationship................................................. 386
entity ..............................................................341
DB Web .............................................................. 29
file ..................................................................414
Datawarehouse.................................................102
involving ........................................................375
view ...............................................................424
December .......................................................... 65
Delete/Insert..................................................... 411
15 ..................................................................219
ALL ................................................................251
OnLine .............................................................19
Default BackColor ...............................................19
Default Drill .......................................................414
Default font .......................................................424
Default Menu icon .............................................356
Default PW ........................................................242
Default security PW ..........................................127
Define the ...........................................................40
Defined .....................................................119, 395
Join ................................................................119
Where ............................................................395
10 ................................................................... 79
all .................................................................... 80
all entity members .......................................... 80
Batch Reader procedure .............................. 118
Capsule screens........................................... 147
Data Reader protocol ................................... 115
entity ............................................................... 78
entity members ............................................... 79
InfoCube ......................................................... 97
members ........................................................ 69
procedures ................................................... 228
screen ........................................................... 155
Defining40, 59, 64, 65, 67, 68, 76, 82, 112, 122,
124, 126, 157, 158, 213, 289, 401, 407, 414
Box ................................................................213
Deliver ................................................................ 59
CMS ................................................................40
Dataflow ........................................................124
ETL ................................................................112
ETL transformation........................................112
Layout ...........................................................158
Department ........................................................ 93
Menu .............................................................157
multidimensional .............................................59
BoardClient................................................... 309
ODBO ............................................................289
OLE DB .........................................................401
relationship ......................................................82
Rule ...............................................................122
time .................................................................68
time entities relationships ................................68
User ...............................................................414
Where ............................................................407
years range .....................................................64
Delay .................................................................213
Delete .................................................................97
Delete button ............................... 78, 80, 118, 155
440
Index
Entities ............................................................99
DMZ ................................................................... 17
Applies ..........................................................275
DetailBy ............................................................336
column ...........................................................336
Does not............................................................. 76
Over-dimensioning ......................................... 76
Determine .........................................................411
WHERE .........................................................411
having ............................................................373
Developers ........................................................375
Developping ......................................................151
DexA .................................................................267
Dials000.jpg ......................................................173
Dials010.jpg ......................................................173
Dials020.jpg ......................................................173
Dials100.jpg ......................................................173
Dim strParEnc...................................................285
Dimensional ......................................................379
Dimensioning ......................................................15
criteria .............................................................15
Drag ................................................................... 95
Division1 ...........................................................246
441
Using .............................................................261
Dual-Engine ......................................................379
upgraded .......................................................379
DueDate ..............................................................93
DWR .................................................................311
442
Index
DynaSheet objects embeded ...........................211
CMS ................................................................. 8
Day ................................................................. 67
E3......................................................................112
E3&F3 ...............................................................112
Each Product ....................................................232
Edit ........................................... 108, 272, 311, 335
Chart .............................................................311
CSS file .........................................................272
use ................................................................108
Edit button ................................ 108, 111, 119, 250
Edit Desc ..........................................................216
Editable .............................................................335
EditQuery ..........................................................279
EIS ....................................................................149
Elavuates ..........................................................229
True ...............................................................229
Elevation ...........................................................188
Else ...................................................................229
Else checkbox...................................................229
Email .................................. 45, 227, 238, 239, 372
contain ...........................................................239
driving ............................................................372
Email Broadcast................................................372
EMF ..................................................................183
Enable8, 29, 40, 67, 116, 127, 143, 148, 237,
315, 322, 411, 414
Activate checkbox ...........................................40
Allow Access checkbox ...................................29
Auto ...............................................................148
Autosize ........................................................315
Broadcast checkbox ......................................237
443
Entity members25, 59, 61, 67, 70, 74, 76, 79, 80,
83, 104, 105, 107, 118, 121, 122, 125, 126,
133, 138, 139, 140, 141, 142, 170, 176, 189,
215, 219, 243, 247, 251, 260, 289, 297, 308,
318, 320, 327, 329, 333, 335, 336, 341, 347,
373, 379, 387, 411, 414, 422
Adding .......................................................... 140
deleting ........................................................... 79
Entity members according ........................... 67, 74
Entity members now ........................................ 333
Entity members that ......................................... 118
Entity member's UID .......................................... 79
Entity occurrances ............................................. 53
Entity part ................................................. 138, 414
hierarchy....................................................... 138
Entity ProfitAndLoss......................................... 170
Entity properties ................................................. 77
Modifying ........................................................ 77
Entity Region.................................................... 278
Entity_name ..................................................... 219
Entity1 ................................................................ 88
Entity2 ........................................................ 88, 278
Entity3 ................................................................ 88
EntityA .............................................................. 414
EntityB .............................................................. 414
EntityN ............................................................. 278
Entity's number .................................................. 59
members ........................................................ 59
Entity's UID ........................................................ 77
all use ............................................................. 77
Environment2, 5, 7, 19, 59, 60, 79, 90, 93, 97,
112, 115, 130, 138, 149, 181, 188, 204, 205,
206, 207, 213, 227, 241, 242, 265, 289, 297,
308, 310, 311, 315, 320, 329, 333, 335, 339,
340, 341, 349, 356, 362, 363, 366, 375, 379,
383, 387, 390, 414, 421
Environment allowing ....................................... 207
Setting .............................................................78
object .............................................................347
444
Index
Error ..........................................................271, 424
define ............................................................112
ETL configuration..............................................289
Expires ............................................................... 25
Defining .........................................................112
Europe ................................................................66
Exampe .............................................................163
Example ............................................................366
Examples For......................................................55
20 ..................................................................311
F.Y. .................................................................... 65
limitat ...............................................................88
F1 ..................................................................... 424
Excel 97 ............................................................204
Excel file .................. 147, 239, 261, 315, 354, 356
opening .........................................................354
Excel or other spreadsheet ...............................335
Exclude .............................. 59, 139, 275, 279, 336
Customer .........................................................59
MXC ......................................................275, 279
use ................................................................336
Exe7, 8, 39, 40, 45, 53, 116, 117, 148, 239, 241,
375
computer .......................................................241
Exe file ................................................................23
Exe installation....................................................40
Exe Path .............................................................40
Execquery .........................................................267
Execute ...................................... 55, 118, 158, 247
multidimensional .....................................55, 158
press .............................................................363
FileInputStream................................................ 285
Face001 ............................................................173
made .............................................................173
Face002 ............................................................173
Face003 ............................................................173
Facing .................................................................17
Internet ............................................................17
False .........................................................163, 229
evaluate .........................................................163
evaluates .......................................................229
False_value ......................................................163
Fast Commuting ...............................................136
disabling ........................................................136
Feature allows25, 289, 299, 308, 339, 352, 372,
379, 383
Firewall rule........................................................ 17
store ..............................................................308
picture ...........................................................173
Defining .......................................................... 65
Features2, 16, 25, 35, 36, 43, 51, 54, 59, 97,
125, 130, 133, 136, 140, 149, 167, 173,
186, 187, 196, 200, 201, 203, 224, 225,
244, 251, 261, 262, 289, 299, 308, 309,
322, 326, 327, 335, 336, 339, 340, 341,
349, 352, 354, 356, 363, 366, 372, 375,
383, 386, 407, 411, 414, 422, 424
102,
179,
241,
311,
344,
379,
446
Index
Flowchart properties .........................................211
Focus ................................................................142
entities ...........................................................142
Folder12, 16, 19, 25, 29, 36, 55, 62, 63, 117, 147,
148, 149, 151, 184, 209, 227, 244, 246, 250,
258, 264, 268, 271, 274, 275, 280, 281, 297,
302, 305, 311, 315, 333, 335, 356, 363, 372,
373, 375, 411, 421, 422, 424
Applies.......................................................... 275
Creating .........................................................184
Folder containing ........................................55, 275
database .......................................................275
Folder object ............ 184, 297, 375, 421, 422, 424
Folder object causing................................422, 424
Folder object provoking ....................................375
Folder/Analysis .................................................366
FolderAlias ........................................................148
Foldername/Queryname ...................................280
Folders correspond ...........................................244
Folders starting .................................................244
Follow .................................... 34, 49, 93, 204, 267
characteristics ...............................................204
Contemporary User .........................................34
Uninstall ..........................................................49
URL ...............................................................267
Windows ..........................................................93
Followign ...........................................................283
use ................................................................283
Following illustration .........................................414
Font butons .......................................................213
Font button ........................................................186
Font Size ...........................................................356
Font, 3D ............................................................180
Fontname ..........................................................366
Fonts by ............................................................275
applied ...........................................................275
FontSize ....................................................153, 366
Footer ...............................................................311
added ............................................................311
168,
213,
250,
289,
335,
375,
170,
219,
251,
297,
336,
379,
173,
222,
267,
311,
339,
387,
178,
225,
269,
315,
344,
390,
181,
232,
272,
322,
354,
395,
196,
237,
274,
324,
356,
414,
204,
238,
275,
329,
363,
421,
Ranking .........................................................165
database......................................................... 59
Refer .............................................................251
Select ............................................................289
GIF ... 163, 173, 183, 196, 207, 251, 275, 281, 366
Function estimates............................................168
Go
licensing ......................................................... 46
press ............................................................... 86
G
Gamma .................................................62, 63, 275
Gamma database .........................................62, 63
Gantt .................................................................188
Gauge feature ...................................................366
Gauge on DataView..........................................336
Gauges .................... 173, 251, 297, 336, 421, 422
provoking.......................................................336
use ................................................................173
Gauges option ......................... 196, 251, 336, 422
GB .....................................................................336
GDE158, 192, 193, 194, 195, 210, 224, 225, 322,
373
Using .............................................................194
GDE object ...................................... 192, 193, 195
General .................................... 395, 401, 404, 405
General Options................................................251
Generally sufficient .............................................15
448
Index
Greek ..................................................................36
Hh................................................................. 55, 57
Gregorian ............................................................66
Hhmmss ............................................................. 54
Grey ..................................................................352
Hi 188
Gross ................................................................121
Hide .. 153, 168, 208, 216, 246, 251, 275, 279, 307
HideTable......................................................... 279
GROUP BY .......................................................411
Group folders ....................................................246
Hierarchies4, 59, 60, 61, 74, 81, 82, 86, 87, 93,
97, 99, 100, 102, 105, 116, 138, 139, 142, 216,
235, 237, 260, 278, 305, 308, 327, 375, 383,
405, 411, 414
GROUP34 ...........................................................29
Create ............................................................. 59
Group9Head .....................................................272
Group9HeadName............................................272
GS .....................................................................121
Gt ......................................................................163
Guidelines .......... 15, 76, 88, 91, 93, 105, 149, 366
Hierarchy CustomerCityStateCountry.......... 86
H1 .....................................................................285
H3 .....................................................................285
Half................................................................45, 46
Creating ...........................................................45
HL....................................................................... 19
Sending ...........................................................46
Half-KEY .......................................................45, 46
Sending ...........................................................46
Creating ...........................................................45
Has a...................................................................88
Host ...................................................................... 8
Hostname......................................................... 302
Developer ......................................................373
LitePlus .........................................................289
How
Shape ............................................................363
Refer ............................................................... 40
Hdoc..................................................................267
HP .................................................................... 336
HeaderCol .........................................................272
HeaderName ....................................................272
HR .................................................................... 285
HeaderTotal ......................................................272
Hellen ................................................................356
Help...................................................................424
449
IMG.WebPicture............................................... 272
Implementing ............................................... 59, 92
Boolean .......................................................... 92
multidimensional............................................. 59
Import Chart ..................................................... 192
IMPORTANT .................................................... 271
Important notes .......................................... 50, 382
Importing .......................................................... 375
Day ............................................................... 375
Improved in ...................................................... 297
Improved performance ............... 25, 339, 354, 375
Improved Web.................................................. 339
IN...................................................................... 411
HTPP ..................................................................25
number ............................................................25
Optimizing .....................................................354
value ................................................................25
HTTP service log file...........................................57
HTTP Traffic .......................................................34
HTTPS ......................................... 25, 51, 242, 336
HWD .................................................................297
Hyperlink .......................... 251, 267, 269, 272, 281
Hyperlinks .........................................................261
2D ................................................................. 188
BOARD......................................................... 244
City ............................................................... 119
firewall .......................................................... 242
javascript file................................................. 281
Lite ................................................................ 308
LitePlus................................................. 311, 315
I
0 285
ICO................................................... 163, 173, 183
ID ..................................................... 285, 289, 411
Board .............................................................411
member .........................................................289
IF 163, 216, 229
nesting ...........................................................216
query .....................................................275, 279
Ignore Current Period .......................................414
enable ...........................................................414
Il 145
Images ............................. 163, 173, 251, 336, 356
IMG.Drill ............................................................272
IMG.Img01.Img09 .............................................272
IMG.MenuList ...................................................272
450
MS ................................................................ 204
OU ................................................................ 302
Rich Text Format .......................................... 206
Year ........................................................ 67, 143
Inconsistencies ................................................ 307
case .............................................................. 307
Incorrectly displayed ........................................ 297
Incrementing .................................................... 153
screen ........................................................... 153
Indentation ............................................... 264, 311
Index ................................................................ 356
InetOrgPerson.................................................. 305
InfoCube54, 60, 61, 64, 83, 93, 95, 96, 97, 112,
125, 158, 162, 166, 170, 188, 194, 230, 275,
289, 297, 308, 318, 324, 333, 335, 336, 375,
386, 392, 405, 407, 411, 414
Index
Clearing ...........................................................97
corresponding ...............................................411
Creating .....................................................59, 93
Deleting ...........................................................97
INPUT.MenuList............................................... 272
Moving .............................................................95
INPUT.Refresh................................................. 272
InfoCube Clear..................................................231
Copying ...........................................................95
Infocube Xtract..................................................289
InfoCubes2, 4, 7, 54, 55, 59, 65, 74, 76, 78, 80,
81, 87, 88, 89, 90, 91, 92, 93, 95, 97, 99, 100,
102, 104, 105, 106, 107, 108, 118, 121, 123,
124, 126, 127, 129, 131, 138, 157, 158, 162,
163, 166, 167, 168, 179, 192, 193, 196, 204,
209, 216, 219, 222, 224, 225, 227, 229, 231,
232, 237, 239, 241, 243, 247, 251, 262, 269,
279, 320, 322, 326, 339, 349, 354, 363, 366,
372, 373, 379, 383, 386, 395, 401, 405, 407,
411, 421, 422, 424
both types......................................................379
Create .............................................................59
creating .............................................................7
InfoCubes basic concepts ..................................87
InfoCubes considering ........................................76
InfoCubes DataReader .....................................333
InfoCubes form .....................................................4
multidimensional data .......................................4
InfoCubes having ............. 168, 232, 289, 333, 414
InfoCubes having City.......................................289
InfoCubes having Customer ...............................76
Infocubes launched...........................................297
InfoCubes returns ...............................................93
InfoCubes used.................................................354
InfoCubes'configuration ......................................76
Information ..........................................................66
BoardMaster ................................................... 17
facing .............................................................. 17
451
Interrupting ........................................................116
Intra .................................................................9, 13
WAN ..............................................................157
Introducing ..........................................................88
sparse structures.............................................88
Inventory ...........................................................121
Johnsmith........................................................... 46
Join .......... 119, 133, 136, 373, 395, 404, 407, 411
Customer .......................................................216
Date ...............................................................375
IOException ......................................................285
ISO ......................................................................66
ItemNr .................................................................78
Iteractive .............................................................59
Iterations ...........................................................229
ITunes ...............................................................332
Jan.00 ...............................................................275
Jan.04 .................................................................70
values ............................................................107
install .............................................................135
screen1......................................................... 181
use ................................................................283
452
Index
June 2004 .........................................................168
JVM ...................................................................135
KB .......................................................................25
KeepTop ...........................................................279
LAN ...... 7, 9, 11, 12, 13, 16, 17, 59, 150, 242, 363
Keeptop20 ........................................................279
KEY ................ 19, 44, 45, 46, 48, 49, 50, 283, 382
Launch7, 8, 16, 19, 23, 25, 36, 39, 40, 45, 48, 49,
52, 73, 86, 102, 108, 115, 116, 117, 131, 138,
142, 148, 149, 179, 180, 181, 182, 213, 227,
230, 235, 239, 241, 258, 267, 271, 279, 297,
307, 320, 332, 336, 339, 363, 366, 395
L02 ....................................................................121
L04 ....................................................................121
453
194,
209,
244,
311,
336,
375,
About .............................................................158
Defining .........................................................158
DataView .......................................................373
Layout containing..............................................335
Layout Nr ..........................................................216
Layouts defining................................................131
Go ................................................................... 46
Moving ............................................................ 48
Reinstalling ..................................................... 50
Entity .............................................................421
uninstall .......................................................... 49
Month ............................................................189
Uninstalling ..................................................... 49
Upgrading ....................................................... 49
configure .......................................................302
configuring.....................................................299
value ..............................................................299
Licenses overview.............................................. 43
LDAPAppend ....................................................336
Limitat ................................................................ 88
Ldapbrowser .....................................................302
exceeded ........................................................ 88
more ................................................................54
454
Index
reached ...........................................................88
Locally .................................................................. 9
LocalServers Nr ................................................. 40
Linked databases..............................................387
Location ............................................................. 90
HTML ............................................................356
ScreenName .................................................363
List
Log file ....... 53, 54, 55, 57, 61, 116, 127, 235, 375
Logo_P01......................................................... 366
Lite 45, 49, 289, 297, 307, 308, 311, 315, 336, 382
Loss ................................................................... 92
including ........................................................308
upgraded .........................................................49
having ............................................................289
face001......................................................... 173
Main25, 29, 62, 63, 117, 148, 271, 275, 297, 335,
372, 373, 392, 395
Lo ......................................................................188
Load data ............................................................59
Loading .......................................................76, 107
Customer .........................................................76
data ...............................................................107
Loc19, 59, 147, 150, 234, 237, 264, 265, 311,
315, 335
Connecting ......................................................40
MaxItemNumbers............................................... 91
Manual ..... 1, 23, 52, 102, 302, 339, 362, 404, 407
Mapping ... 158, 176, 196, 210, 224, 225, 322, 373
Creating .........................................................196
Using .............................................................196
March ................................................................107
January .........................................................142
Mario .................................................................283
corresponding............................................... 289
creates.......................................................... 289
ME ...................................................................... 19
Master9, 12, 23, 40, 52, 55, 76, 104, 105, 149,
176, 192, 196, 200, 203, 239, 251, 264, 269,
297, 302, 311, 336, 372, 373
456
131,
196,
261,
339,
147,
198,
262,
356,
152,
199,
265,
363,
Index
Menu Current ....................................................311
MenuDat ...........................................................356
Menulist Title.....................................................251
Message ...........................................................216
Modifying ............................................................ 77
Monday
Meta ..................................................................150
starting............................................................ 66
Monitor2, 23, 29, 34, 35, 36, 48, 52, 55, 74, 354,
379, 411, 424
Month4, 36, 67, 68, 70, 87, 93, 105, 106, 107,
108, 112, 116, 139, 143, 144, 170, 189, 232,
278, 326, 366, 375, 392, 395, 405, 414
use ................................................................274
METHOD ..........................................................285
Season ........................................................... 70
Microphone Locking..........................................136
Month entity ....... 68, 107, 251, 275, 379, 390, 414
configure .......................................................300
More2, 4, 7, 9, 15, 25, 29, 36, 43, 54, 64, 69, 70,
74, 76, 81, 83, 86, 87, 88, 90, 91, 92, 93, 96,
102, 108, 119, 127, 129, 131, 133, 136, 140,
142, 147, 149, 155, 158, 163, 170, 173, 176,
178, 179, 184, 188, 199, 208, 215, 224, 228,
231, 232, 238, 239, 241,242, 243, 246, 247,
251, 259, 271, 275, 278, 279, 282, 289, 297,
302, 307, 326, 333, 335, 336, 339, 341, 354,
363, 366, 372, 373, 375, 379, 382, 383, 386,
395, 405, 407, 411, 414, 421, 422, 424
Mid ....................................................................289
MinValue1 .........................................................275
MinValue2 .........................................................275
Missing ..................................................70, 83, 235
childparent...............................................70, 83
Mktg ..................................................................121
457
Multiple sessions................................................ 15
MouseOver .......................................................356
Running .......................................................... 15
action .............................................................228
InfoCube ..........................................................95
license .............................................................48
Mozilla ...............................................................336
create ............................................................. 92
Mr ......................................................................302
account ..........................................................302
feed ................................................................ 92
Index
Mysite ...............................................................283
N__N1 .................................................................54
string ...............................................................54
Changing .........................................................63
New1, 16, 25, 29, 39, 40, 46, 48, 49, 53, 55, 59,
62, 63, 66, 69, 76, 79, 90, 95, 96, 97, 99, 100,
104, 114, 116, 122, 127, 130, 140, 147, 149,
151, 154, 158, 162, 167, 181, 188, 190, 196,
205, 215, 216, 222, 227, 228, 242, 244, 250,
268, 275, 285, 289, 297,299, 300, 307, 308,
309, 310, 311, 315, 320, 324, 327, 329, 332,
335, 339, 340, 341, 347, 349, 352, 354, 356,
362, 363, 366, 373, 375, 379, 382, 392, 395,
401, 405, 411, 414, 421, 422, 424
computer ........................................................ 48
Creating .......................................................... 62
therfore ........................................................... 55
Named StandAlone...........................................382
Named TOTAL..................................................262
Creating .......................................................... 95
Num_chars....................................................... 289
Number .............. 15, 16, 19, 25, 34, 206, 283, 354
BoardClient..................................................... 16
BoardServer ................................................... 15
HTTP .............................................................. 25
TCP ................................................................ 19
Web ................................................................ 34
Adding .............................................................95
Next...........................................................366, 414
NightlyUpdate@BoardMaster ...........................117
Nn .................................................................65, 66
Nnn ...................................................................275
No
clicks .............................................................414
No ALL ..............................................................143
enabling .........................................................143
Layout........................................................... 333
No Hwnd ...........................................................336
ObjectClass...................................................... 305
enable ...........................................................116
Normalize function ............................. 86, 102, 235
Normalize icon ....................................................86
North America ...................................................411
Not Available.....................................................421
Not Responding ................................................354
129,
150,
183,
201,
215,
272,
319,
347,
421,
NoTable ............................................................279
removing....................................................... 156
NoTotals ...........................................................336
460
Index
Occurring ..................................................335, 336
press ......... 69, 78, 119, 311, 341, 363, 387, 401
DataView .......................................................336
Supertable .....................................................335
ODBC17, 102, 108, 112, 115, 119, 289, 373, 375,
379, 395, 401, 404, 405, 411
create ............................................................395
displayed .......................................................289
entity ..............................................................373
refer ...............................................................112
views .............................................................375
Setting ...........................................................112
On a ................................................................. 224
Creating .........................................................108
ODBC Data Reader protocol generates ...108, 395
ODBC Data Source ..........................................401
ODBC Data Source Administrator window .......401
ODBC Data Source Name ........................395, 405
ODBC DataReader .......................... 289, 373, 375
create ............................................................289
ODBC DataReader options ..............................404
ODBC driver used............................ 108, 395, 407
ODBO ...............................................................289
connect ..........................................................289
define ............................................................289
measures ......................................................289
ODBO data .......................................................289
ODBO Datareader ............................................289
Of the ........................................................163, 302
Office.................................................................352
Office2007Aqua ................................................332
Offset ................................................................356
OK39, 40, 45, 62, 69, 78, 88, 95, 108, 115, 119,
126, 158, 188, 189, 193, 194, 196, 199, 202,
285, 297, 311, 341, 349, 363, 387, 401
clicking ................................... 45, 108, 119, 297
Operating system................................................15
simulated by ....................................................15
Opt ....................................................................271
Options8, 11, 12, 16, 19, 23, 25, 29, 35, 36, 40,
49, 50, 52, 65, 66, 67, 74, 77, 86, 92, 95, 102,
104, 105, 107, 112, 126, 127, 134, 135, 136,
138, 143, 147, 153, 157, 158, 162, 163, 166,
167, 168, 170, 173, 176, 178, 182, 184, 185,
186, 188, 189, 190, 192, 193, 195, 196, 198,
199, 200, 201, 202, 203, 204, 205, 206, 208,
211, 213, 216, 219, 222, 224, 229, 232, 234,
239, 243, 246, 247, 250, 251, 259, 261, 262,
264, 265, 268, 269, 271, 272, 275, 278, 279,
280, 281, 289, 297, 300, 307, 310, 311, 315,
320, 324, 326, 329, 333, 335, 336, 339, 340,
341, 347, 352, 354, 356, 362, 363, 366, 372,
373, 375, 392, 395, 401, 404, 407, 411, 414,
421, 422, 424
Other2, 7, 9, 11, 12, 13, 16, 17, 19, 23, 25, 32, 34,
36, 43, 46, 48, 54, 61, 67, 74, 76, 77, 87, 88,
90, 91, 92, 93, 102, 104, 107, 112, 116, 119,
121, 122, 123, 129, 130, 133, 136, 139, 145,
147, 148, 149, 150, 152, 158, 162, 163, 166,
167, 170, 176, 180, 183, 184, 186, 192, 196,
200, 203, 204, 209, 215, 216, 224, 231, 237,
241, 242, 243, 250, 251, 261, 267, 269, 271,
272, 282, 289, 297, 299, 300, 305, 308, 309,
310, 311, 315, 320, 326, 327, 333, 335, 336,
339, 340, 341, 354, 362, 366, 373, 375, 379,
382, 383, 390, 401, 404, 411, 414
Option replaces.................................................104
462
Index
Other Business Intelligence ..............................102
P&L ...................................................................121
P.MainTitle ........................................................272
P.MenuList ........................................................272
P.PageBy ..........................................................272
P.SubTitle .........................................................272
P.TextNote ........................................................272
P> .....................................................................285
P1........................................................................88
Page25, 29,
200, 202,
244, 246,
272, 274,
308, 311,
375
199,
243,
269,
285,
366,
Changing .......................................................259
Java ...............................................................135
Peer ................................................................... 19
Pentium .............................................................. 22
F4 key........................................................... 130
183,
251,
332,
383,
196,
275,
336,
392,
Index
Processing of ..................................................... 15
Processor 8 ........................................................ 15
Product4, 76, 87, 88, 89, 92, 93, 105, 106, 107,
108, 116, 118, 119, 144, 215, 216, 224, 232,
269, 278, 326, 339, 354, 366, 375, 383, 392,
395, 405, 414
press .............................................................264
Priorly ................................................................401
set..................................................................131
Product entities ...... 76, 87, 93, 215, 379, 387, 414
Procedure described.........................................119
DataReader ...................................................421
Procedure stops................................................238
Procedures2, 9, 36, 39, 40, 48, 49, 50, 53, 61, 74,
77, 79, 80, 86, 87, 91, 92, 93, 102, 107, 115,
116, 117, 118, 119, 124, 126, 127, 129, 131,
133, 138, 142, 147, 148, 150, 151, 153, 155,
180, 181, 209, 213, 216, 224, 227, 228, 229,
230, 235, 238, 239, 241, 242, 251, 269, 271,
272, 280, 289, 297, 307, 308, 309, 318, 320,
326, 329, 332, 333, 335, 336, 339, 340, 362,
363, 366, 372, 373, 375, 379, 382, 387, 390,
407, 414, 421, 422, 424
Profit ................................................................... 92
ProfitAndLoss................................................... 170
Creating .........................................................227
Project ................................................................ 93
deleting ..........................................................228
Promotion........................................................... 67
Printout .............................................................237
Opening .........................................................227
Procedures having ............................................422
DataReader ...................................................422
Procedures list ..................................................272
Table containing ............................................272
Procedures updating.........................................126
Product Type...................................................... 87
Production .......................................................... 29
Products Sold InfoCubes ................................. 232
Cost .............................................................. 232
Profile ............................................................... 289
Profile table ...................................................... 289
Prompting......................................................... 414
Yes ............................................................... 414
Properties48, 50, 59, 74, 77, 97, 99, 138, 142,
148, 152, 153, 158, 180, 184, 190, 210, 211,
213, 215, 272, 275, 279, 282, 283, 289, 307,
311, 324, 332, 352, 356, 363, 366, 422
Property Auto ................................................... 148
Proportional in .................................................... 12
465
Capsule .........................................................151
LAN ...............................................................242
If 275, 279
Protocols three..................................................261
Provides accuracy..................................................91
BoardClient ...................................................307
Gauges ..........................................................336
Pw list ...............................................................213
Pwd ...................................................................285
Pwd.charAt .......................................................285
Py ..............................................................269, 275
Q
Q.nn yy ...............................................................65
Q1 .......................................................................65
2004 ................................................................65
Q2 .......................................................................65
2004 ................................................................65
466
Index
DataView .......................................................211
Ran .....................................................................40
BoardWebKitSetup..........................................40
Ranking .............................................................165
Refer25, 40, 44, 65, 70, 73, 83, 86, 112, 129, 148,
167, 170, 179, 185, 199, 237, 247, 251
function ..........................................................165
RBD InfoCubes .................................................375
RDB289, 333, 372, 373, 375, 379, 395, 401, 405,
407, 411
Creating .........................................................405
table ..............................................................407
RDB Infocube setup options .............................411
RDB-InfoCube ODBC .......................................375
RDBMS .................... 379, 395, 401, 404, 405, 411
let...................................................................411
RDN ..........................................................302, 305
concatenating ................................................305
RDN of the ........................................................302
Reached .............................................................88
limitat ...............................................................88
Read ................................................ 105, 126, 136
Customer .......................................................105
dB ..................................................................136
Read & Write ....................................................126
Read Only .........................................................126
Read/write ...................................................61, 125
Reader ................................................................90
Reader's Replace function..................................93
Reading long screen .........................................335
ReadOnly ..........................................................126
REC ..........................................................112, 115
Recalc ...............................................................251
Receive12, 19, 25, 43, 44, 46, 48, 49, 50, 51, 133,
136, 239, 267, 299
Reconfigured ......................................................17
Record Update Method.....................................411
Rectangle Ellipse ..............................................213
Recycle .............................................................147
Red Alert Value.................................................173
Red20 green20 block Square ...........................366
Red80 green120 block dec1 .............................275
DS ................................................................ 179
Fiscal Yearquarters ........................................ 65
functions ....................................................... 251
How ................................................................ 40
Multi .............................................................. 247
ODBC ........................................................... 112
SSL ................................................................. 25
SSO ................................................................ 25
The ....................................................... 185, 199
Refer To ........................................................... 229
clicking .......................................................... 229
References tab................................. 167, 170, 251
References tab holds ....................................... 251
Total ............................................................. 251
ReferTo .................................................... 336, 424
ReferTo function .............................................. 424
Refresh ............................ 216, 259, 260, 297, 363
clicking .......................................................... 363
press ..................................................... 259, 260
Refresh button ................................................. 167
Refresh file List ................................ 106, 112, 392
Press ............................................ 106, 112, 392
Refresh Tree ............................................ 250, 267
call ................................................................ 267
press ............................................................. 250
RefreshTree ..................................................... 267
RefTo ............................................................... 366
Regards ............................................................. 29
confidentiality.................................................. 29
Region entity ...................................................... 76
Regional ........................................................... 163
467
Reinstalling .........................................................50
license .............................................................50
relationship ..................................................... 83
REJ ...................................................................115
Supertable .....................................................366
WEB ................................................................36
Relational ..........................................................407
Defining ...........................................................82
Removing ........................................................83
Relationship CustomerCountry.........................86
Response ........................................................... 25
BoardClient................................................... 349
Relatioships ......................................................126
Boardserver .................................................... 36
use ................................................................232
rightmost....................................................... 289
multidimensional........................................... 118
Representations ......................................... 66, 129
Index
Rightmost column .............................................106
Ro/rw...................................................................54
Robert ...............................................................356
Rom ..................................................................375
BoardServer ................................................... 15
Running the...................................................... 127
Runs the actual ................................................ 230
RunTime .......................................................... 421
Royale ...............................................................332
Royalty ..............................................................232
Royalty Value....................................................232
Russian .............................................................. 36
Rt ......................................................................163
Rule17, 61, 66, 74, 81, 87, 102, 112, 121, 122,
123, 124, 170, 211, 216, 232, 264, 275, 289,
308, 322, 327, 333, 411, 421
Defining .........................................................122
Using .....................................................123, 124
Rule calculates .................................................327
members .......................................................327
Rules basic concepts ........................................121
Run7, 8, 15, 17, 19, 22, 23, 25, 29, 34, 36, 39, 40,
43, 44, 48, 50, 51, 52, 53, 61, 76, 80, 86, 90,
102, 105, 106, 108, 115, 116, 117, 119, 126,
127, 129, 131, 133, 135, 136, 146, 148, 158,
196, 199, 202, 208, 209, 213, 216, 224, 227,
229, 230, 231, 232, 235, 241, 242, 244, 247,
259, 260, 265, 271, 272, 274, 280, 289, 299,
300, 302, 305, 307, 308, 309, 311, 318, 320,
326, 332, 333, 335, 336, 340, 341, 344, 356,
362, 363, 366, 372, 373, 375, 382, 392, 401,
411, 414, 421, 422, 424
BoardClient ...................................................133
SAMAccountName........................................... 302
Scan ..............................................................102
Same structure................................................... 95
SandAlone ........................................................189
SAP ...................................................................372
DataReader ...................................................372
Sate...................................................................138
California .......................................................138
clicks .............................................................216
press .............................................................250
Save As ............................................................250
Save button.............................. 167, 194, 262, 356
Save icon ......................................... 133, 311, 315
Save screen icon ..............................................155
Save Setup button ..............................................86
Save Values......................................................222
press .............................................................222
Saved for ..........................................................145
Saving151, 154, 155, 227, 250, 261, 267, 315,
335, 405
Board Web query ..........................................250
call .................................................................267
MS .................................................................315
press .............................................................151
Query ............................................................261
screen ...........................................................155
use ................................................................154
Scan ......................................... 70, 73, 83, 86, 102
run .................................................................102
SceenList ..........................................................422
Scheduling ........................................................148
Capsule procedures ......................................148
Screen2, 19, 22, 129, 130, 131, 133, 134,
138, 142, 143, 144, 145, 147, 148, 149,
151, 152, 153, 154, 155, 156, 157, 158,
170, 176, 179, 180, 181, 182, 183, 184,
188, 189, 193, 194, 196, 199, 200, 202,
204, 206, 207, 208, 209, 210, 211,213,
227, 228, 229, 230, 234, 238, 239, 264,
307, 308, 318, 320, 324, 329, 332, 333,
336, 339, 341, 344, 352, 363, 366, 372,
375, 379, 383, 386, 387, 390, 404, 414,
424
470
135,
150,
168,
185,
203,
216,
297,
335,
373,
422,
Index
Month ..............................................................70
Sec ......................................................................19
Security5, 8, 9, 19, 23, 28, 29, 33, 48, 51, 52, 54,
61, 79, 125, 126, 127, 158, 167, 242, 246, 289,
297, 299, 300, 302, 308, 320, 356, 372, 373,
414
Security basic concepts ....................................125
Security privileges...............................................28
Security profile29, 54, 61, 79, 125, 126, 127, 242,
289, 373
Assigning.......................................................127
Defining .........................................................126
database .........................................................29
Sel .....................................................................275
Select19, 25, 29, 32, 36, 39, 40, 45, 46, 49, 50,
52, 55, 59, 63, 65, 66, 67, 68, 70, 71, 72, 73,
74, 77, 82, 83, 85, 86, 90, 92, 93, 95, 97, 99,
100, 102, 106, 107, 108, 111, 112, 115, 116,
117, 118, 119, 122, 123, 124, 126, 131, 133,
136, 138, 139, 140, 141, 142, 143, 144, 145,
146, 149, 151, 152, 154, 158, 162, 163, 165,
166, 168, 170, 176, 179, 180, 181, 183, 184,
185, 186, 188, 189, 190, 192, 193, 194, 195,
196, 198, 199, 200, 201, 202, 203, 204, 205,
206, 208, 210, 211, 213, 216, 219, 222, 228,
229, 230, 232, 234, 235, 237, 238, 244, 247,
250, 251, 259, 260, 264, 265, 267, 269, 271,
272, 275, 281, 289, 300, 307, 308, 310, 311,
315, 320, 322, 324, 326, 329, 332, 333, 335,
336, 339, 341, 344, 347, 349, 352, 354, 356,
362, 363, 372, 375, 382, 386, 387, 390, 392,
395, 401, 405, 407, 411, 414, 421, 424
471
Server holds......................................................305
subtree ..........................................................305
Server making...................................................282
SERVER PLUS.................................................382
time ................................................................. 67
Server_Name......................................................19
Server01 ...........................................................302
Servers Nr ...........................................................25
Set4, 6, 15, 16, 19, 23, 25, 28, 29, 32, 35, 36, 40,
55, 59, 62, 64, 67, 68, 73, 74, 76, 77, 78, 86,
88, 90, 93, 99, 102, 106, 107, 108, 112, 116,
121, 123, 125, 126, 127, 131, 133, 136, 139,
140, 142, 143, 144, 149, 151, 153, 158, 162,
163, 165, 166, 167, 168, 170, 173, 176, 178,
180, 182, 184, 185, 186, 188, 189, 190, 192,
193, 194, 195, 196, 198, 199, 200, 201, 202,
203, 204, 210, 211, 213, 216, 219, 227, 229,
239, 243, 247, 251, 259, 265, 268, 269, 272,
275, 279, 283, 285, 289, 297, 299, 300, 302,
305, 308, 322, 336, 339, 340, 344, 347, 349,
352, 354, 356, 362, 363, 366, 372, 379, 386,
Settings .............................................................. 93
472
Index
Shape ...............................................................363
having ............................................................363
Share ..................................................................15
RAM ................................................................15
Formatting .....................................................206
Sn ..................................................................... 305
Sheet1 ..............................................................354
Shift .....................................................................64
2002.2006 .......................................................64
Short ...................................................................93
Show5, 23, 29, 34, 40, 51, 69, 71, 72, 76, 78, 81,
85, 86, 89, 90, 93, 96, 97, 102, 106, 115, 122,
138, 142, 144, 151, 158, 162, 166, 170, 176,
178, 190, 211, 213, 216, 222, 238, 246, 251,
260, 261, 269, 271, 275, 279, 281, 285, 289,
305, 322, 329, 335, 336, 352, 363, 366, 375,
382, 383, 392, 395, 401, 405, 407, 414, 421
list ................................................................... 89
Introducing...................................................... 88
ShowAll .............................................................279
ShowLines ........................................................153
Silver .................................................................352
Simulated by .......................................................15
Store4, 11, 13, 16, 19, 29, 39, 40, 44, 53, 59, 62,
63, 74, 77, 79, 87, 88, 92, 93, 123, 124, 129,
163, 207, 227, 231, 241, 242, 264, 289, 299,
308, 320, 333, 362, 363, 379, 383, 405, 411,
414
Creating .........................................................194
Creating .........................................................189
Stp ...................................................................... 36
CMS ..........................................................40, 52
Monday ...........................................................66
474
Index
pCon ..............................................................285
relating.......................................................... 366
pRes ..............................................................285
uid..................................................................285
User ...............................................................302
StrParEnc .........................................................285
Support .............................................................. 46
StrPwd ..............................................................285
Structre .............................................................414
SVR .................................................................... 90
Style definitions.................................................272
Style Sheets......................................................272
Cascading .....................................................272
levels .............................................................333
Submitting ...........................................................35
WebQueries ....................................................35
SubTitle .............................................................269
Subtree .............................................................305
server holds...................................................305
Succesful ..........................................................282
enable ...........................................................411
SQL statement adding ..................................411
Summarisation ..................................................424
Summarized ..................................................72, 85
Summarized mode........................................72, 85
Summary algorithm.......................... 166, 322, 336
Summer Promotion Products ...................379, 387
Sun Java 1.3 .....................................................285
Super table .......................................................366
Supertable ............................... 335, 336, 363, 366
occurring .......................................................335
112,
216,
311,
372,
116,
235,
333,
373,
118,
241,
335,
375,
TD.TotalData.................................................... 272
TD.TotalName.................................................. 272
TABLE.Data ......................................................272
TABLE.Folder ...................................................274
TABLE.Item ......................................................274
TABLE.MenuList ...............................................272
Terminal ............................................................. 19
TABLE.Procedure .............................................272
TableHide .........................................................279
TabsNr ..............................................................184
Tag ....................................................................251
HTML ............................................................251
number ............................................................19
TD.Group1Head ...............................................272
TD.Group1HeadName ......................................272
TD.GroupTotalData ..........................................272
TD.GroupTotalName ........................................272
TD.GroupTotalTotal ..........................................272
TD.HeaderCol ...................................................272
Th ....................................................................... 49
TD.HeaderName...............................................272
The
TD.HeaderTotal ................................................272
TD.Hyperlink .....................................................272
TD.MenuList .....................................................272
TD.ProcedureError ...........................................272
TD.ProcedureExec ...........................................272
TD.ProcedureInput ...........................................272
TD.ProcedureLogo ...........................................272
TD.ProcedureName ..........................................272
TD.RowData .....................................................272
TD.RowDataGreen ...........................................272
TD.RowDataGreenBlock ..................................272
TD.RowDataRed...............................................272
TD.RowDataRedBlock ......................................272
TD.RowName ...................................................272
476
Index
Defining .......................................................... 68
Setting ............................................................ 67
Setting ............................................................ 67
Defining .......................................................... 68
Therfore ........................................................55, 57
time ................................................................. 55
Time range ... 59, 61, 62, 63, 64, 67, 168, 297, 375
Navigating .....................................................258
Through CityCountry.........................................86
Through CityState .............................................82
Through Dataflow Procedures ..........................407
Through Get List button ....................................289
Through ODBC .................................................116
Through protocol.............................. 102, 118, 119
Through screens .......................................131, 133
Navigating .....................................................131
Through screens working .................................133
Through StateCountry ......................................86
Thte Local .........................................................227
Thursday
concluding .......................................................66
Time2, 4, 7, 8, 9, 12, 15, 16, 19, 23, 25, 35, 39,
40, 51, 54, 55, 57, 59, 61, 62, 63, 64, 66, 67,
68, 70, 73, 76, 79, 86, 88, 91, 93, 97, 102, 103,
104, 106, 108, 112, 133, 135, 138, 142, 150,
158, 163, 167, 168, 224, 229, 231, 232, 251,
10 ..................................................................262
Uk ..................................................................... 282
TR.GroupHeadVA.............................................272
TR.GroupTotalVA .............................................272
TR.HeaderVA ...................................................272
TR.ProcedureVA...............................................272
TR.RowVA ........................................................272
TR.TotalVA .......................................................272
Transaction files................................................105
Transformations ................................................112
DataView .......................................................336
Year .................................................................67
Trend.................................................................275
BOARD........................................................... 49
Applies ..........................................................275
complete ......................................................... 50
follow .............................................................. 49
Trigged ..............................................................271
license ............................................................ 49
Trigger ..............................................................332
Triggered by......................................................324
True...........................................................163, 229
elavuates .......................................................229
True_value ........................................................163
Uninstalling ........................................................ 49
license ............................................................ 49
Trustlib ..............................................................285
Try .....................................................................336
Ununsed ............................................................. 54
Index
Lite Plus ..........................................................49
User .................................................................49
Uses23, 33, 92, 95, 108, 115, 154, 173, 176, 182,
213, 232, 251, 274, 283, 300, 308, 315, 336,
366, 414
create ..............................................................32
find ..................................................................33
Search ............................................................ 33
User Group .... 28, 29, 32, 149, 246, 299, 339, 356
Toolbox......................................................... 366
create ..............................................................29
User ID ................................................................45
User_ID .............................................................411
Using1, 7, 15, 17, 23, 29, 39, 40, 43, 46, 50, 51,
53, 64, 65, 66, 67, 73, 74, 79, 86, 87, 89, 91,
93, 96, 102, 108, 112, 116, 123, 124, 126, 131,
133, 135, 136, 142, 144, 145, 146, 147, 148,
153, 155, 163, 170, 173, 178, 183, 184, 186,
190, 192, 194, 196, 198, 200, 201, 202, 203,
204, 211, 213, 215, 216, 222, 224, 228, 237,
238, 239, 241, 247, 251, 261, 262, 265, 268,
275, 278, 279, 282, 289, 297, 299, 300, 302,
309, 320, 322, 324, 329, 333, 335, 336, 339,
340, 341, 344, 352, 356, 362, 363, 366, 373,
375, 379, 382, 392, 395, 404, 407, 411, 414,
421, 422, 424
UserGroup ........................................................246
Userl....................................................................40
Bimonth .......................................................... 65
contains .........................................................282
encrypt ..........................................................283
479
STO ...............................................................222
Using Quarters....................................................65
Using VBScript..................................................241
Using Weeks.......................................................66
Versions1, 54, 61, 65, 66, 76, 78, 80, 88, 89, 90,
91, 92, 93, 95, 96, 97, 100, 105, 147, 179, 231,
289, 297, 307, 308, 309, 327, 332, 333, 335,
336, 339, 340, 347, 354, 362, 372, 373, 375,
379, 382, 405, 414, 421, 422, 424
Validation ..........................................................216
clicking ..........................................................216
Validation rule .......................... 102, 112, 215, 216
Value .................................. 25, 107, 136, 168, 299
500 ................................................................136
HTTP ...............................................................25
January .........................................................107
LDAP .............................................................299
Yearly Moving Total ......................................168
Value list ...........................................................219
Value list entity..................................................219
Value1 ...............................................................219
Value2 ...............................................................219
Values based ....................................................224
Var ............................................................275, 285
Variance ............................................................269
VBScript ............................................................285
Verify7, 44, 46, 48, 50, 61, 70, 80, 88, 96, 127,
136, 282, 289, 299, 366, 375, 386, 422
View function...................................................... 79
Version 5 ...........................................................333
480
Index
creating .........................................................207
Creating .........................................................208
Web Query25, 55, 74, 77, 79, 87, 244, 247, 251,
264, 267, 268, 289, 340, 375, 421
added ............................................................411
determine ......................................................411
Www.myBoardServer.com ................................ 19
Where IN ...........................................................411
WWYYYY......................................................... 103
Width .................................................................307
following ..........................................................93
resize .............................................................155
Windows 98 ........................................................19
XP .................................................................... 362
XP Home Edition................................................ 19
Windows NT .................................................19, 22
use ..................................................................23
XY .................................................................... 188
Windows Start...............................................39, 40
0 285
Windows/System32 ..........................................283
Windows's NET...................................................53
Year64, 67, 68, 70, 87, 93, 112, 143, 170, 232,
271, 329, 379, 390
Index
Year, Product ....................................................232
W.nn ............................................................... 66
Applies ..........................................................275
Yearly Cumulated Value function .......................65
Yearly Moving ...................................................251
Yearly Moving Average.............................168, 275
Applies ..........................................................275
Yearly Moving Total ..................................168, 251
function returns .............................................168
value ......................................................168, 275
Applies .......................................................275
Qnn ................................................................. 65
Defining ...........................................................64
YearToDate ......................................................267
Yes ............................................................333, 414
create ............................................................414
enable ...........................................................414
prompting ......................................................414
Yma...................................................................275
Ymt....................................................................275
You are ...............................................................76
YYYYY ........................................................... 65
YYYYB ............................................................. 103
YYYYBB ........................................................... 103
YYYYMM ............................. 54, 55, 103, 112, 275
Yyyymmdd ........................................... 54, 55, 103
YYYYQ ............................................................. 103
YYYYQQ .......................................................... 103
YYYYWW ......................................................... 103
YYYYY ............................................................... 65
yyyy ................................................................ 65
Z
ZeroOn ............................................................. 275
ZeroOn option .................................................. 264
ZIP Code entity .................................................. 74
Zip File Read Error........................................... 424
483