Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kuali Coeus KEW Functional Training


Published on

Session 1 will be functionally-focused; we will review the key features of KEW, including the action list, route log, and document search; walk through the default workflows provided out of the box for the KC modules; and demonstrate some basic configuration that can be done using the administrative screens.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Kuali Coeus KEW Functional Training

  1. 1. Kuali CoeusWorkflow and KIM - Part 1
  2. 2. Workflow - What/Why!  Model or improve existing business processes!  Automate repetitive, manual tasks!  Work efficiently, collaboratively!  Measure performance, gather metrics
  3. 3. About Kuali Enterprise Workflow (KEW)!  Component of Kuali Rice middleware!  Mature - Production at Indiana University 2003!  Integrated Action List/Document Search !  Flexible !  Integration modes - Embedded, Bundled, Remote !  Rules processing !  Content based routing !  eDoc Lite
  4. 4. Kuali Enterprise Workflow (KEW)" Concepts!  Document types!  Document Policies (behaviors)!  Route Nodes!  Rules/Rule Templates!  Workgroups/Groups
  5. 5. KEW Concepts-Document Type XML!  Define behavior of a routable document !  KC Prop Dev Document!  Document Type Hierarchy - Inherited Behavior !  KC Maint Docs all have a common ancestor!  Post Processor - Client code that executes as the document routes !  KC uses the KNS provided Post Processor!  Doc Handler - Tells KEW how to find your Documents!  Default Workgroups - Super User, Exception (can also be defined in KIM)!  Document Policies - Initiator must route/save; Route Log Look Future!  Custom Doc Search Attributes
  6. 6. KEW Concepts-Route Nodes Defines the route path of a document!  Can be simple Can be simple: !  Or Complex
  7. 7. KEW Concepts-Rules!  One way to tell a document where to go and how to get there!  Rules Templates define the evaluation criteria for a rule !  Ex. Doc Type Foo will route based on Units!  Rule Attributes - Define how to evaluate Document content; Java or XML !  Tells KEW where to find Unit data on the Foo Doc!  Rules Matches document content to evaluation criteria !  If Unit = Chemistry, Sally must approve!  After the Rule Template and Rules Attributes are created, Rules can be created and managed using a GUI (i.e., no code)
  8. 8. KEW Concepts-KIM Roles!  KIM - Kuali Identity Management; Another Rice module!  Roles - Used for Authorization; Bundles of Permissions!  Roles can be “qualified” with business data to limit their scope !  KC mainly uses Unit/Unit Hierarchy Qualified Roles!  Roles can be maintained or derived !  KC - Derived Roles for PI, Co-I, Key People
  9. 9. KEW Concepts-KIM Responsibilities!  Responsibilities - Used to build workflows instead of Rules !  KC - PI has an Approve Responsibility!  Uses Qualifiers to define Rule Attributes!  Granted to Roles, not people/groups !  KC - PI is a derived Role !  KC - OSP Approver is a Maintained Role
  10. 10. KEW Concepts-Document Content!  Rule Attributes Define Route Nodes !  Java - Code execution !  XML/XPath - KNS uses XMLStream to generate XML representations of documents; XPath queries this XML to make routing decisions!  Document Post Processing !  When workflow doc changes state, code executes in the client system !  KC - Change Prop Dev Status
  11. 11. KEW - User facing components !  All Documents !  Have a Route Log !  Show in Doc Search !  Users !  Have an Action List !  Can set Action List Preferences !  Interact with individual Documents
  12. 12. Route Log
  13. 13. Doc Search
  14. 14. Action List
  15. 15. Outbox
  16. 16. Kuali Coeus - Out of thebox
  17. 17. KC - Classes of Documents•  Transactional Documents!  Business transactions!  Non-Admin users!  Most likely to have workflows•  Maintenance Documents!  Reference Data!  Admin users!  No “out-of-the-box” workflows; Unlikely to have workflows
  18. 18. KC - Examples of Documents•  Ex. Transactional Docs Ex. Maintenance Docs!  Proposal Dev Doc ! Sponsor  !  Prop Budget ! Rolodex  !  Award ! Special   Review Type!  Protocol ! Valid   Cost Element Rate
  19. 19. KC - Maintenance Docs!  Leverage the Kuali Nervous System (KNS) Maint Doc Framework!  Similar to Coeus’ Code Tables!  Group Based authorizations (AuthZ) restrict access!  KEW routes to the same Group that authorizes access!  Approval is implicit when AuthZ user submits (or blanket approves) Maint Doc !  KcAdmin Group
  20. 20. KC Transactional DocsKC Module Out of the box workflowProp Dev POCProp Budget None (Coeus FE)Inst Prop None (Coeus FE)Award None (Coeus FE)Award T&M None (Coeus FE)Award Budget Award Budget ApprovalIRB Protocol Dept Review, IRB ReviewIRB Online Review Init, IRB Admin 1, IRB Online Review, IRB Admin 2
  21. 21. KC - Proposal Development Document!  Proof of concept workflow demonstrates concepts/capabilities1.  Split Node to handle KC Proposal Hierarchies (Only the parent routes, gets submitted) Required for Prop Hierarchy functionality2.  Feedback loop between OSPInitial and ProposalPersons (PI, Co-I, Key People)3.  Unit Routing !  POC routing based on Custom Data4.  Departmental Routing !  Lead Unit/Lead Unit Hierarchy Routing5.  OSP Approval/Submission6.  Join Node - Required for Prop Hierarchy
  22. 22. KC - Proposal Development Document
  23. 23. KC - Custom Workflow Next Steps!  Understand KC data!  Define desired business process !  Don’t build in current process work-arounds!  Define business rules !  Simple or complex
  24. 24. KC - Future!  KC 3.1 - Released in July 2011!  KC 3.2 - Late Summer 2011; Rice 2.0!  KC 4.0 - Fall 2011!  KC 5.0 - Spring 2012
  25. 25. Custom Doc Search Attributes