1 / 17

Kuali Enterprise Workflow

Kuali Enterprise Workflow. Ryan Kirkendall (Indiana University) Brian McGough (Indiana University). KEW Core features. User Work Queue (Action List) Document Searching Document Audit Trail (Route Log) Flexible process definition

dawn
Download Presentation

Kuali Enterprise Workflow

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Kuali Enterprise Workflow Ryan Kirkendall (Indiana University) Brian McGough (Indiana University)

  2. KEW Core features • User Work Queue (Action List) • Document Searching • Document Audit Trail (Route Log) • Flexible process definition • Splits, Joins, Parallel branches, Sub processes, Dynamic process generation • Basic User and Group support • Can be overridden and customizable to plug into Institutional user and groups solutions • Business Rules • Email Notification

  3. KEW Core features • Notes with attachments • Wide array of pluggable components to customize routing by process • Where to route document • Indexing of document data for searching • Email Notification Customization • Customization of Action List • Customization of Business Rules • EDocLite • Framework for creating simple documents quickly

  4. KEW Core features • Client APIs available through web services • Programmed against open standards that allow KEW to run in any J2EE appserver • No stack buy in • Can run in Servlet Container • Can use JTOM JTA to participate in JTA transactions in non-J2EE environment • All processing is transactional

  5. Supports Agile Business process • Runtime changing of business process • Upload of process definition • Changing of business rules • Re-resolution of Roles • Re-resolution of Workgroup(s) • Re-deployment of routing components

  6. Upload of process definition • XML Defined process • Who to route to • What business rules/roles to use during routing • What code/XML to use to during routing • How to contact client application during routing • How to index business data during routing • Determines how documents route • Can be changed at runtime • When changed, all new documents follow new process • Currently routing document follow old process definition

  7. Changing of Business Rules & Roles • KEW Supports Business rules out of the box • Written by programmers • For use by functional users • Reusable across processes within Institution • When Business rules change all documents affected by those rules reflect the change • Documents are re-evaluated against the new rule data • Roles routed to can be dynamically re-resolved at the request of applications • All routing documents reflect the change

  8. Re-resolving Workgroups • All routing documents are dynamically re-resolved that are affected by the change • Action List (Work Queue) of new and removed members updated • Notifications of document arrival sent to new members based on notification preferences

  9. Re-deploying routing components • Components that interact with workflow engine to determine documents’ routing defined in XML and Java • XML can be uploaded to change process at runtime • Java components live in ‘Plugin’ space that is a self contained environment for application and institutional code • Plugins can be hot deployed at runtime • Changes to one application’s components do not impact the entire Institution

  10. Re-deploying routing components • Processes defined to use the newly deployed components will immediately change to the new definitions

  11. Head-to-Head Comparison • Head-to-HeadComparison of KEW to OSWorkflow and JBoss jBPM • Done using documentation provided with each product. These are all flexible open source projects that can conceivably do ANYTHING with enough work. We are looking for concerns specifically addressed in the documentation - not possibilities.

  12. Head-to-Head Comparison

  13. Head-to-Head Comparison

  14. KEW = Workflow fast • Designed with people based processes in mind from the beginning • Many of the hard parts solved • Work Queue • Audit Trail (this is big) • Searching • Decentralized process management through business rules, workgroups, and delegation • Simpler configuration than many workflow solutions

  15. KEW = Workflow fast • No stack buy in • Run in servlet container of your choice • Web service interfaces for non java clients • XML components for processes without java • EDocLite for fast and easy routing without investment in new applications • XML based routing content and flexibility of configuration make integrating existing application into routing easy.

  16. Future Enhancements • Embedding workflow directly in application • No need to contact workflow as a remotely available service in applications • Service Bus at core of workflow • All clients running embedded workflow can publish and consume services from the bus • Services Published on bus can participate in processes defined in workflow • All Services can be called Synchronously or Asynchronously

  17. Future Enhancements • JMX • KEW Managed by JMX • Client applications can publish MBeans over the bus • Client JVMs can be monitored via JConsole or KEW GUI • Improved overriding of KEW Services by implementing institutions

More Related