Board 10.1.0 Release Notes

What's New in Board 10.1.0

Board Web new features


Version 10.1.0, Board web client includes new exclusive features, other than the normal capsule navigation:



Please check Chapter 11 for further information.


Upgrade instructions

After upgrading the Board Server it is required to upgrade all Board Client and Office Add-in installations to the same version 10.1.0.

Capsules created with prior versions of Board (version 9 or 8) can be opened without requiring any editing with version 10. A Capsule that created or saved using version 10.1 is automatically upgraded to a new format and can't be re-opened with an older version such as version 10.0 or older.


Upgrading Board Web from version 10.0 to 10.1

All custom configuration settings of Board Web 10.0 which were stored in the following two files

c:\Program Files (x86)\Board\BoardWeb Api Server\BoardWebApiEngine.config

c:\Program Files (x86)\Board\BoardWeb Api Server\Web.config


are now in multiple files, all stored in the following subfolder

c:\Program Files (x86)\Board\BoardWeb Api ServerApp_Data\config


If you have an installation of Board Web server 10.0 and you defined some custom configurations in the Web.config or BoardWebApiEngine.config files, you must re-type your configurations in the new files of version 10.1 located in the folder specified above.  


Time Entities Enhancements

The time entities management has been improved with several new features and capabilities.







Note that this new feature make it very simple to compare data of a certain day with the same day of the week of the previous year, i.e. compare a Wednesday with the corresponding Wednesday of the same week of the previous year.



In order to enable this function, the custom time entity must contain the year as part of the code of the members.

For example, the members of the custom time entity could be the following:

2016/01, 2016/02, ... 2016/13, 2017/01, 2017/02 ... 2017/13


To activate the custom calendar function, its necessary to specify the part of the code that contains the year through the definition of a Mask. This mask drives the code convention for that entity: use the "Y" for each digit that represents the year and a "-" (hyphen) for each other part of the code. The characters specifying the year must be numerical, the other part of the members code can be alphanumeric and can include separators and spaces.


Examples of possible masks


The first four characters (digits) represent the year, followed by three other characters that specify the period.


The four characters specify the period, the year is specified by the following two positions.


The year is specifies by the digits found in position 2 to 4 of the code.



For example, for a custom entity, having 4 digits for the year and 2 for the period number, the mask will look like this YYYY--

The entity members codes could be the following





If the codes contain extra characters such as P.2017/01 then the mask should be --YYYY---


To define the Mask for a custom time entity




Once the mask is created the entity will be shown in the calendar drop down list of the time functions:





Security Profile Enhancements

It is now possible to define a security selection at user account level. This new security Select is additive to the security select define in the Security Profile. This new feature reduces the need to create different Security Profiles for users that differ only in the Selection range.

To add a security Select on a user account, click the new Select icon found on the Users panel of the User's account management window, as shown in the following picture.




ANSI File Encoding

It is now possible to read text files containing double-byte characters (for example japanese or chinese) which are in ANSI encoding format.


In previous version, double-byte languages cloud only be loaded  from files in UTF-8 encoding. Text files with ANSI encoded files can be loaded through a DataReader or Data FastTrack. Note that, unlike UTF-8 and other encodings, ANSI encoding does not refer a specific code page, it is a generic definition that uses the default code page of the operating system. For this reason, reading a file with double-byte characters on different computers could lead to different results depending on the default code page. To know what is the default code page of your system, open the command prompt and type the command chcp.

Log Encryption

It is now possible to protect the Board Log files through encryption.


To activate encryption of the log files, open the Board Server Configuration program, go in the Security tab and enable the check-box and type your encryption pass-phrase as shown in the picture below.




The pass-phrase is also necessary to de-crypt the files, make sure you keep a safe copy of your pass-phrase accessible only to authorized personnel.

Once the encryption is enabled, the prefix "encrypted" is added to the file name: for example the log file Login.log becomes encryptedLogin.log

The encryption pass-phrase is saved locally on the server using DPAPI encryption.


To de-crypt the log files you may use the utility program BoardLogDecrypter.exe which is found in the folder

c:\Program Files\Board\Board Server\Tools\BoardLogDecrypter


The syntax of the command to de-crypt a log file is the following:


BoardLogDecrypter EncFile="[Encrypted File]" DestFile="[Destnation File]" Password="[Password]"


EncFile: the encrypted log that you want to decrypt

DestFile: The destination file that will contain the Decrypted Log

Password: the password you set up in the step before.

Note that the de-crypter generates a new file in clear text without altering the original encrypted file.


Transporter enhancements

Transporter Tool now allows changes in production with no loss of comparability, for further details check the transporter page


Fixes and minor changes