Financial Management

TUI University

Joseph A Ireland

4 MAR 2012

Case Module 3

Instructor: Dr. Craig Schreiber

The biggest thing I can appreciate about Kuali Enterprise Workflow (KEW) is the thought of a world or

in my case organization without paper flow everywhere. No more forms to fill out and route to the

proper place, the chance of lost or misplaced documents which I have experienced constantly being in the

military, which seems to be a paper document driven organization and although it seems to be getting

better it stills has a long way to go to catch up with the rest of the corporate world. I think the biggest

thing I really could relate to and it has recently been implemented into the Navy and the way that leave

requests are submitted and approved is a stand- alone engine upon which you can integrate other

enterprise application to do routing and approval. We have a system very similar to this which we call E-

leave. For example, a Leave Request document would include a request from Joseph Ireland to take a

week off in March. The document would contain within itself enough information to make the decision

(may use data keys in the document to retrieve other external information). The document would then

route to the person's supervisor for approval, and so forth, depending on how the department has these

processes configured. Once the document is fully approved, it will trigger a post-processor, which can be

any action taken as a result of the document completing.

In addition, the E-Leave request contains hooks for all the stages that a document goes through, such that

an external application using workflow for routing and approval can take necessary actions on each

change in state of the document. So you can say with this leave example E-leave is very similar if not

identical to KEW. There are many features with KEW and I will try and briefly explain the features and

processes and what they accomplish.

The first thing would be the:...