Kuali Enterprise Workflow (KEW)
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 for auditing purposes.
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
- 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 the Document Search screens. Provides a single place for all workflow document searches.
eDocLite allows quick document building and integration with workflow using XML-based technologies and tools.
- Routing Rules
Provides a mechanism for defining routing rules which govern which entities are responsible for participating in the workflow transaction. Rule screens give functional users ability to maintain the routing rules for their business processes.
- Notes and Attachments
Notes and Attachments can be attached to documents using KEW's notes and attachments services.
- Kuali Identity Management Integration
Supports routing definitions that are based off of responsibilities defined in KIM. Principals and/or groups are attached to Roles which are given responsibilities that may require approval or acknowledgment of certain workflow transactions.
- JTA Transaction Support
All transactions and documents route in a JTA transaction. Allows for coordinated commit and rollback across multiple data sources.
- Web Service API
All system functions available through SOAP Web Service API.
Service calls can be authorized using digital signatures.
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 run as a standalone service.
- Bundled Integration Support
Web portion can be bundled 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. Great for self-contained packages of software that leverage the workflow engine.
- Service Bus Integration
Integration with the Kuali Service Bus (KSB). Various services deployed to the bus and the bus is utilized heavily for routing messages and other asynchronous functions that are performed by the workflow engine.