Skip to end of metadata
Go to start of metadata

More on KNS and KRAD

KRAD (Kuali Rapid Application Development) is the next generation of the KNS (Kuali Nervous System).

Timelines

View a more detailed timeline and breakdown of Rice 2.2 features at Rice 2.2 Project Plan with Milestones and information on 2.3 Planning at Rice 2.3 Project Plan. Note that due to the large scope of the items in 2.3 as well as the desire to get changes out to the community on a regular basis, the Roadmap items are now being delivered over 3 releases: Rice 2.3, 2.4, and 2.5. Please email rice.info@kuali.org with any questions.

Maintenance patch releases and Milestone code releases are made available with greater frequency.

See details on our release cycles, i.e. frequency of major, minor, and patch releases at Rice Roadmap - Release Cycles.

Features

key summary assignee fixVersion status

com.atlassian.sal.api.net.ResponseException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

View these issues in JIRA
key summary assignee fixVersion status

com.atlassian.sal.api.net.ResponseException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

View these issues in JIRA

Future Enhancements

Below is the prioritized list of features for future releases of Rice. Voting occurs ~ every 6 months so the order of these items are subject to change.

  1. KRRM-138: Add support for effective dating to all data in KIM in order to support historical record of data and changes
  2. KRRM-32: Mobile Application Support
  3. KRRM-90: Add support in Rice for integration of a Document Management System (DMS) system with Kuali applications
  4. KRRM-139: Offer RESTful Services from Rice
  5. KRRM-12: Implement Escalation Functionality
  6. KRRM-77: Implement "Remove/Replace Principal" functionality
  7. KRRM-143: Update delivered Rice documents/Screen to Use KRAD
  8. KRRM-147: Configurable user preferences in KIM
  9. KRRM-94: Expand KIM functionality to incorporate full Identity and Access Management capabilities
  10. KRRM-25: Design and implement Kuali Organization Management (KOM)
  11. KRRM-44: Security Metadata - Data Dictionary enhancements
  12. KRRM-6: Batch File Scheduler and Monitor
  13. KRRM-9: Action List Improvements
  14. KRRM-146: Integrate entities that are used by multiple modules or multiple applications.
  15. KRRM-41: Research how Kuali RIce can better support Federated Identity Management Services
  16. KRRM-7: KIM Management Screens
  17. KRRM-82: Internationalization and Localization Features
  18. KRRM-13: Implement simple Document-Type-based Delegation Features
  19. KRRM-142: Custom Function editor in rule editor
  20. KRRM-127: Research the approach and requirements for a GUI for KEW
  21. KRRM-101: Rice Framework Compatibility
  22. KRRM-57: Modularize KRAD
  23. KRRM-56: Expand support for XML import and export of data
  24. KRRM-8: Document Search Improvements
  25. KRRM-134: Enhance KIM with additional features to support KPME and KS establising KIM as the central person repository (Person Registry)
  26. KRRM-124: Implement a GUI for Designing KEW Processes
  27. KRRM-133: Implement Support for Federated Identity Management Services
  28. KRRM-22: Implement "update" operations for the various KIM services
  29. KRRM-24: Add support for "versionable" documents
  30. KRRM-50: A consistent documentation framework for all Rice components (see KRICE Documentation)
  31. KRRM-140: Complete modularity work on Rice impl
  32. KRRM-4: Replace KSB with alternative ESB
  33. KRRM-59: Architecture and functionality review of KEN
  34. KRRM-70: Standardize Configuration Parameter and System Parameter Names
  35. KRRM-52: Modularity (SOA+ProjectBuild+OSGI)
  36. KRRM-76: Rewrite eDocLite to use the KRAD
  37. KRRM-131: Implement Accessibility Standards
  38. KRRM-68: Implement proper handling of FERPA and FIPPA regulations
  39. KRRM-102: Implement declarative loop support within the Kuali workflow engine
  40. KRRM-14: Improve Capabilities of Exception Routing
  41. KRRM-27: Support for different DBMS platforms
  42. KRRM-86: Investigate whether the "embedded" workflow engine model should be changed to not require direct database access from client applications
  43. KRRM-75: Consolidate Notes and Attachments between KNS and KEW and KS
  44. KRRM-84: Modularization - Investigate how KIM can be modularized to run standalone
  45. KRRM-88: Improve configuration of the KNS and Rice