AdaptableBlotter.JS Tech Spec

AdaptableBlotter.JS is a purely native JavaScript widget running in the browser.  It is compatible with the most recent versions of all the major browsers.

 

AdaptableBlotter.JS contains a single download.

Audit Log

The audit log allows you to keep abreast of all changes that are taking place in the Blotter.  It receives a stream of updates concerning data changes, user changes and much else so you can stay updated with what has happened to your data. 

 

The audit stream is sent through an HTTP Channel and you can then use whichever technologies you prefer to listen to the messages and build reports, using the tools which your organisation has already configured.

 

If the Adaptable Blotter determines that nothing is listening to the logs then it stops sending them automatically.

 

Many of our users use a pipeline using Elastic products to listen to the audit log HTTP Channel.  In this scenario, Logstash sends all the audit data to Elasticsearch which stores it centrally and it is then queried using Kibana

 

Our Support Team can provide you with advice on how to listen to the Audit data channel and report on it. 

 

Whatever internal tools you decide to use, you can have real-time access to everything that has happened in your Blotters and receive immediate alerts if something happens that you need to know about.

Configuration

AdaptableBlotter.JS makes it easy for administrators and developers to configure user settings, storage location details, user permissions and other related information, in a location most suitable for each team’s needs.

 

Most configuration is done using the Configuration Server component.

 

There are 4 types of configuration data AdaptableBlotter.JS deals with:

 

  • User Configuration - e.g. whether dashboard is collapsed or expanded, which layout is loaded

  • User Data (user-created Blotter Entities) - e.g. Advanced Searches, Layouts, Shortcuts etc. Anything that a user creates or edits while using Adaptable Blotter is configurable and stored

  • Application Configuration - e.g. show only some toolbar buttons in Dashboard when first launching the application. Application Configuration also contains all User Permission information (e.g. whether a Function is visible, read only, or hidden for a particular User or Role).

  • Application Data (predefined Blotter Entities) - e.g. a predefined Search called "Today's Trades", Shortcuts where 'M' multiples numeric cells by 1,000,000

 

There are 2 modes of storage available in AdaptableBlotter.JS:

 

Local Storage

 

When using Local Storage the User Configuration is stored in the browser's local storage using the Blotter's unique Id.

 

When the application is launched for the first time the User Configuration is initialised together with the Application Configuration (if there is one).

 

At run-time both the User Data and Application Data are fully available - but all Application Data is Read-Only.

 

All User Configuration changes are persisted but to local cache only.

 

Remote Storage (using Configuration Server)

 

When using Remote Storage, the User Configuration is stored (via Configuration Server) on a configured location.

 

When the application is first launched, the User Configuration is initialised together with the Application Configuration (if there is one).

 

At run-time both User Data and Application Data are fully available - but all Application Data is Read-Only.

 

All configuration changes are sent to the Configuration Server and then persisted in the appropriate location.

AdaptableBlotter.JS  has no external dependencies on any containers.  However future AdaptableBlotter.JS versions will leverage both OpenFin and Electron so those who are using these containers can automatically take advantage of the extra features these offer.

 

AdaptableBlotter.JS additionally contains Audit Log, which enables you to see all activity in the Blotter, and Configuration Server which helps you to manage user permissions, storage locations and team sharing.

Team Sharing

Team Sharing allows end-users easily to share part of their own configuration data with other users in the same team e.g. one user can create a "Pricing View" layout, or a new Cell Validation editing rule, and then, with just a single click, can share that layout or rule with all other members of the team who will have immediate access to the newly created objects.

 

Each time a Blotter Element is created, it can be instantly shared with team members.

 

Administrators or developers are able to configure Team Sharing at design time.

+44 (0)20 7078 4141

sales@adaptabletools.com

Enter your text here

Enter your text here