fluid product sheet ‐ low level · fluid product sheet ‐ low level low level feature set for...

Fluid Product Sheet ‐ Low Level Low Level Feature Set for Fluid ‐ Business Management System ‐ June 2016

Introduction Content Management Capabilities

Database Filesystem Storage Amazon S3 Supported File Types Content Storage / Attachment Versioning

Electronic Form Capabilities User Dashboard Screenshot Electronic Form Screenshot Customized User Queries Supported Field and Data Types Electronic Form Ancestor and Descendant Capabilities Field Scopes Electronic form Retrieval Electronic Form Lookup

Spotlight Search Preconfigured User Query Search

Electronic Form Field Versioning Users & Roles (Access Control Lists)

Roles Administrative Functions Views Electronic Form Actions User Queries

Workflow Capabilities Rule Engine Rule Traceability Rule Step Types Supported Rule Engine Functions

Conditional Functions Work Distribution

Send to Colleague Case Flow Allocation

Business Process Flow Management Screenshot Integration Capabilities

Custom Program interface for Flow Steps Custom Program interface for Electronic Forms Application Programming Interface (API) Scheduled Events

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

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.

of 23


Reporting Capabilities User Punchcard Staff and System overall performance Content Storage Utilization

Security Content Security Electronic Form Field Security Application / Web Security API (Application Programming Interface) Security Authentication and Authorization

Auditability and Traceability Content Auditability Electronic Form Auditability Workflow Route Administrative Auditability User Punchcard

Fluid Messenger Supported Operating Systems (Server Side) Supported Browsers

Mobile Browser Support Supported Database Engines Supported Application Servers Product Roadmap

Data Archive Reports and Statistics Import and Export of Flows Additional Information



of 23


Introduction The following document contains the feature set of the Fluid Business Process Management suite. 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 the following;

Content Storage Web Application Access Electronic Form Access

Maintenance and Downtime Little or no downtime is necessary during system maintenance or modifications.

Please note that this does not include Fluid system upgrades if not in a clustered configuration.

User Interface The Fluid user interface is completely Web Based. Supported Browsers are listed

below. One has the ability to develop a custom frontend 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 interface for Flow Steps. Fluid Custom Program interface for Forms. Fluid Custom Scheduled tasks for scheduled or periodically executed

functions. (Such as advanced reporting) Fluid Application Programming Interface (modern JSONREST based)



of 23


Reporting User Punchcard 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 reassignment from an administrative

perspective. Configuration

Single point of entry for all configurations. The aim for Fluid is to excel in each of the Forrester identified Business Process Landscapes;

In addition to the above, a strong focus is placed on Content and Electronic Form Management. Each of the main features are listed below with a brief description of each.



of 23


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

application/pdf pdf

application/zip zip



of 23

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


application/rtf rtf

application/msword doc,dot

application/vnd.openxmlformatsofficedocument.wordprocessingml.document

docx

application/vnd.openxmlformatsofficedocument.wordprocessingml.template

dotx

application/vnd.msexcel xls

application/vnd.openxmlformatsofficedocument.spreadsheetml.sheet

xlsx

application/vnd.openxmlformatsofficedocument.spreadsheetml.template

xltx

application/vnd.mspowerpoint ppt,pps,ppa,pot

application/vnd.openxmlformatsofficedocument.presentationml.presentation

pptx

application/vnd.openxmlformatsofficedocument.presentationml.template

potx

application/vnd.openxmlformatsofficedocument.presentationml.slideshow

ppsx

audio/mpeg3 mp3

application/javaarchive jar

application/xjavaclass class

application/vnd.msoutlook msg

application/xtar tar,tar.gz

text/csv csv

Content Storage / Attachment Versioning Fluid manages file versioning internally. Every time a updated version of a file is created against a electronic form, the previous version is preserved and the newly updated version becomes the primary, still making it easy to access older file versions.



of 23


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.



of 23


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.



of 23


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



of 23


Supported Field and Data Types Fluid supports an overwhelming 17 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 characters.



of 23


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

Multiple Choice Plain or Searchable

Limit certain field data by allowing for data to be selected from a combobox.

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.

or



of 23


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

Date Time Date and Time Date field used to store dateandtime specific information.

Decimal Plain Numeric data.

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



of 23


* 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).

Electronic Form Ancestor and Descendant Capabilities Each Electronic form in Fluid has the ability to morph / evolve into a more complex Electronic form as the business process or flow progress. This is achieved by each electronic form having a single Ancestor / Parent but multiple Descendents / Children. Each of the children or parent may be involved in a separate business process.



of 23


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

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.

Electronic form Retrieval Electronic Form Lookup In order 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.

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



of 23


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.

User Queries Customized searches associated with a Role in order 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



of 23


Rule Traceability Each action carried out in the route is logged. 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.

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.



of 23


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.

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 in order to continue the business process.

Send to Colleague Send a 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.



of 23


Business Process Flow Management Screenshot

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.

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.



of 23


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.

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).

Content Storage Utilization Monitor the Current Storage and Electronic Form statistics.

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 final destination using symmetric encryption. The 256bit 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;

256Bit Key size Cipherblock Chaining (CBC)



of 23


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;

256Bit Key size Electronic Codebook (ECB) Key portion separation for enhanced security. HMAC (Keyedhash 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) 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.

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.



of 23


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

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. Ubuntu. CentOS. Red Hat. 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.0.Final.



of 23

http://www.docker.com/


Supported Browsers The listed browsers have been tested and are fully supported by Fluid;

Browser Developed By Version Release Date

Chrome Google 23 and above November 2012

Internet Explorer Microsoft 9 and above March 2011

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 iPad and iPhones.

Supported Database Engines Fluid supports the Database engines listed below. Although requests to support additional database engines can be made. Below is a list of 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



of 23


Supported Application Servers Please note that Fluid supports and recommends using Docker containers. This greatly speeds up the initial setup and configuration of Fluid. Please note that Fluid is completely Java EE 7 compliant, which means the Application Servers listed below are supported;

Application Server Vendor Version

WildFly Red Hat 9.0.2.Final

Jboss (EAP) Enterprise Application Platform 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 2016 will include the feature set below;

Data Archive The ability to store unused Electronic Form and File Content data for extended periods of time, separate from the primary storage. This refers to less frequently accessed information.

Reports and Statistics Additional advanced reporting and statistics on system from an organization operational perspective.

Import and Export of Flows Ability to import and export Flows as templates.

Additional Information For any additional information, you can contact Jason at [email protected].



of 23

http://docker.com/

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/

mailto:[email protected]

fluid product sheet ‐ low level · fluid product sheet ‐ low level low level feature set for...

Documents