[KULRICE-10452] Primary keys should not be editable on maintenance edit action Created: 11/Sep/13  Updated: 21/Apr/14  Resolved: 19/Feb/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development, KNS Equivalency, User Experience (UX)
Affects Version/s: None
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Major
Reporter: Jerry Neal (Inactive) Assignee: Tadas Paegle (Inactive)
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 1 day
Original Estimate: 1 day

Issue Links:
cloned to KULRICE-10454 Improve handling of the binding errors Open
discovered by KULRICE-10244 Maintenance Gap Analysis: basic stuff... Closed
discovered by KULRICE-10440 Maintenance Gap Analysis: basic stuff... Closed
is relied upon by KULRICE-13394 Create Web Tests for KRAD Maintenance... Open
Epic Link: UI Maint/Doc
Rice Module:
KRAD Feature Area:
Application Requirement:
Sprint: 2.4.0-m4 KRAD UXI Sprint 4
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:


When a maintenance edit is done, the primary key fields on the new side should not be editable. There is also a special case which is also not working for when principalId is part of the primary key, where if a UserControl is used and the principalName is actually being written by the control instead of the principalId, then the control should not be editable. Both of these cases are handled in the KNS in FieldUtils.fixFieldForForm.

Comment by Tadas Paegle (Inactive) [ 19/Feb/14 ]

Added @override method performCustomApplyModel() to MaintainableImpl.java

Generated at Mon Jan 25 14:08:09 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.