Page History

...

• Documented processes. To define a workflow, a developer typically must have access to business process documentation such as an activity diagram and details on each process step such as inputs, outputs, and roles.
• Defined roles. To execute a workflow, business users typically must be placed in roles that are authorized to execute workflow steps.
• Organizational model. Roles fit into an organizational hierarchy, which is used to determine who has authority to monitor workflows and override decisions.
• Adherence to process. A workflow defined to support a documented business process is only effective if the business process is actually carried out as documented. Otherwise, the workflow solution will be a barrier to "how we really do things."

...

• Enterprise authorization. As the workflow system integrates with more other system, there is increased pressure to centrally manage groups and roles for consistent authorization across systems -- both for security and for efficient provisioning. (Conceptually, the enterprise authorization problem exists even for business processes that aren't in any workflow solution, but it's brought to the fore by enterprise workflow.)
• Integration of systems. As the workflow system integrates with more other systems, more resources are required to carry out integration, messaging, orchestration, etc. If the workflow system acts as a "hub" among systems, this progression may be linear, but if there is a "web" of interactions between services, it may not.