...
Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
...
- Perform lookups/inquiries within a lightbox/iframe that pops up over the document
- Open documents or route log from action list or document search in a lightbox
- Add support for some transactional document layouts without using JSPs.
KRAD makes data dictionary change such as adding lookup constraints and custom constraints. Overall, KRAD will enhance OLE UI capabilities.
For more about KRAD, see Rice KRAD analysis
KRMS
The other important component in Rice 2.0 is Kuali Rule Management System (KRMS). KRMS is a rule engine for defining decision logic, commonly referred to as business rules. KRMS facilitates the creation and maintenance of rules outside of an application for rapid update and flexible implementation that can be shared across applications. KRMS provides OLE the opportunity to build its own flexible and easily managed business rule system.
For more about KRMS, see the KRMS and PeopleFlow Overview
...
How OLE is affected
...
Based on the above Rice 2.0 features, obviously, moving OLE to Rice 2.0 framework is what we should go for. However, Kuali OLE's current version is bundled with KFS, which utilizes Rice 1.x. Since Rice 2.0 was formally released on Feb 24th, 2012, it was impossible for KFS (Kuali Financial System) to upgrade to Rice 2.0 before OLE 0.6 release. It is not realistic to abandon KFS and one-year's worth of implementation based on that and to rebuild our own financial system for OLE. So for the OLE 0.6 release we set up two servers, one for OLE with KFS/Rice1.x to keep our financial functions and one for OLE on Rice2.0 to try the new features and see what kind of benefits it can bring for OLE. Since Rice 1.x can not talk with Rice 2.0 through the KSB (Kuali Service Bus), therefore, the communication between two servers geso through SOAP services like this simple drawing for the architecture.
...