Kuali Rice 2.2.2-SNAPSHOT Release Notes

Released: 03-28-2013


Table of Contents

Overview
Release Highlights
Download
Documentation
Contact
Upgrade Guide: Rice 2.2.1 to Rice 2.2.2-SNAPSHOT
Upgrading the database
Items Addressed in Rice 2.2.2-SNAPSHOT
Bug Fix
Improvement
Task
Impacting Changes
Reduce the size of KRAD_MSG_T.LOC column

Overview

Welcome to Rice 2.2.2-SNAPSHOT!

Release Highlights

This version of Rice includes many improvements to the Kuali Rapid Application Development (KRAD) Framework. Below is a summary of the larger new features and you can learn more about them in the KRAD Guide which is also now publicly available with this release. Also review the Jira list at the end of this document to see the smaller items.

Highlights of this release include:

  • Numerous bug fixes in support of Kuali applications
  • Documentation updates

Download

Kuali Rice 2.2.2-SNAPSHOT can be downloaded from the Rice website at http://kuali.org/rice/download.

There are three different distributions of Rice available: source, binary and server. Please read the Installation Guide for more details on each of these distributions.

Applications can also consume Rice from the maven site at http://search.maven.org/#search|ga|1|org.kuali.rice.

Documentation

API Documentation can be found at http://site.kuali.org/rice/2.2.2-SNAPSHOT/apidocs/index.html

Formal documentation can be found at http://site.kuali.org/rice/2.2.2-SNAPSHOT/reference/html/portal.html. This documentation is still in the process of review and update which will continue through subsequent releases, so please follow the notes in each document to report any outdated information.

Contact

If you encounter any difficulty, please don't hesitate to contact the Rice team on our public collaboration mailing list at . Please indicate that you are using the 2.2.2-SNAPSHOT version of Rice.

Upgrade Guide: Rice 2.2.1 to Rice 2.2.2-SNAPSHOT

Caution

We recommend backing up your database before performing any upgrade!

Upgrading the database

Please see the Impacting Changes section of this document for details on updates to the database.

Items Addressed in Rice 2.2.2-SNAPSHOT

Bug Fix

  • [KULRICE-8538] - Responsibility Required routing flag not working unless responsibility defined for exact document

  • [KULRICE-8644] - When trying to copy certain permissions, doc gets stuck 'Enroute'

  • [KULRICE-8674] - RouteManagerException: PostProcessor failed to process document

  • [KULRICE-8857] - Permission doc says the max length of the Permission Name is 40 characters but KFS has existing values that exceed that

  • [KULRICE-8968] - PeopleFlow Maintenance Document - Unable to set ApprovePolicy when PeopleFlow Member is of type Group

  • [KULRICE-8972] - Role Service does not include AttributeTransform for QueryByCriteria calls

  • [KULRICE-9007] - RoleMemberBo.groovy prevents replacement of KIM services

  • [KULRICE-9029] - Bug in PeopleFlowMaintainableImpl retrieveTypeAttributes method

  • [KULRICE-9044] - KRAD "stacked" collection elements are not rendering add/delete buttons

  • [KULRICE-9047] - Term maintenance freemarker exception

  • [KULRICE-9062] - Action list id links result in 404 or NPE

  • [KULRICE-9081] - Stack trace while doing wilcard searches in role lookup while adding role member delegate

  • [KULRICE-9085] - TermSpecification throws an exception during save/routing

  • [KULRICE-9092] - Bug is RoleDaoOjb

  • [KULRICE-9094] - TermBoServiceImpl fails to populate TermSpecificationDefinition.contextIds on retrieval

  • [KULRICE-9095] - KRAD Error messages in section not displayed correctly

  • [KULRICE-9096] - Message after initial save prevents additional saves/routing

  • [KULRICE-9097] - Don't display the common section on KRMS Term and TermSpecification maintenance documents

  • [KULRICE-9106] - Bug in PeopleFlowInquirableImpl retrieveTypeAttributes method

  • [KULRICE-9146] - SuperUserAction tab does not load when using custom DocumentTypeAuthorizer implementation in embedded mode

  • [KULRICE-9162] - Role document broken when adding responsibilities

  • [KULRICE-9165] - Person document not displaying role qualifiers

  • [KULRICE-9169] - Bug in UiDocumentServiceImpl

  • [KULRICE-9190] - The Proposition portion of the KRMS Rule Editor is broken

  • [KULRICE-9199] - Unable to inactivate roles of type unitHierarchy or unit from person maintenance docs

Improvement

Task

  • [KULRICE-8698] - Update TRG documentation to reference maven instead of groovy when creating new Rice applications

  • [KULRICE-8959] - Investigate if column indices can be added to further improve the performance of getRoleMemberPrincipalId()

  • [KULRICE-8996] - Display Term Specification description when it displays in the Term list box while creating propositions for a rule.

  • [KULRICE-9019] - Like to have a way to fetch all valid TermSpecifications for a context

  • [KULRICE-9147] - Toggling the show/hide active button on collections causes an exception

  • [KULRICE-9148] - Disable SessionDocumentService in the KNS

  • [KULRICE-9151] - Document in the guide on clustering that session failover should be implemented for full reliability

  • [KULRICE-9152] - PK for krad_msg_t is too long for MySQL 5.1

  • [KULRICE-9221] - Invalid bean name "matchAllTxInterceptor" for KIM Remote mode

  • [KULRICE-9231] - Add striping to the tables for easier readibility

Impacting Changes

Reduce the size of KRAD_MSG_T.LOC column

The changes relate to the following issue:

[KULRICE-9152] - PK for krad_msg_t is too long for MySQL 5.1

The script reduces the size of the KRAD_MSG_T.LOC column from a VARCHAR(255) to a VARCHAR(80) (Note: for Oracle, the column is of type VARCHAR2) in order to bring down the total size of the compound primary key to a length supported by MySQL 5.1.

Depending on if you are applying this to a client or server schema, and based on your database platform, the scripts to run will differ:

  • Server dataset:

    • MySQL:

      scripts/upgrades/2.2.1 to 2.2.2/final/update_final_mysql.sql
    • Oracle:

      scripts/upgrades/2.2.1 to 2.2.2/final/update_final_oracle.sql

      The above script will leave an extra table behind named OLD_KRAD_MSG_T. Once you are satisfied that the data in the new KRAD_MSG_T table is intact, you can drop OLD_KRAD_MSG_T by running

      scripts/upgrades/2.2.1 to 2.2.2/final/cleanup_final_oracle.sql
  • Client dataset:

    • MySQL:

      scripts/upgrades/2.2.1 to 2.2.2/final/update_client_final_mysql.sql
    • Oracle:

      scripts/upgrades/2.2.1 to 2.2.2/final/update_client_final_oracle.sql

      The above script will leave an extra table behind named OLD_KRAD_MSG_T. Once you are satisfied that the data in the new KRAD_MSG_T table is intact, you can drop OLD_KRAD_MSG_T by running

      scripts/upgrades/2.2.1 to 2.2.2/final/cleanup_client_final_oracle.sql