1 / 47

KRA Workflow

KRA Workflow. Dan Dwyer Cornell University Bryan Hutchinson Cornell University Lisa Oliva Michigan State University. Agenda. KRA Proposal Routing Requirements KRA Workflow Technical Overview KRA Proposal Routing Implementation. KRA Proposal Routing Requirements.

hannaphillips
Télécharger la présentation

KRA 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. KRA Workflow Dan Dwyer Cornell University Bryan Hutchinson Cornell University Lisa Oliva Michigan State University

  2. Agenda KRA Proposal Routing Requirements KRA Workflow Technical Overview KRA Proposal Routing Implementation

  3. KRA Proposal Routing Requirements

  4. KRA Proposal Routing Requirements Proposals are routed for: • Researcher certifications • Department and college approvals • Special reviews • Delivery to sponsored programs office

  5. Proposal Routing Challenges • Multiple department approval due to collaboration or joint appointment • Variability in rules by unit, sponsor or type • Time constraints due to hard deadlines • Who does rejected proposal return to? • What data can change without re-routing? • Workgroup coverage and proxy approvals at many steps

  6. KRA Workflow Analysis • Develop use case that represents most common scenarios • Check use case among partner institutions • Test multiple scenarios during QA • Recognition that implementing institutions will modify according to local needs – configurability is critical

  7. Workflow Use Case

  8. Workflow Use Case - Initiation

  9. Workflow Use Case - Researcher

  10. Workflow Use Case - Department

  11. Workflow Use Case - College

  12. Workflow Use Case - Completion

  13. Workflow Requirements for Compliance Protocols • Generally simpler routing rules the proposal routing • Interest in routing for some special reviews prior to or in parallel to routing to compliance office • Routing for review may involve some confidentiality issues not found with proposals

  14. KRA Workflow Technical Overview

  15. KRA Workflow Technical Overview • Kuali Enterprise Workflow (KEW) Overview • KEW Configuration • Coeus/KRA Workflow Functionality and Gaps

  16. Kuali Enterprise Workflow Overview • One of the components of Kuali Rice • Rice is Kuali based enterprise class middleware which enables Rapid Application Development • Provides consistent Workflow functionality across your applications

  17. Kuali Enterprise Workflow Overview • Workflow as a Service • Rules • Actions (Approval, Acknowledgement, FYI) • Workgroups • Integrated into KNS Documents • Accessible from existing applications • Embedded/External • Action List • Document Search • Route Log

  18. Action List

  19. Document Search

  20. Route Log

  21. Kuali Enterprise Workflow Overview • KEW Allows KRA to: • Submit a Proposal Development Document a pre-configured set of users for approval • Give approvers the ability to route the Proposal to users for approval who aren’t in the approval chain on an adhoc basis • Track where a Proposal is in the approval process • Give Investigators the ability to approve or disapprove a Proposal, or return it to the PI for modification

  22. KEW Configuration • Primarily XML • Rules can be maintained through the KEW GUI • Requires technical expertise • Defines KEW Configuration Components: Document Type, Route Nodes, Route Templates, Routing Attributes, Searchable Attributes, Rules

  23. Document Type <documentType> <name>ProposalDevelopmentDocument</name> <description>Create an Awesome Development Proposal</description> <label>KRA Proposal Development</label> <postProcessorName>org.kuali.workflow.postprocessor.KualiPostProcessor</postProcessorName> <superUserWorkgroupName>WorkflowAdmin</superUserWorkgroupName> <blanketApproveWorkgroupName>WorkflowAdmin</blanketApproveWorkgroupName> <defaultExceptionWorkgroupName>WorkflowAdmin</defaultExceptionWorkgroupName> <docHandler>${kuali.docHandler.url.prefix}/proposalDevelopmentProposal.do?methodToCall=docHandler</docHandler> <active>true</active> <attributes> <attribute> <name>AggregatorSearchAttribute</name> </attribute> … </attributes> <routingVersion>2</routingVersion> <routePaths> <routePath> <start name="Initiated" nextNode="OSPInitial" /> <requests name="OSPInitial" nextNode="ProposalPersons" /> <requests name="ProposalPersons" nextNode="UnitRouting" /> <requests name="UnitRouting" nextNode="OSPOfficeRouting" /> <requests name="OSPOfficeRouting" /> </routePath> </routePaths>

  24. Document Type <routeNodes> <start name="Initiated"> <activationType>P</activationType> <mandatoryRoute>false</mandatoryRoute> <finalApproval>false</finalApproval> </start> <requests name="OSPInitial"> <activationType>S</activationType> <ruleTemplate>OSPInitialApproval</ruleTemplate> <mandatoryRoute>false</mandatoryRoute> <finalApproval>false</finalApproval> </requests> <requests name="ProposalPersons"> <activationType>P</activationType> <ruleTemplate>ProposalPersonsApproval</ruleTemplate> … </requests> <requests name="UnitRouting"> <activationType>P</activationType> <ruleTemplate>CustomApproval</ruleTemplate> … </requests> <requests name="OSPOfficeRouting"> <activationType>S</activationType> <ruleTemplate>OSPOfficeApproval</ruleTemplate> … </requests> </routeNodes> </documentType>

  25. Rule Attribute <ruleAttribute> <name>ProposalPersonRoleAttribute</name> <className> org.kuali.kra.workflow.ProposalPersonRoleAttribute </className> <label>Proposal Routing</label> <description>Proposal Routing</description> <type>RuleAttribute</type> </ruleAttribute>

  26. Search Attribute <ruleAttribute> <name>BudgetCreatorSearchAttribute</name> <className>edu.iu.uis.eden.docsearch.xml.StandardGenericXMLSearchableAttribute</className> <label>BudgetCreatorSearchAttribute</label> <description>BudgetCreatorSearchAttribute</description> <type>SearchableXmlAttribute</type> <searchingConfig> <fieldDef name="budgetCreator" title="Budget Creator"> <display> <type>text</type> </display> <quickfinder service="UserLookupableImplService" appliesTo="networkId" draw="true" /> <fieldEvaluation> <xpathexpression>//users/budgetCreator/value</xpathexpression> </fieldEvaluation> </fieldDef> <xmlSearchContent> <users> <budgetCreator> <value>%budgetCreator%</value> </budgetCreator> </users> </xmlSearchContent> </searchingConfig> </ruleAttribute>

  27. Document Search with Search Attributes

  28. Rule Template <ruleTemplate allowOverwrite="true"> <name>OSPInitialApproval</name> <description>OSP Initial Approval Routing Rule</description> </ruleTemplate> <ruleTemplate allowOverwrite="true"> <name>ProposalPersonsApproval</name> <description>ProposalPersons Approval Routing Rule</description> <attributes> <attribute> <name>ProposalPersonRoleAttribute</name> <required>false</required> </attribute> </attributes> </ruleTemplate>

  29. Workgroup Rule <rule> <documentType>ProposalDevelopmentDocument</documentType> <ruleTemplate>OSPInitialApproval</ruleTemplate> <description>OSP Initial Approval</description> <ignorePrevious>true</ignorePrevious> <responsibilities> <responsibility> <workgroup>WorkflowAdmin</workgroup> <approvePolicy>A</approvePolicy> <actionRequested>A</actionRequested> <priority>1</priority> </responsibility> </responsibilities> </rule>

  30. Role Rule <rule> <documentType>ProposalDevelopmentDocument</documentType> <ruleTemplate>ProposalPersonsApproval</ruleTemplate> <description>ProposalPersons Approval</description> <ignorePrevious>true</ignorePrevious> <responsibilities> <responsibility> <role>org.kuali.kra.workflow.ProposalPersonRoleAttribute!PROPOSALINVESTIGATOR</role> <approvePolicy>A</approvePolicy> <actionRequested>A</actionRequested> <priority>1</priority> </responsibility> </responsibilities> </rule>

  31. Workgroup Rule - GUI

  32. Coeus/KRA Workflow Functionality and Gaps • KRA/Coeus Gap Analysis Spring 2007 • Functional and Technical • Coeus Workflow configuration is significantly different than the KEW configuration we were starting with • There were also some areas of Coeus Workflow functionality that KEW couldn’t provide

  33. Coeus/KRA Workflow Functionality and Gaps • Filled Gaps • Configuration - Meta-Rules, Rules and Conditions • Multiple Approvals • Inbox (Action List) - View Resolved • Gaps for KRA Release 2.0 • Workflow Configuration through GUI • Other potential Workflow Use Cases • More dynamic Actions/Statuses • Multiple documents tied together

  34. KRA Proposal Routing Implementation

  35. Data Validation

  36. Adhoc Recipients

  37. Submit!

  38. Route Log

  39. Status: Enroute

  40. Workflow Action List

  41. Select Document #2222

  42. Action: Approve

  43. Action List

  44. Action: Disapprove

  45. Outbox: Approved & Disapproved Documents

  46. For Further Information • https://test.kuali.org/confluence/display/KULRICE/Documentation • Rice (including KEW) Documentation • https://test.kuali.org/confluence/display/KRADOC/Home • KRA Documentation • Contacts • Dan Dwyer - djd1@cornell.edu • Bryan Hutchinson - bh79@cornell.edu • Lisa Oliva - malonel@ais.msu.edu

  47. Questions?

More Related