The new Card object is available on the web application. The Card object is an alternative and graphical representation of the standard dataview object. The object is available on the toolboxes list on the web editor.
Once the object is dragged in the screen, the configuration is a standard layout setting. The blocks can be of any type (numeric, text, blobs) with the standard options like the data-entry available. The blocks are also drillable.
The layout configuration has the following constrains:
one entity by row in the axis
the columns are not available
the detail by is not available
As soon as the row axis is defined, a card that contains all the blocks defined in the layout is shown per each of the occurrences of that entity. Each block is shown in the layout editor as a rectangle that can be positioned and resized inside the card.
The card object is responsive. So, once the layout is configured, the card object puts as many cards element as possible on each single line.
It is possible to configure a fixed card height and width from the card settings panel. It is also possible to configure a gap between each of the card elements.
Additionally, there is a dynamic option for the card width, so there is a max and a min width to configure to have the objects automatically resized within these limits. These sizes are measured in number of pixels.
The new Responsive Container is now available on the toolboxes list of the web application. Once the object is dragged into the screen in design mode, it is possible to add other toolboxes (like dataviews, charts, labels, etc..) inside the container. Then it is possible to configure the layouts of the child elements.
As per the Card object, there are 2 available options for the children width under the grid settings: Fixed and Dynamic. This configuration will drive the sizing and positioning of the children objects. The dynamic option will help in fitting the available space in a better manner.
A new Expander object is available on the web application. The Expander is a container where it is possible to position child elements (other toolboxes). The child objects are displayed in column: 1st object then 2nd object below the 1st and so on. On these objects it is possible to set-up the visibility option. While the screen is in play mode, the position of these child objects depends on the result of the visibility properties. For example, if the expander contains 2 objects 1 dataview above and a chart below, if the visibility of the dataview is hiding the object, the chart is switched in the first position inside the expander container. Below an example:
A new Quick Edit functionality is available on the web application. This feature is available only for the Dataview object for now. From the quick Edit it is possible to show or hide on the fly the visible blocks defined in the layout.
It is also possible to modify on the fly the axes of a layout. From the rows & columns menu it is possible to move the existing entities on the axes or to set other additional entities that are not present in the original dataview axes saved on the screen but have been set up by the screen developer in the layout settings.
The Quick Edit Layout can be enabled or disabled from the layout editor. By default the Quick Edit is enabled in al the new dataviews and in the dataviews that already exists in a capsule. From the layout editor the quick edit configuration is available under the settings. It is possible to enable/disable it and configure additional entities that will be available by the end user on the screen in play mode. Additional entities can be added from the Add field, typing the name of the entity.
The Procedure Debugger is now available on the web application. The breakpoints can be enabled or disabled from the procedure designer when in edit mode.
When the procedure run, at the first breakpoint the debugger console is shown up with all its available commands.
From there it is possible to control the execution flow with the buttons Continue, Next and Stop. Continue executes the procedure until the next breakpoint. Next executes the next step (with or without the breakpoint). Stop will break the execution of the procedure. There are then other command on the console to check the results of he procedure execution.
(1) clicking this icon it is possible to jump into the procedure and edit it
(2) it is possible to check the current selection during the procedure execution
(3) it is possible to create layouts and check data during the procedure execution
It is now possible to configure a specific font family on the web objects. The Font configuration is available on the right-side configuration panel selecting the web object in edit mode.
There is also the possibility to upload a Corporate Font on hte web application. The corporate Font will be available on the entire environmnet. This font can be uploaded from the Them section, available under the System Administration space.
It is possible to load a Corporate Font for the capsule objects (.woff format supported) and one for the PDF exports (.ttf format supported).
When configuring a Go to screen action, it is now possible to select another capsule and a target screen for the navigation procedure. The configuration is shown in the below image.
A new option is available on the data-entry lock configuration. It is possible to decide if the locking block is locking when the value is 0 or different than 0. Blow the new configuration box.
The settings configuration of the selector object has been reviewed as per the below image:
The Pause and Play function of the selector has been reviewed and enhanced. Multiple members selections dragging the mouse over the selector object are now supported.
It is now possible to configure an export action from a procedure. The files are exported on the server. The available export functions are:
1) Create Report procedure step: available in capsule procedures under the screen group. It runs the printing function on a specific screen when it's called from a procedure.
2) Export Data procedure step: available in capsule procedures under the screen group. It runs the export data in excel format on a specific screen when it's called from a procedure.
3) Export Presentation: available in capsule procedures under the Broadcasting group. It exports a presentation in a specific folder on the server that is running the Board Web API Engine. The Root Path by default is "C:/Board/Export". This parameter can be customized in the appsettings.config configuration file of the Board Web API Engine (available in the App_Data folder). This customization can be done adding the following parameter: <add key="exportPresentationActionRoots" value="path" /> where path is a custom root path. Multiple paths can be added using the comma as a separator. Then, multiple path choices will be available on the drop-down list in the root path field while configuring the procedure step. The sub path is not mandatory.
It is now possible to automatize the execution of a transporter package. A Transporter package can be executed from MS Windows Powershell and command line or from Unix shell. This allows to automate and schedule the execution of Transporter packages during a given service window. This automation is available under the System Administration section on the CLI automation tile.
All the instructions on how to run it are available on the CLI automation section of the web application.
It is mandatory to enable the Token service and create and have available the transporter package on the target instance.
The naming convention on the data-reader actions has been changed on the web application.
In the bullet chart it is now possible to configure drills, master layout and apply a selection from the sliding toolbar.
It is now available a shortcut to jump in edit mode into a procedure from a screen object where the procedure is launched.
The Gauge object supports the drill-down function.
The dataview search supports a multi-line text (it works in OR).
An enforcement of the Sparse Structure to prevent database corruptions has been introduced in this version.
A malfunction on the Broadcasting scheduled tasks that occurs when a task is not configured properly has been fixed.
A malfunction in the concurrent opening of capsules and screens that was holding the BoardFolderProfiles.dat file has been corrected.
The decimal separators on a excel extraction are now consistent between the sublines and the totals.
The clear entity action doesn't display the standard time entity list anymore.
The suggested values list based on an entity in a dataview follows the screen selections.
Azure AD authentication through the SAML2 protocol is now supported on the win client and the office add-in.
The apply on totals option on the rule blocks is now available on the web designer.
Enhancements in the management of exceptions during the transporter actions.
The suggested values are now available in the drill-down window on the web.
An enforcement on the protection from XSS attacks has been applied on the web application.
The save/undo option affects also the data-entry on BLOB cubes on the web application.
A visual issue (absence of scrollbars) in the file upload page on the cloud platform has been fixed.
A malfunction on the data-reader ETL while is evaluating a numerical vs text type has been fixed.
A malfunction on the execution of an ETL combined with the regional settings of the Windows user that is running the BOARD service has been fixed.
A fix on the propagate cell template in the dataview settings has been introduce on the web.
A malfunction on the ASCII data-reader procedure step that is showing the wrong detail information about the protocol has been fixed.
The relationships management on the web has been reviewed and optimized.
A malfunction on entity block treated as numeric in dataview layouts has been fixed.
Decimals digits are now visible on the geomap blocks.
A malfunction on the procedure launcher due to case sensitive characters has been fixed.
A malfunction on the ATO insert new member function and the code length of new members has been fixed.
A malfunction on the edit description of the ATO pager has been resolved.
A malfunction on the disable record count option on the data-readers connection definition has been fixed.
A malfunction on select entity based on cube not displaying all related cubes has been fixed.
A malfunction on the Broadcasting for which modifications on an existing task were invalidating it has been fixed.
A misalignment between the Win Client and Web Client on the management of subtotals and locked cells has been resolved.
A malfunction on the Impact Analysis due to the Folder Profiles configuration has been fixed.
Version 10.6 has a full web HTML5 client. Capsules that are created from the web client have a new format: ".bcps". The old ".cpsx" capsule can be still used in play mode in the old format. Old capsule in ".cpsx" need to converted into the new ".bcps" format to be used in edit mode on the web client (a common web browser). The migration process is automatic and documented HERE. The system will retain a copy of the capsule in the old format renaming it with the "(BKP) tag in the capsule name. The ".bcps" capsules cannot be opened from the BOARD Windows Client.
Broadcasting features installation
The broadcasting features (subscription, send to and broadcasting) require an additional service that execute the mailing function. The web API Engine installation (self-hosted) deploys a new service "BoardMailerService" that is used for the Broadcasting like functions. If the Web API Engine has been deployed under IIS, this new service is not automatically deployed on the instance. An additional set of CMD commands must be run on the server to deploy that service.
Below the commands for the "BoardMailerService" deploy:
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe" "C:\inetpub\wwwroot\B10WEB\Bin\Board.Mailer.Service.exe"
sc config BoardMailerService start=auto
sc start BoardMailerService
Where "C:\inetpub\wwwroot\B10WEB" is the IIS path where the BOARD web application is hosted.
Other details on the configuration of the Mailer service can be found HERE.
Printing features installation
This features relies on a Windows process (Board.Web.Snapshotter.exe) that requires the installation of the .net Framework 4.7.1 . Please notice that this version of the .NET framework requires Windows Server 2012 or later.
If you are deploying the Board Web Service using IIS, make sure to configure your instance as described below:
|
The 'Snapshotter' folder must be cut from the Bin Folder and copied in the IIS Board Website Root (like the App_Data folder). For additional information please refer to the Boardville Community Wiki Document. |
|
In the Application Pool of the IIS Board Website, go to advance settings, and set parameter “Load User Profile” to true. |
No additional configuration are requested if you're deploying the Board Web Service suing its own http Server.
After upgrading the Board Server it is required to upgrade all Board Client and Office Add-in installations to the same version 10.6. A Capsule created or saved using version 10.6 can't be re-opened with an older version such as version 10.5.x or even older.
When you open Capsules created with prior versions of Board (version 9 or 8) a request of upgrade to Board 10 format prompts out. If you click Yes the Capsule is automatically updated in few secs and enabled to the Board Web Client. If you click 'No' you can still go on to use the Capsule but with the Board Win Client only
It is possible to change some settings of the Snapshotter Process editing the file C:\Program Files (x86)\Board\Board WebApi Server\App_Data\config\snapshotter.config (if you run IIS refer to IIS App_Data Folder location path).
| <add key="host" value="http://localhost:8011/" /> | It's the snapshotter process host address. Change the IP port if needed |
| <add key="applicationUrl" value="http://localhost/" /> | As configured on your site bindings, for example: https://yourhostname.board.com/ If the web application port has been changed, you need to specify the port here in the applicationUrl definition |
| <add key="minPoolSize" value="1" /> | It's the number of Web Client (Browsers) that can simultaneously generates reports. By default it is from 1 (min) to 5 (max) |
| <add key="maxPoolSize" value="5" /> | |
| <add key="workingFolderPath" value="..\reporting\" /> | The temporary folder path where screenshots are saved while generating the report |
| <add key="logLevel" value="Error"/> | You can setup Error, Verbose, Debug. (Error by Default) |
| <add key="logPath" value="..\log\Snapshotter\{Date}.log" /> | The folder Path where logs generated by the reporting jobs are saved. |
