By using FileNet® P8 Process
Designer, you can associate complex business rules with various routes
between workflow steps.
Workflow definitions
By creating a workflow definition, you can define the activities
and resources that are required to accomplish a business process. A
workflow definition consists of a series of process steps that are
connected together by a series of routes, which define the sequence
in which the steps are executed.
Workflow version management
Defined processes are stored in an object store. Storing
the definitions in an object store provides a mechanism for managing
the lifecycle of the workflow definition by controlling user access
and managing different versions of the same workflow.
Workflow submaps
Workflow definitions can be developed by using a collection
of nested subprocesses, or submaps. Submaps can be defined in Process
Designer and are inherited from the base work class of the workflow
definition.
Workflow inheritance
To establish consistent processing and expedite creation
of workflow definitions across a group of related processes, a workflow
author can create workflow definitions that inherit the characteristics
and properties of previously defined workflow definitions.
Workflow steps
The steps in a workflow represent either a specific business
task or a system activity. A business task can be performed by an
individual user, by a group of users, or by an automated application.
Parallel work and routing
Routing defines the order of execution for a series of
steps, which can be based on specific rules and events. Except for
the last step on the map, every step has one or more routes that lead
from it. You can define a route so that it is always taken or is taken
only if a predefined condition is met. Workflow steps can occur in
parallel to facilitate more efficient processes.
Vote-based routing
In many cases, a single task can require action by a number
of users collectively. These users can be identified explicitly or
implicitly by using workflow groups.
Work prioritization
By default, tasks are processed in the order in which they
are received. You can modify the processing order based on any data
field that is associated with the workflow process, such as a required
service level.
Deadlines and timers
You can use deadlines and timers to further ensure that
work is processed in a timely manner. A deadline provides a time-based
scheduling constraint, which requires that a step or workflow be completed
within a certain amount of time. The deadline can be relative to the
time the step was routed to the participant or to the time the workflow
was launched. An expression builder defines a time expression for
the deadline.
Interrelated processes
In any business process management solution, not only can
individual processes be complex, but processes can also be programmed
to interact with each other. Interaction facilitates the implementation
of processes that cut across the internal and external boundaries
of an organization.
Event-based workflow launching
Workflows can be automatically launched when objects in
an object store change. For example, if a new customer object is created,
a workflow that manages new customer acquisition can be automatically launched.
Graphical process design
You can use Process Designer to
easily create a workflow definition through a graphical user interface.