Why Use KEW?
Provides a single action list for the constituents of the organization to
see work that requires their attention
Establishes a configurable way for service providers to define their
processes, allowing them to alter those processes over time to reflect
organizational change
Promotes transparency of processes to the institution so that people can
seamlessly see the status, actors, and the history of any institutional
process which leverages KEW as its workflow engine
What is KEW?
Kuali Enterprise Workflow provides a common routing and approval engine that
facilitates the automation of electronic processes across the enterprise.
The workflow product was built by and for higher education, so it is
particularly well suited to route mediated transactions across departmental
boundaries. Workflow facilitates distribution of processes out into the
organizations to eliminate paper processes and shadow feeder systems. In
addition to facilitating routing and approval workflow can also automate
process to process related flows. Each process instance is assigned a
unique identifier that is global across the organization. Workflow keeps a
permanent record of all processes and their participants.
KEW Documentation
Documentation is available for each release.
KEW Features
Flexible Workflow Engine - Support for sequential, parallel and dynamic routing paths. Extensible architecture allows for easy customization.
Content-Based Routing - Routing decisions can be made based on XML document content. XPath and other XML tools can be used to determine routing without writing code.
Pluggable Components - Components can be deployed to the system at runtime using Plugins. Hot deployable class loading space provides robust enterprise ready deployment environment for workflow code.
People in the Routing Process - Documents can be routed to individuals, workgroups or roles.
Action List - Displays a list of each user's pending items which require his/her attention, such as documents which are awaiting approval. Users can configure, whether they receive emails when the document enters their Action List.
Document Search and Route Log - Allows users to search for documents and see an audit trail of what has happened to the document during its life cycle.
Document Search Customization - Document based content can be associated with workflow data and searched on using our Document Search screens. Have a single place for all of your workflow document searches.
EDocLite - EDocLite allows quick document building and integration with workflow using only XML.
Rules System - Provides a mechanism for defining business rules which govern how a document routes. Rule screens give functional users ability to maintain the business rules for their applications. Documents affected by rule changes are re-routed real time.
Notes and Attachments - Notes and Attachments can be attached to documents using KEW's notes and attachments services out of the box. Institution based attachment and note services can be used by overriding our default services.
User Services - Maintains users of the system, available Out-of-the-Box or override with your institution's user services.
Workgroup Services - Maintains groups of users, available Out-of-the-Box or override with your institution's workgroup services.
Transactions - All transactions and documents route in a JTA transaction.
Web Service API - All system functions available through Web Service API.
Security - Web service calls can be authorized using digital signatures.
Scalability - Can be clustered and run on multiple machines to allow for horizontal scalability.
Embeddable Engine - Workflow engine can be embedded in an application as well as ran as a standalone service.
Embeddable Web Application - Web portion can be embedded in an application as a Struts module. Run the Action List, Document Search, Route Log, Rules System and more from within your application with minimal effort.
Service Bus Integration - Integration with the Kuali Service Bus (KSB). Override any service from within workflow by having workflow grab the service from the bus or use workflow's pluggable components to deploy bus enabled services.
JMX Support - A set of management functions are exposed through JMX.
Spring Based Integration - KEW is designed with Spring based integration in mind.
