key element : business intelligence

Elasticsearch

Elasticsearch is a search engine based on the Lucene library. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.
Elasticsearch is developed in Java and is dual-licensed under the source-available Server Side Public License and the Elastic license, while other parts fall under the proprietary (source-available) Elastic License.
Official clients are available in Java, .NET (C#), PHP, Python, Apache Groovy, Ruby and many other languages.According to the DB-Engines ranking, Elasticsearch is the most popular enterprise search engine followed by Apache Solr, also based on Lucene.

Kibana

Elasticsearch

Kibana is a data visualization dashboard software for Elasticsearch. It provides visualization capabilities on top of the content indexed on an Elasticsearch cluster. Users can create bar, line and scatter plots, or pie charts and maps on top of large volumes of data.
Kibana also provides a presentation tool, referred to as Canvas, that allows users to create slide decks that pull live data directly from Elasticsearch.
The combination of Elasticsearch, Logstash, and Kibana, referred to as the "Elastic Stack" (formerly the "ELK stack"), is available as a product or service.
Logstash provides an input stream to Elasticsearch for storage and search, and Kibana accesses the data for visualizations such as dashboards.
Elastic also provides "Beats" packages which can be configured to provide pre-made Kibana visualizations and dashboards about various database and application technologies.
In December 2019, Elastic introduced Kibana Lens product.

key element : integration

Custom program interface for Flow steps

Custom program interface for Electronic Forms

Fluid allows for custom Java Program execution at Java Program steps. This is done as follows:

Reference the FLUID Custom Program library during development
Include the complete set of Java Classes in a single Java Archive (JAR)
Upload the custom developed component into FLUID via the Web interface

Custom program interface for Electronic Forms

Fluid allows for custom Java Program execution when performing actions on ‘Electronic Forms’. This is done as follows:

Reference the FLUID Custom Program library during development
Include the complete set of Java Classes in a single Java Archive (JAR)
Upload the custom developed component into FLUID via the Web interface

Application Programming Interface (API)

Custom program interface for Electronic Forms

Application Programming Interface (API)

Access to the inner workings and stored content in FLUID, can be accessed via the Restful JavaScript Object Notation (JSON) Web Service

key element : Auditability

Auditability and Traceability

The first layer of protection in any system, is to manage user and role permissions. This is configured and managed in the FLUID Admin system.

FLUID by design will record and track all changes that are made in the system. Every transaction and function is traceable and auditable.

Document and Template Auditing

FLUID by default will assign a new version to any changes in a document or template that is made within FLUID. These changes can be viewed, audited and reported.

Digital Form and Field Auditing

FLUID associates "Fields" and "Forms" with each other. Any changes made to "Fields" will automatically update a "Form".

All changes made are managed by role permissions and are fully auditable and reportable.

Workflow route

All changes made to the Route is tracked

Electronic Form Business Process historical data does not get altered when the Flow is changed

Administrative auditability

All administrative and configuration tasks performed are managed by role permissions and auditable

key element : security

Content security

Each implementation has the choice of storing the attachment or file content at the final destination using symmetric encryption.
The 256-bit symmetric key will be generated and stored in the FLUID database, although a derived or poisoned variant of the key will be used during encryption and decryption.
The following attributes form part of the security:
256-Bit Key size
Cipher-block Chaining (CBC)
Initialization Vector
Key poisoning
Secure Random
PKCS5 Padding

Application / Web security

Fully supported Asymmetric encryption from the chosen J2EE server:
SSL 1.0, SSL 2.0 and SSL 3.0 (Secure Sockets Layer)
TLS 1.1, TLS 1.2 (Transport Layer Security)

API (Application Programming Interface) Security

Fully supported Asymmetric encryption from the chosen J2EE server:

SSL 1.0, SSL 2.0 and SSL 3.0 (Secure Sockets Layer)
TLS 1.1, TLS 1.2 (Transport Layer Security)
The authentication for the API is done via Kerberos security model
The authorization is configured as part of the FLUID ACL framework / configuration

Authentication and Authorization

The Access Control List (ACL) model used in FLUID makes it possible for users of the system to send electronic forms to their colleagues without exposing sensitive content to the recipient

key element : business intelligence

Elasticsearch

Elasticsearch

Elasticsearch

Kibana

Elasticsearch

Elasticsearch

key element : integration

Custom program interface for Flow steps

Custom program interface for Electronic Forms

Custom program interface for Electronic Forms

Custom program interface for Electronic Forms

Custom program interface for Electronic Forms

Custom program interface for Electronic Forms

Application Programming Interface (API)

Custom program interface for Electronic Forms

Application Programming Interface (API)

key element : Auditability

Auditability and Traceability

Document and Template Auditing

Digital Form and Field Auditing

Workflow route

Administrative auditability

key element : security

Content security

Application / Web security

API (Application Programming Interface) Security

Authentication and Authorization

This website uses cookies.