| Section | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Excerpt |
|---|
The Kuali Enterprise Workflow (KEW) is a general-purpose, content-based electronic routing infrastructure or workflow engine. Its main purpose is to automate the routing of electronic documents (e-docs) to individuals and groups for approval, yet the KEW can also be used to orchestrate complex processes between business components and applications. Approval routing is based on institutional or departmental business rules and policies. A new routing option called PeopleFlow is also available from the KEW to provide a streamlined way to view and update routing actions. This section provides an overview of KEW as it relates to the OLE. |
...
KFS Knowledge Transfer - KIM functions (roles permissions, responsibilities) was a video conference about roles and workflows. It also contains a visual demonstration about responsibilities.
PeopleFlow Overview
PeopleFlow is a new Kuali Rice feature that Kuali OLE is now using for License Requests and Electronic Resources. PeopleFlows are a prioritized list of people to send requests to. Essentially, it's like a mini people-based workflow that doesn't require you to specify a KEW node in the document type for each individual who might need to approve or be notified. You can define "Stops" in a PeopleFlow, where everything in the same stop proceeds in parallel, but all must be done within the stop before proceeding to the next stop.
You can call/execute a PeopleFlow from within a KEW workflow node directly, or you can invoke the Kuali Rules Management System (KRMS - a common rules engine for defining decision logic, commonly refereed to as business rules) engine from an application and any PeopleFlows that get selected during rule execution, defined in a KRMS agenda, will be called. In this way, you can integrate business rules across applications and workflows.
The same PeopleFlow that defines a routing order among a set of persons, groups or roles can be called by KRMS rules, with the KRMS rules defining which type of request to pass to the PeopleFlow (for example, an "approval" routing action or a "notification").
For information about creating and managing PeopleFlows in OLE, see in the Guide to OLE System Administration Functions.
| Anchor | ||||
|---|---|---|---|---|
|
...