In order to improve the monitoring of web applications, a new log file is available.
The accuracy of the log file can be manually configured in the Web Server Configuration file that by default is in the following path:
C:\Program Files (x86)\Board\Board WebApi Server\App_Data\config\log.config
Short Notices:
if you do not find this file in the App_Data folder, you can download it here
Any change to the configuration file is immediately active. It is not necessary to restart the service
How to activate the web login
The log is automatically enabled during the installation of the Board 10.1.4 and can't be disabled. To activate it in existing installation, also after the version updated, download etc etc.
With trace logging enabled, actions and results are logged to a file in a location you indicate. it is possible to define different properties of the tracking.
How to configure the properties of the Web Log
Open the file with Notepad.
Scroll the file and change the following parameters
<targets>: it defines the properties of the log file. Possible values of this parameter are:
writeTo: It is the file path and name. Including the statement {Date} as part of the file name , the system creates a new log file every day.
minimunLevel: defines the level of accuracy of messages in the log file. Possible values of this parameter are:
Error: only exceptions and critical errors are logged
Debug: : more details are logged, warning and useful information for troubleshooting
Verbose: all client/server communications
Short Notices:
By default the Accuracy level of the Log is set = Error (minimum) .
<features>: When the minimumLevel is set to Debug or Verbose, it is possible to apply filters to log only some specific instructions. Filters do not impact the error tracking.
Possible values of this parameter are:
System: Web proxy status, Stop and start, recycle, client actions ..
Authentication: all information and messages about authentication, including Saml2
Procedures: all procedure messages and client-side actions such as refresh, go to screen, popup, etc..
ServerTask: all interactions with Board Engine task such as engine up and running, running batch etc
All: all instructions above
Possible values of this parameter are:
username: the name of the User which actions you like to track. If you add the username=UNKNOWN all the actions that can't be attribute to a specific user will be tracked too, such as Opening the Web Home Page (before logging)
Short Notices:
if you do not explicitly name any user all the users will be tracked
Web: A malfunction generated by the Dynawrite which body has an empty row has been solved
Web: An unexpected consumption of the resources such as Memory, when multiple tabs/screens are opened, has been solved
Web: Large data-view optimization. The visualization of large data-views is faster now.
Web: Large data-view optimization. The scroll of large data-views is faster now.
Web: The message queue polling has been improved
Web: The mechanism of the Procedure Checkpoints (Error or Confirmation messages) has been improved
Web: A situation where the procedure windows is frozen after the procedure is completed has been fixed
Backup: A malfunction that prevents the cleaning of obsolete back-up copies of the Board database through the execution of a Procedure Command has been fixed. It is now possible to define a different expiration date for each database
Export: A malfunction generated during the export of a screen with many iterations like Broadcasting and export with pager, has been solved. (some objects were shifted one pixel down after each iteration).
Call Procedure Command. When you're developing a database template, that you can potentially use to generate several identical Data-Marts, it is suggested to enable this option when using a Call Procedure Command on such data-base . If active the Call Command eventually ignores a rename of the database.
Transporter Tool: A malfunction that did not allow the comparison of databases has been solved (Download Images).
Transporter Tool: It is now possible to transport all the procedures, including those that have been modified. Updates performed into an existing procedure will be promoted to production.
Transporter Tool: It is now possible to compare databases with different names. This solution allows to transport changes from a template database to child-databases (data-marts), regardless of the database name.
Yahoo Finance, the service is being discontinued. Yahoo has blocked this service and at the moment is not possible to use the Rest APIs.
WARNING: horizontal selector, which height is less than 42pixel, could generate an error message on the win client.
After upgrading the Board Server it is required to upgrade all Board Client and Office Add-in installations to the same version 10.1.4. A Capsule created or saved using version 10.1.3 can't be re-opened with an older version such as version 10.0.3 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 .
In such situation the Log Tracking will be activated only and if only the log.config file is created in the proper folder (see above). Upgrading from 10.1.x to 10.1.4 doesn't create the file. Only new installation does. You can then download the file from here and copy it in the folder.
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.X located in the folder mentioned above.
It is of course not necessary if you already run 10.1.0 or later.
In such situation the Log Tracking will be activated only and if only the log.config file is created in the proper folder (see above). Upgrading from 10.1.x to 10.1.4 doesn't create the file. Only new installation does. You can then download the file from here and copy it in the folder.