|
Architecture
Workflow Management
 The Visibility Layer – Executive Dashboard
The term Executive Dashboard refers to the concept of using workflows as a
standardized Global View to all automated processes. As defined, all
transactions become workflows and therefore can be evaluated in the same manner
by using workflow states as a status pointer or locater.
User Defined status and Search Pointers
The use of status pointers can be augmented with user-defined search fields and
status field data. These fields are included in the context of each individual
workflow instances and therefore available for deep search capabilities and
status.
Work Queue Visibility
Additional visibility to the Work Queue shows the status of manual activity as a
transaction is worked. The queue provides a list of current tasks, the task
groupings (internally called swim lanes), the associated user group and
assigned user, if there is one. User-defined fields are available for
visibility.
BPM Instance Monitoring
The Executive Dashboard includes real-time accumulation summaries of current
instance counts, the number of instances in each state or step, and other
information critical to resource management and problem resolution.
Master Workflow Management
Visual BPM Workflows
This layer also provides graphical view of the jBPM Workflow Masters Library.
Status can be presented graphical as a location along the process automation
workflow. Workflow Masters are editable and version managed. They can be
provided and deployed into the Workflow engine from a Process Application Suite
or a graphical editor via an XML file.
BPM Master Versioning
Versioning is maintained in the workflow engine which allows current version
flows to be completed while new instances will begin with the newer version.
Master Ownership
Master workflows are named and owned by a company and are available only to
itself. Workflows may be copied and edited, and then given a new name. If the
name remains the same, a version number is incremented and used as the new
master. Masters can be owned by a community which is available to all companies
in a community. Masters can be owned by Public which allows everyone access.
Any master or version level can be selected as the default flow for a suite
Automation Process transaction. Suites can define and deploy as many workflows
as required. Master workflows and any associated actions from within any suite
are available to other suites within the same company restraints.
BPM History Logs
History Logs
Internal logs are included to status process automation via workflow actions
such as instance creation, state changes of each step taken, and user
assignments. All log entries include timestamps of each event. Log history
detail can be combined with current status and counts to produce unequaled
management visibility.
External Monitor
All the same status data is available to any external monitor via the Workflow
Application Bus Interface including user-defined fields and history.
|
