Skip to end of metadata
Go to start of metadata

Purpose

A consistent look and feel would give a much more polished view of Rice to implementation and potential implementations. Additionally, this conversion will be a practical application of KRAD that Rice based Kuali applications can reference as they start looking at converting to KRAD in the future.

Detailed Description

Delivered Rice screens are currently a mix of Spring MVC, KNS, and KRAD; this work would bring the delivered view of Rice under a single framework and give a consistent Look & Feel to Rice. This task is to update all delivered Rice screens, documents, lookups, and inquiries along with the action list, document search, portal, and login screen to use KRAD instead of the current mix.

It's important to note that this work is focused on the conversion of the screens to use KRAD. While working on these there will be some updates to the usability to the screen through the natural development process; however a full usability review and redesign is not intended.

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:

Performance

If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):

References

Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

  1. KULRICE-8910 - Data cannot be retrieved due to an unexpected error
Screens conversion grid

Portal Path

Name

Lookup

Inquiry

Maintenance

Screen

Notes

Login Page

Login Page

n/a

n/a

n/a

 

 

Action List

Action List

n/a

n/a

n/a

 

 

Document Search

Document Search

n/a

n/a

n/a

 

 

Help

Help

n/a

n/a

n/a

 

 

Main Menu > Sample Travel Application Channel

Travel Account

 

 

 

 

 

 

Travel Fiscal Officer

 

 

 

n/a

 

 

Travel Account Type

 

n/a

n/a

n/a

 

 

Travel Account Use Rate

 

 

n/a

n/a

 

 

Attachment Test

 

 

 

n/a

need to ingest sample_attachment_doc_type.xml to test

Main Menu > Workflow

User Preferences

n/a

n/a

n/a

 

 

 

Quicklinks

n/a

n/a

n/a

 

 

 

Routing Report

?

?

?

 

 

 

Routing Rules

 

 

 

n/a

 

 

Routing and Identity Management Hierarchy

n/a

n/a

n/a

 

 
 View Document Configurationn/an/an/a accessed from Routing and ... Hierarchy view

 

eDoc Lite

 

n/a

n/a

n/a

Just the lookup, right?

 

PeopleFlow

 

 

 

n/a

 

 Route Logn/an/an/a Not on the main menu, but let's not forget it!

Main Menu > Notification

Notification Search

 

 

n/a

n/a

I think this is just a custom doc search

 

Channel Subscriptions

n/a

n/a

n/a

 

 

 

Delivery Types

n/a

n/a

n/a

 

 

Main Menu > KRMS Rules

Create New Agenda

 

 

 

n/a

 

 

Agenda Lookup

 

 

 

n/a

 

 

Context Lookup

 

 

 

n/a

 

 

Attribute Definition Lookup

 

 

 

n/a

 

 

Term Lookup

 

 

 

n/a

 

 

Term Specification Lookup

 

 

 

n/a

 

 

Category Lookup

 

 

 

n/a

 

Administration > Workflow

Rule Attribute

 

 

?

n/a

 

 

Rule Template

 

 

?

n/a

 

 

XML Stylesheets

 

 

?

n/a

 

 

XML Ingester

n/a

n/a

n/a

 

 

 

Statistics

n/a

n/a

n/a

 

 

 

Document Operations

 

n/a

n/a

 

 

 

Document Type

 

 

 

n/a

 

Administration > Notification

Send Simple Notification

n/a

n/a

n/a

 

 

 

Send Event Notification

n/a

n/a

n/a

 

 

 

Manage Content Types

 

 

 

n/a

It's not a maint doc now, but looks like it should be

Administration > Identity

Person

 

 

?

 

hybrid trans/maint doc

 

Group

 

 

?

 

hybrid trans/maint doc

 

Role

 

 

?

 

hybrid trans/maint doc

 

Permission

 

 

 

n/a

 

 

Responsibility

 

 

 

n/a

 

 

Campus

 

 

 

n/a

 

 

Country

 

 

 

n/a

 

 

County

 

 

 

n/a

 

 

Postal Code

 

 

 

n/a

 

 

State

 

 

 

n/a

 

 

Address Type

 

n/a

n/a

n/a

 

 

Affiliation Type

 

n/a

n/a

n/a

 

 

Campus Type

 

 

 

n/a

 

 

Citizenship Status

 

n/a

n/a

n/a

 

 

Email Type

 

n/a

n/a

n/a

 

 

Employment Status

 

 

n/a

n/a

 

 

Employment Type

 

 

n/a

n/a

 

 

Entity Type

 

n/a

n/a

n/a

 

 

External Identifier Type

 

n/a

n/a

n/a

 

 

Name Type

 

n/a

n/a

n/a

 

 

Phone Type

 

n/a

n/a

n/a

 

 

Role/Group/Permission Responsibility Type

 

n/a

n/a

n/a

 

Administration > Configuration

Parameter

 

 

 

n/a

 

 

Parameter Type

 

 

 

n/a

 

 

Component

 

 

 

n/a

 

 

Namespace

 

 

 

n/a

 

 

Pessimistic Lock

 

 

n/a

n/a

PessimisticLock.xml

 

Configuration Viewer

n/a

n/a

n/a

 

 

Administration > Service Bus

Message Queue

n/a

n/a

n/a

 

 

 

Thread Pool

n/a

n/a

n/a

 

 

 

Service Registry

n/a

n/a

n/a

 

 

 

Quartz

n/a

n/a

n/a

 

 

 

Security Management

n/a

n/a

n/a

 

 

Administration > Miscellaneous

Cache Admin

n/a

n/a

n/a

 

 
Secondary:
  1. item

Dependencies

  1. Working with the UX team, a standard look and style for all of delivered Rice needs to be created. Things like colors and images can be applied after or while development is going on, but it would be good to have standard layout decisions made ahead of times. Changes to standards in table or page structure could affect the conversion of these pages.

Issues

List any issues that need to be resolved before work on this item can begin:

Functional:
  1. item
  2. item
Technical:
  1. Converting KNS, KSB, and KEN may involve more than simply plugging in KRAD on them

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps

Checkoff

Functional Analysis Complete? No (completed by SME)

Needs Review by KAI? No (completed by SME)

Technical Analysis Complete? No (completed by DM)

Needs Review by KTI? No (completed by DM)

Estimate: ~1,000 hours (completed by DM)

Technical Design: Link Here (completed by DM)

JIRA: KRRM-143 - Data cannot be retrieved due to an unexpected error (completed by SME)

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels