| 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. |
...
OLE Workflow relies on Kuali Identity Management (KIM) to specify when workflow action requests are to be generated and who should take action to fulfill them. Functional users employ the KIM interfaces to make changes that affect the routing of documents.
KFS Knowledge Transfer - KIM functions (roles permissions, responsibilities) was a video conference about roles and workflows. It also contains a visual demonstration about responsibilities.to make changes that affect the routing of documents.
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 | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
The In financial e-docs, the error correction action allows you to correct documents by creating a new document that reverses the original transaction that has been fully approved. A document created with the error correction action must route and be approved in the same manner as the e-doc it corrects.
...
- Click
.
The system creates a new document with a new document ID. The system also displays Corrects Document ID in both the document header and the Notes and Attachment tab of the document.
Amounts are in negative to reverse the original transaction.
The new document has an annotation that is an error correction.
- Click submit.
The header of the corrected document shows the corrected by document ID.
...
Color changes do not take place until the next time you log onto the system. The row colors change the next time you log on.
| Anchor | ||||
|---|---|---|---|---|
|
...