You can use FLOWer as the backbone for your whole IT infrastructure. For example the user may just see one screen but the data populating the fields has been drawn from several databases from other applications.
FLOWer has already proved its added value in a modern Service Oriented Architecture (SOA). By using FLOWer in a SOA, it is easy to call various services from within the system. These calls can take place synchronously (the process waits for a reply from the service and only then continues) or asynchronously (the process does not wait for a reply). Calling the appropriate services is done through the “Enterprise Backbone” (EB). All services are connected to this EB so they do not need to be integrated independently.
All messages comply with a default protocol, such as XML/Soap which enables seamless communication through the EB.
FLOWer in the Application Architecture
Application architecture usually consists of several default components. In addition to FLOWer these can consist of:- folder and document management
- record management
- digitalisation of paper documents
- connecting third parties (chain partners) through the web
- receiving, recognising and assigning incoming e-mail
- automatically generating documents and outgoing electronic messages based on templates
- Central management of all relation and contact data
- Business intelligence
FLOWer as a Proven Enterprise Application Integration (EAI) Framework
To make the most of process automation it is essential that different systems are integrated with FLOWer. The processing of unstructured mail using process support has often been applied successfully. Integration with scanning, mail and fax applications are more often the rule than the exception in environments that use FLOWer. Also the so-called ‘primary’ or ‘legacy’ systems have been linked successfully to process transactions within FLOWer. Examples of such systems are:- ERP systems
- UWVs registration applications
- Mortgage and credit systems
- EDRMS software