low level feature set for fluid - usiness management …€¦ · fluid produ t sheet low level...

FLUID PRODUCT SHEET LOW LEVEL FEATURE SET FOR FLUID - BUSINESS MANAGEMENT SYSTEM

KOEKIEBOX (PTY) LTD

FEBRUARY 17, 2017

1 | P a g e

Copyright © 2014 by Koekiebox (Pty) Ltd. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means — electronic, mechanical, photocopying, recording, or otherwise — without the permission of Koekiebox (Pty) Ltd.

CONTENTS

About Fluid ................................................................................................................................................. 4

Introduction ............................................................................................................................................... 5

Content Management Capabilities ............................................................................................................ 7

Database ................................................................................................................................................ 7

Filesystem Storage ................................................................................................................................. 7

Amazon S3 ............................................................................................................................................. 7

Supported File Types .............................................................................................................................. 7

Content Storage / Attachment Versioning ............................................................................................. 9

Electronic form capabilities ....................................................................................................................... 9

User Dashboard Screenshot .................................................................................................................. 9

Electronic Form Screenshot ................................................................................................................. 10

Customized User Queries..................................................................................................................... 10

Supported Field and Data Types .......................................................................................................... 11

Electronic Form Ancestor and Descendant Capabilities ...................................................................... 15

Field Scopes ......................................................................................................................................... 15

Electronic form Retrieval Electronic Form Lookup .............................................................................. 16

Electronic Form Field Versioning ......................................................................................................... 16

Users & Roles (Access Control Lists) ........................................................................................................ 16

Roles ..................................................................................................................................................... 16

Electronic Form Actions ....................................................................................................................... 16

User Queries ........................................................................................................................................ 17

Workflow Capabilities .............................................................................................................................. 17

Rule Engine .......................................................................................................................................... 17

Rule Traceability ................................................................................................................................... 17

Rule Step Types .................................................................................................................................... 17

Supported Rule Engine Functions ........................................................................................................ 18

Work Distribution................................................................................................................................. 19

Integration Capabilities ............................................................................................................................ 20

Custom Program interface for Flow Steps ........................................................................................... 20

Custom Program interface for Electronic Forms.................................................................................. 21

2 | P a g e


Application Programming Interface (API) ............................................................................................ 21

Scheduled Events ................................................................................................................................. 21

Reporting Capabilities .............................................................................................................................. 21

User Punchcard .................................................................................................................................... 21

Staff and System overall performance ................................................................................................. 21

Departmental Performance ................................................................................................................. 21

Content Storage Utilization .................................................................................................................. 21

Business Intelligence ................................................................................................................................ 21

Apache Lucene through Elasticsearch ................................................................................................. 21

Kibana .................................................................................................................................................. 22

Security .................................................................................................................................................... 22

Content Security .................................................................................................................................. 22

Electronic Form Field Security ............................................................................................................. 22

Application / Web Security .................................................................................................................. 23

API (Application Programming Interface) Security .............................................................................. 23

Authentication and Authorization ....................................................................................................... 23

Auditability and Traceability .................................................................................................................... 23

Content Auditability ............................................................................................................................. 23

Electronic Form Auditability ................................................................................................................ 23

Workflow Route ................................................................................................................................... 23

Administrative Auditability .................................................................................................................. 24

User Punchcard .................................................................................................................................... 24

Fluid Messenger ....................................................................................................................................... 24

Supported Operating Systems (Server Side) ............................................................................................ 24

Supported Browsers................................................................................................................................. 24

Mobile Browser Support ...................................................................................................................... 25

Supported Database Engines ................................................................................................................... 25

Supported Application Servers ................................................................................................................ 25

Product Roadmap .................................................................................................................................... 26

Import and Export of Flows ................................................................................................................. 26

Office Plugins ....................................................................................................................................... 26

3 | P a g e


Microsoft Power BI .............................................................................................................................. 26

Docker Certified Fluid Images .............................................................................................................. 26

4 | P a g e


ABOUT FLUID

Fluid was born out of a deep understanding of the needs of modern business.

The management of any principal business is driven by the requisites for cost effective and efficient management, whilst delivering to customers. Central to management is information. Information is POWER and the ability to access this information is key, as are successful tools required to deliver this management capability.

In addition, businesses need to be agile and adaptable to respond to ever changing market demands. Even small businesses now require enterprise solutions that can be implemented and changed at speed.

It is a reality that by the time traditional systems are implemented, they are clunky, constrained i.e. legacy systems before they can bear fruit.

The APP revolution has forced the focus on INSTANT IMPROVED processing and INSTANT IMPROVED communication with customers; and traditional systems fail to do this in a cost-effective way.

Furthermore, there is an appreciation that a business cannot simply eliminate what is in place and replace it with totally new environment. The practical preference should be rather to adapt and use what is already in place and to enhance it.

Moreover, Governance demands on businesses add another onerous layer of delivery and necessity for agility.

Fluid is an Enterprise Java application that brings this ALL together …. process management; document or object management; and data management …. in one elegant, agile and integrated solution that is entirely auditable and secure.

5 | P a g e


INTRODUCTION

The following goals were regarded high during the architecture and design of the system; ✓ Simplicity

➢ Configuration and usage of the system have been designed in a way to make it simple to

install, configure and utilize the system.

✓ Flexibility and extensibility

➢ Flexibility and extensibility forms the core part of Fluid’s principles and vision.

➢ Great though and architectural design have been incorporated to ensure any business

requirement can be met.

✓ Adaptability

➢ Fluid was designed to rather adapt into an existing or new environment with the system

enhancing, rather than replacing existing processes or systems. This is due to the unique

approach taken for custom integrations.

✓ Security

➢ Security has been taken into consideration for all aspects including Content Security,

Application / Web Security, API (Application Programming Interface) Security, Accessibility

✓ Maintenance and Downtime

➢ Little or no downtime during system maintenance or modifications.

✓ User Interface

➢ The Fluid user interface is completely Web Based.

➢ One has the ability to develop a custom front-end or application that can interact with

the Fluid engine via the Fluid (API) Application Programming Interface.

✓ Business Process Management

➢ The Visual Design tools are Web Based, ensuring single point of entry rule changes and

collaboration.

✓ Integration

➢ Integration to and from Fluid is made simple and possible via Fluid Custom Program, API

and Scheduled tasks

✓ Reporting

➢ User Punch Card Reports. Includes accurate data on how long users were logged in and

performing work functions.

➢ Staff and System overall performance.

➢ Content Storage Utilization

✓ Administration

➢ Easily administer work management and re-assignment from an administrative

perspective.

✓ Configuration

➢ Single point of entry for all configurations

6 | P a g e


The aim for Fluid is to excel in each of the Forrester identified Business Process Landscapes;

7 | P a g e


CONTENT MANAGEMENT CAPABILITIES

Fluid has a variety of different content storage abilities depending on the deployment environment.

For more information on Content Storage Security, see Content Security.

DATABASE

Store the file content directly in the database.

FILESYSTEM STORAGE

Store the file content on a network drive or local file server.

This is best suited when you don’t want to store content off site.

AMAZON S3

Store the file content on Amazon’s Simple Storage Service, see http://aws.amazon.com/s3/. This is ideal for when one wants to run Fluid in the cloud.

SUPPORTED FILE TYPES

Below is a list of supported attachment types and their extensions.

Mimetype File Extension

image/png png

image/jpeg jpe,jpeg,jpg

image/tiff tiff,tif

image/gif gif

text/plain txt

text/xml xml

text/html shtml,html,htm

application/json json

application/mp4 mp4

http://aws.amazon.com/s3/

8 | P a g e


application/pdf pdf

application/zip zip

application/rtf rtf

application/msword doc,dot

application/vnd.openxmlformats-officedocument.wordprocessingml.document docx

application/vnd.openxmlformats-officedocument.wordprocessingml.template dotx

application/vnd.ms-excel xls

application/vnd.openxmlformats-officedocument.spreadsheetml.sheet xlsx

application/vnd.openxmlformats-officedocument.spreadsheetml.template xltx

application/vnd.ms-powerpoint ppt,pps,ppa,pot

application/vnd.openxmlformats-officedocument.presentationml.presentation pptx

application/vnd.openxmlformats-officedocument.presentationml.template potx

application/vnd.openxmlformats-officedocument.presentationml.slideshow ppsx

audio/mpeg3 mp3

application/java-archive jar

application/x-java-class class

application/vnd.ms-outlook msg

application/x-tar tar, tar.gz

text/csv csv

9 | P a g e


CONTENT STORAGE / ATTACHMENT VERSIONING

Fluid manages file versioning internally.

Every time an updated version of a file is created against an electronic form, the previous version is preserved and the newly updated version becomes the primary, still making it easy to access older file versions.

ELECTRONIC FORM CAPABILITIES

Electronic forms are used to couple File Content, Historic Data and Fields.

The Electronic Form is the main element exposed to the Fluid user in addition to the User Dashboard.

USER DASHBOARD SCREENSHOT

The main user view. Follows similar view to that of an email inbox to make the user familiar with an environment that feels close to home.

10 | P a g e


ELECTRONIC FORM SCREENSHOT

Electronic form that combines fields to create Electronic Form or Document Types.

The electronic forms will likely form part of a workflow.

CUSTOMIZED USER QUERIES

Create Custom User Queries that allows a user to run quick report or query to access information.

11 | P a g e


SUPPORTED FIELD AND DATA TYPES

Fluid supports an overwhelming 19 data types to ensure any business need from a form capturing basis is met and transcended.

Below is a list of supported electronic field data types and a brief description of each;

Field Type Sub Type Description

Text Plain Alphanumeric data up to 255 characters.

Text Masked Alphanumeric data up to 255 characters with masking ability. This ensures that specific formats are followed when capturing data, for example; a phone number or email address.

Text Barcode Alphanumeric data up to 255 characters with a barcode as an output.

Text Location Ability to store Longitude and Latitude locations for use in Google Maps.

True / False True / False Useful when only a simple yes or no value is expected.

Paragraph Text Plain Used to store data that usually contain more than 255

12 | P a g e


characters.

Paragraph Text HTML Hyper Text Transfer Protocol data usually used to store rich text.

Paragraph Text Signature

Multiple Choice Plain or Searchable

Limit certain field data by allowing for data to be selected from a combo-box.

or

Multiple Choice Select many with Search option supported

Limit certain field data by allowing for data to be selected from a selection of choices.

Useful when requiring one or more values to be selected.

13 | P a g e


or

Date Time Date Date field used to store date specific information.

Date Time Date and Time Date field used to store date-and-time specific information.

Decimal Plain Numeric data.

14 | P a g e


Decimal Spinner Numeric data in the form of a spinner with a forced minimum and maximum range value.

* Data manually entered usually.

Decimal Slider Numeric data in the form of a slider with a forced minimum and maximum range value.

Decimal Rating Numeric data in the form of a rating visual interface.

Table Field Predefined Form Definition

Ability to store Field Data in a tabular format based on a preconfigured Form Definition.

* Ideal for; ● Accounting ● Stock taking ● Timesheets

Text Encrypted Plain A field that will always be stored as a encrypted value, but viewed in the clear.

Text Encrypted Masked A field that will always be stored as an encrypted value and when displayed, only partially revealed

(where permissions appropriate).

15 | P a g e


ELECTRONIC FORM ANCESTOR AND DESCENDANT CAPABILITIES

Each Electronic form in Fluid could evolve into a more complex Electronic form as the business process or flow progresses.

This is achieved by each electronic form having a single Ancestor / Parent but multiple Descendants / Children hierarchy.

Each of the children or parent may be involved in a separate business process.

FIELD SCOPES

Field Scopes allows one to define where a field belongs and what role each field plays, below is a list of Fields and the purpose they serve in Fluid;

Scope Description

User Store a field against a user in the system.

Examples include;

Salary, Income, Available leave days etc.

Form Store a field against a Form in the system that will later form part of a Form Definition.

Examples include;

Identity Number for an Identity Document,

Number of Leave Days requested for a Leave Form.

Route Store a field in the system that will only live for as long as a particular form is in a business process. This will typically be a field that is not present to the users of the system.

Examples include;

How long an Electronic Form has been in a particular

department.

Global Store a field in the system that will be accessible from anywhere in the Fluid system.

This will typically be a field that is not present to the users of the system, but only to administrators.

Examples include;

The number of leave days accumulated per annum.

The date and time format for a region.

16 | P a g e


ELECTRONIC FORM RETRIEVAL ELECTRONIC FORM LOOKUP

To access stored Electronic Forms and content from Fluid, one can make use of preconfigured Search capabilities or spotlight.

Spotlight Search

Perform a quick search based on key indexes of the Electronic Forms stored in Fluid.

Preconfigured User Query Search

Fluid supports a feature whereby searches can be completely customized based on Electronic Field and Form Definitions.

Each of the customized searched can be associated with a specific role, thus limiting the available searches to only what that role is allowed.

ELECTRONIC FORM FIELD VERSIONING

Fluid automatically track changes made to each of the Electronic Form Fields.

This ensures that all requirements are met from a auditability perspective

USERS & ROLES (ACCESS CONTROL LISTS)

Visibility and access to Views, Electronic Forms and Fields, Preconfigured Searches, Administrative Functions, Application Programming Interface (API) are all controlled via Roles, these roles are then assigned to the users. One user can have access to more than one role.

More in depth details below;

ROLES

Fluid supports an advanced ACL function that can grant or deny visibility and accessibility on all levels.

The following attributes may be associated with a role.

Administrative Functions

Limit access to administrative functions in the system like modifying Flows, Electronic Form Definitions, Fields, User’s, Workflow monitoring and system Configuration.

Views

View’s enable users to view their “Work-In-Progress” from the User Dashboard interface.

The views are created and refined via the Assignment Flow Step.

ELECTRONIC FORM ACTIONS

Access for a specific role can be changed to Field level.

Changes to the role can be made to restrict certain document access completely, or only certain fields.

This is very useful when sending Electronic forms within one's organization and concealing sensitive data.

17 | P a g e


USER QUERIES

Customized searches associated with a Role to easily access existing Attachment and Electronic Form data.

WORKFLOW CAPABILITIES

Below is a list of features supported by the workflow and business process engine of Fluid.

RULE ENGINE

The rule engine is responsible for carrying out numerous operations. The rule engine allows for rules of type Workflow Entry, Exit, View and User Query.

RULE TRACEABILITY

Each action carried out in the route is logged, as with the rest of Fluid.

When changes are made to the business process, the rules executed at an earlier time won’t be affected.

RULE STEP TYPES

The following Step Types or areas of operation are supported;

Step Type Description

Introduction Entry point for business processes.

Initiates the business process and associated rules.

Re Route Remove an item from one business process (Flow) and send it to another.

Exit End point for a business process.

Terminates the business process and associated rules.

Assignment Step in the business process where human interaction is necessary in order for the business process to continue.

This step is exposed to the users via a Role.

Database Capture Import data from an external Database Management System into Fluid by using a preconfigured Data Source.

18 | P a g e


Mail Capture Import mail from an Internet Message Access Protocol (IMAP) or Post Office Protocol (POP) mailbox.

Send Mail Send mail from the business process via Simple Mail Transfer Protocol (SMTP).

Tweet Send a tweet message at a certain point in the business process.

Java Program Execute a Custom Java Program that enables one to take full advantage of the Java programming language.

Only Java Standard Edition experience is necessary.

Clone Item Make a copy of an existing item into another, in order to support business processes with additional complexities.

SUPPORTED RULE ENGINE FUNCTIONS

Below is a list of functions supported by the rule engine.

Conditional Functions

Function Description

EQUAL Check whether two fields are equal in a condition statement.

IS_EMPTY Check whether the value of a field is empty.

AND Compare one conditional value or statement against another.

If both values equate to True, the result will be True.

OR Compare one conditional value or statement against another.

If one of the values equate to True, the result will be True.

NOT_EQUAL Check whether two fields are not equal in a condition statement.

If the values are not equal, the result of the condition would be True.

LESS_THAN Equates to True if the value on the left of two fields is less than the value on the right. Otherwise the function equates to False.

19 | P a g e


GREATHER_THAN Equates to True if the value on the left of two fields is greater than the value on the right. Otherwise the function equates to False.

WORK DISTRIBUTION

Fluid allows one to step out of the normal business flow to cater for scenarios whereby external input is required to continue the business process.

The functions below allow for the normal business flow to be interrupted to continue the business process.

Send to Colleague

Send an Electronic Form to a colleague for review or changes before advancing to the next steps in the business process.

Case Flow Allocation

If the configured Flow rules are followed, Electronic Forms that require attention will be accessed via the Views, which is configured via the Flow.

Business Process Flow Management Screenshot

20 | P a g e


INTEGRATION CAPABILITIES

Integration downstream and upstream have been made as simple as possible.

Deployment of custom components are done easily and reflect instantly without system downtime.

The Fluid-API is a publicly available framework and may be found at;

https://github.com/Koekiebox-PTY-LTD/Fluid

CUSTOM PROGRAM INTERFACE FOR FLOW STEPS

Fluid allows for custom Java Program execution at Java Program steps.

This is done as follows; 1. Reference the Fluid Custom Program library during development.

2. Include the complete set of Java Classes in a single Java Archive (JAR).

3. Upload the custom developed component into Fluid via the Web interface.

https://github.com/Koekiebox-PTY-LTD/Fluid

21 | P a g e


CUSTOM PROGRAM INTERFACE FOR ELECTRONIC FORMS

Fluid allows for custom Java Program execution at when performing actions on Electronic Forms.

This is done as follows; 1. Reference the Fluid Custom Program library during development.

2. Include the complete set of Java Classes in a single Java Archive (JAR).

3. Upload the custom developed component into Fluid via the Web interface.

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. The API is feature rich, but highly secured through asymmetric and symmetric cryptography.

SCHEDULED EVENTS

Ability to execute a custom program on a daily, weekly, monthly or annual basis.

REPORTING CAPABILITIES

To follow are the reports provided by the Fluid BPM system.

USER PUNCHCARD

Accurate reports on how active users are on the system and when the system was utilized.

STAFF AND SYSTEM OVERALL PERFORMANCE

Expose potential bottlenecks in the Process Flow or system integrations.

Easily measure expected vs actual workload (Key indicators).

DEPARTMENTAL PERFORMANCE

Measure the volume, performance and effectiveness of an area of the business.

CONTENT STORAGE UTILIZATION

Monitor the Current Storage and Electronic Form statistics.

BUSINESS INTELLIGENCE

To follow are the business intelligence provided by Fluid BPM system.

APACHE LUCENE THROUGH ELASTICSEARCH

Elasticsearch is a search engine based on Lucene (A high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform). It provides a distributed, multitenant-capable full-text search

22 | P a g e


engine with an HTTP web interface and schema-free JSON documents. Elasticsearch is also fast “really, really fast”.

Fluid fully supports Elasticsearch integration. Fluid will automatically configure the data mappings between Fluid and Elasticsearch datatypes.

Fluid User Queries are automatically converted to Elasticsearch equivalent queries. No previous Elasticsearch experience required.

Find out more at https://www.elastic.co/products/elasticsearch.

KIBANA

Kibana is a plugin 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 in high speed.

Find out more at https://www.elastic.co/products/kibana.

SECURITY

Security of the system is completely up to the implementation of the system.

The implementation can be done from making use of little or no security, to high security ranging from the topics below;

CONTENT SECURITY

Each implementation has the choice of storing the attachment or file content at the desired 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

ELECTRONIC FORM FIELD SECURITY

Fluid features a Field type called “Text Encrypted”. The Text Encrypted field allows for encrypted stored text based field data. In addition to encrypted stored values, the clear text value may also be concealed (Masked) and only revealed to users with the relevant access.

The following attributes form part of the security; ● 256-Bit Key size

● Electronic Codebook (ECB)

https://www.elastic.co/products/elasticsearch

https://www.elastic.co/products/kibana

23 | P a g e


● Key portion separation for enhanced security.

● HMAC (Keyed-hash Message Authentication Code) for lookups.

APPLICATION / WEB SECURITY

Fully supported Asymmetric encryption from the chosen Java EE 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)

● Although SSL is supported, it is not recommended.

● TLS 1.1, TLS 1.2 (Transport Layer Security).

● Preferred and recommended protocol is TLS 1.2.

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.

AUDITABILITY AND TRACEABILITY

All actions in Fluid are tracked for auditability, security and traceability.

Below is a list of event and historic data kept in Fluid;

CONTENT AUDITABILITY

The Attachment Versioning ensures that existing File Types / Attachment can be easily updated, yet maintaining a history of older versions of attachments.

ELECTRONIC FORM AUDITABILITY

Each of the Fields from within a Form is Audited, along with the Business Process the Electronic Document follows.

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. This ensures the Electronic Form keeps track of what

24 | P a g e


ADMINISTRATIVE AUDITABILITY

All administrative and configuration tasks performed

USER PUNCHCARD

All User access and actions are audited, and may be reported on using the Fluid Reports.

FLUID MESSENGER

Fluid hosts an instant messenger that may be used to communicate with colleagues internally and securely.

This is ideal for when one does not want organizational instant messages to be broadcasted outside one's internal network.

SUPPORTED OPERATING SYSTEMS (SERVER SIDE)

The Fluid server side is supported by whichever Application Server is used. Most of the application servers supports the following operating systems;

● Linux

○ Fedora

○ Red Hat

○ CentOS

○ Ubuntu

○ Suse

● Windows

○ Desktop and Server Range

● Mac OS X

○ Snow Leopard and above

● Docker

○ Fluid fully supports Docker for easy and streamlined deployments

○ Although Docker is not an operating system. The recommended tried and tested

deployment for Fluid is Docker, under extension; jboss/wildfly:10.0.1.Final.

SUPPORTED BROWSERS

The listed browsers have been tested and are fully supported by Fluid (core components);

Browser Developed By Version Release Date

Chrome Google 23 and above November 2012

Internet Explorer Microsoft 9 and above March 2011

http://www.docker.com/

25 | P a g e


Firefox Mozilla Foundation 4 and above March 2011

Safari Apple 6 and above July 2012

Opera Opera Software 12 and above June 212

MOBILE BROWSER SUPPORT

The Fluid Modern Theme support makes use of the latest frameworks and standards to render an ideal outlook for mobile devices such as tablets and smartphones.

SUPPORTED DATABASE ENGINES

Fluid supports the Database engines listed below.

Although requests to support additional database engines can be made and added within weeks.

Below is a list of current supported database engines and their versions;

Database Engine Versions

MySQL (InnoDB) ● Community - 5.5.0 ≥ 5.6.20

● Standard - 5.6 ● Enterprise 5.6

MS SQL (Microsoft SQL Server) ● 2003 R2 ● 2008 ● 2008 R2 ● 2012 ● 2012 R2 ● 2016

SUPPORTED APPLICATION SERVERS

Please note that Fluid supports and recommends using Docker containers. Fluid is available from the Docker store (Docker Store).

This greatly speeds up the initial setup and configuration of Fluid.

Please note that Fluid is fully Java Enterprise Edition 7 compliant (Application Servers below are supported);

http://docker.com/

https://store.docker.com/images/6bdc6446-c6ce-4d7b-b91f-143e317c5b60?tab=description

26 | P a g e


Application Server Vendor Version

WildFly (Recommended) Red Hat 10.0.1.Final

JBoss (EAP) Enterprise Application Platform (Recommended)

Red Hat 6.3.0

WebLogic Application Server Oracle Corporation 12.1.3

Websphere Application Server IBM 8.5.5.3

GlassFish Glassfish Community 4.1

PRODUCT ROADMAP

The product roadmap for Q3 and Q4 for 2017 will include the feature set below;

IMPORT AND EXPORT OF FLOWS

Ability to import and export Field, Form, Flow, User Query and Custom Program’s as Fluid templates.

OFFICE PLUGINS

To further ease the Fluid integration into other systems a Word and Outlook plugin development is under way.

MICROSOFT POWER BI

Microsoft Power BI is currently being studied to be supported as part of Fluid’s BI offering. This would allow the “Non Elasticsearch” customers with a Business intelligence solution.

DOCKER CERTIFIED FLUID IMAGES

Fluid is currently in the process of being Docker certified (Complete in Q1 of 2017). Advantages include (Over and above the benefit of using Docker already);

Overall benefit

• Content is reviewed, trusted and real

• Ease of commercial distribution (Easy to find, purchase and update Certified containers on Store)

• Certification signals tight cooperation between Docker and Partner

• Certification gives customer confidence in consuming content

http://wildfly.org/downloads/

http://www.jboss.org/products/eap/download/

https://www.oracle.com/middleware/weblogic/index.html

http://www.ibm.com/software/websphere

https://glassfish.java.net/

https://www.docker.com/

27 | P a g e


Customer benefit

• Consume containers with confidence.

• Docker and partner stand behind container with cooperative support

• Known container provenance

• Container quality and best practices testing

Partner benefit

• Will proactively inform partner of vulnerabilities and other issues

• TSAnet used for complex issues

low level feature set for fluid - usiness management …€¦ · fluid produ t sheet low level...

Documents