Overview
Purpose
To compare Kuali Enterprise Workflow (KEW) with the current workflow functionality available via Define Internals (DI) and to determine the feasibility and benefits of implementing KEW as a core infrastructure piece for DI routing functionality.
Problem
Cleanly integrating KEW with DI workflow middleware.
Assumption
There will be minimal disruption to the current DI Workflow system.
Scope of Investigation
This is only meant to serve as an exploratory work, not a pilot or proof-of-concept. Implementation of a 'test case' is not the priority for this investigation.
Out of Scope
- Implementation of other Kuali functional modules (KFS, KRA)
- Assessment and documentation of functional integration issues beyond core workflow elements, such as details for specific functional interactions beyond document creation and routing
- Use of project findings as a sufficient basis in making enterprise-wide decisions for adopting Kuali
- Negotiations with ERP community stakeholders for implementation planning
Potential for KEW
- Increased functionality of workflow processes
- Extensible architecture model
- Standards-based workflow integration
- Community of fellow higher education developers for training and support
- Common functionality across applications
What KEW Offers the DI Workflow
- Flexibility of content-based routing
- "Abstractable" document types rather than numerous doc types with shared commonalities
- Externalization of business rules
- Support for sequential, parallel, or dynamic routing paths
- User interface standardization
- More accessible to business users and developers in terms of learning the system
- Industry-standard language/design can take full advantage of community sourcing and growth
- An integrative system architecture for the campus
Outcomes
- A better understanding of Kuali infrastructure, especially KEW
- Knowledge that replacement of DI infrastructure is feasible with further study and requirement negotiations
- A test RICE server set up and ready for further KEW development
- DI documentation focused on key integration points is underway
- A better understanding of the limits of our Java knowledge
- A sense of what is needed to move forward with this line of inquiry
Needed to Continue the Investigation
- Appropriate resources such as DEFINE and Java architecture skills
- Continued investigation on workflow integration options
- Continued investigation on integrating current authorization/authentication processes
- Functional discussions on how to integrate current business rules
- A test case within a fully functional KEW environment
- A future pilot using eDocs Lite for a non-DEFINE-based workflow process might be an ideal way to test out the RICE infrastructure while documenting integration with our environment. This would decouple the pilot from the complexity of DEFINE.
