[KULRICE-234] Work with UI team to look at how best to generalize the action list so that it can show document type specific fields Created: 08/Apr/07  Updated: 21/May/15  Resolved: 10/Jan/14

Status: Closed
Project: Kuali Rice Development
Component/s: Analysis, User Interface
Affects Version/s: None
Fix Version/s: Not version specific

Type: Task Priority: Major
Reporter: Aaron Godert (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 5 hours
Time Spent: Not Specified
Original Estimate: 5 hours

Issue Links:
Relate
is related to KULRICE-1462 Add Preferences for adding Last Appro... Closed
is related to KRRM-9 Action List Improvements Open
Similar issues:
KULRICE-9102Determine how best to handle linking to DocumentHeader using JPA as was done with OJB
KULRICE-796Document how inheritance works with the Document Type hierarchy
KULRICE-4275Determine how best to position and package the cornell pdf enhancement
KULRICE-10870Establish and document Jira best practices
KULRICE-4375Action list filters
KULRICE-12170Improve the text of Action List email notifications
KULRICE-9393Determine how best to deprecate ObjectUtils so that it's not referenced from non-legacy KRAD code
KULRICE-2608Buttons in Action List header bar look bad
KULRICE-3570Look into suggestions for document instantiation improvements
KULRICE-6292Modify term selection ui so that parameterized terms can be specified
Rice Module:
KEW, KEN

 Description   

Work with Tom and Tara to figure out how best to merge the KEW and KEN action lists into a single list that makes sense for both types.



 Comments   
Comment by Aaron Godert (Inactive) [ 20/Sep/07 ]

This is a long term enhancement when we look at feeding KEW items into KEN instead.

Generated at Fri Jul 03 19:20:29 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.