FlowRunner - Integration |
|
The ability to integrate corporate
data from disperse systems and
technologies is a major challenge. A successful data
integration solution is a subset of
a business process integration
problem domain. In addition to
workflows that span human activities
FlowRunner is capable of
straight-thought processing (STP).
A FlowRunner hosted business process
may be triggered by an external
system. For example, a form may be
scanned, recognized, and
automatically exported into
FlowRunner as a process instance.
|
One of FlowRunner's most unique
features is its extensibility model.
The unique component-based workflow
engine can be extended with simple,
light-weight components that
interface with other systems and
technologies. These components can
be designed, configured, and
debugged separately to become available to a
business process designer. Simply
put, once designed and tested they
will show as icons on the toolbar to
be dragged onto a palette.
Custom steps functionality
provides both design and run-time support. A custom step may
have a configuration page, on
which a process designer would
set or map process data fields
to custom step properties. An
example of such custom step is a
mail step. A mail step is
a custom component that offers
the functionality to send email
to specified recipients. The step's
configuration page lets a
process designer specify step
input parameters by mapping them
to process data fields.
- Custom steps may have an
optional configuration page
(static HTML) at design time
- Custom steps can read or alter process
data at run time
- Custom steps can influence the
execution of a process by
providing a return code that may
be used conditional
branching
- All process instance data
modifications are
auditable
up to individual field values
- All process instance data
modification are indexed to be
later used for
searching
- A custom step may be executed
at design time by a simple
keystroke or during a
simulation session in
FlowRunner Designer
- Custom steps can have their
own icons on the toolbar
- When dropped onto a palette
custom steps may have their own
image representation
- Custom steps can interact with
a variety of technologies summarized
below
|
|
Technology |
Solution |
Platform |
|
COM |
VBScript |
Microsoft
Windows Native |
|
COM |
JavaScript |
Microsoft
Windows Native |
|
Java |
JavaScript |
Java Virtual
Machine |
|
Java |
Java Component
(JAR) |
Java Virtual
Machine |
|
Web Services |
VBScript,
JavaScript, JAR |
Any |
Picking a technology is a simple
configuration option. Microsoft
Windows® adapter is part of the base
installation.
|
 |
|
This set of supported solutions
provides an excellent platform/technology
interoperability. A single
FlowRunner installation can execute
custom steps native to different
technologies. For example, one step can be a
VBScript calling a COM component,
and the next step can be a Java
component issuing database calls via JDBC.
For organizations with multiple
technologies in place FlowRunner
provides a superb integration
platform for maximum reuse of
existing resources. |
 |
 |
Pure XML Platform
FlowRunner has been architected
as true J2EE, pure XML business
process management platform.
There are no proprietary binary
formats, no legacy interoperability
layers or any other
overhead processing. Everything
is XML. Period.
If the target application
supports XML the integration
process should be a breeze.
-
All data FlowRunner operates
on is in XML format
-
All process definition maps
are in XML format
-
All task addressee routing
information is in XML format
-
All form data is in XML
format. Adobe PDF forms are
generated based on internal
XML format
-
All
brandable
user interface items are in XML
format
-
All generated schema
definitions are in XML format
-
All web services calls are in
XML format
-
All configurations are
in XML format
|
Next section:
Branding »
|
Want to evaluate our software? Complete the information request form.
