Details
-
Type:
Bug Fix
-
Status: Closed
-
Priority:
Major
-
Resolution: Complete
-
Affects Version/s: None
-
Fix Version/s: 2.4
-
Component/s: Development, KNS Equivalency, User Experience (UX)
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Epic Link:
-
Rice Module:KRAD
-
KRAD Feature Area:Maintenance
-
Application Requirement:Rice
-
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?:Yes
Description
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.
Attachments
Issue Links
- cloned to
-
KULRICE-10454 Improve handling of the binding errors
-
- Open
-
- discovered by
-
KULRICE-10244 Maintenance Gap Analysis: basic stuff (rows 35-38)
-
- Closed
-
-
KULRICE-10440 Maintenance Gap Analysis: basic stuff (rows 39-42)
-
- Closed
-
- is relied upon by
-
KULRICE-13394 Create Web Tests for KRAD Maintenance Document Primary Key Editability
-
- Open
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue discovered by |
Issue Type | Improvement [ 4 ] | Bug Fix [ 1 ] |
Link | This issue cloned from KULRICE-10454 [ KULRICE-10454 ] |
Description | When a maintenance edit is done, the primary key fields on the new side should not be editable | 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}}. |
Link |
This issue discovered by |
Epic Link |
|
Fix Version/s | 2.4.0-m2 [ 17036 ] |
Component/s | User Experience (UX) [ 13465 ] |
Epic Link |
|
KULRICE-11677 [ 131203 ] |
Component/s | KNS Equivalency [ 13684 ] |
Fix Version/s | Backlog [ 15811 ] | |
Fix Version/s | 2.4 [ 16913 ] |
Original Estimate | 1 day [ 28800 ] | |
Remaining Estimate | 1 day [ 28800 ] | |
Fix Version/s | 2.4 [ 16913 ] | |
Fix Version/s | Backlog [ 15811 ] | |
Assignee | Jeff Covey [ jcovey ] |
Sprint | 2.4.0-m4 KRAD UXI Sprint 4 [ 200 ] |
Rank | Ranked higher |
Summary | Primary keys should not be editable on maintenance document copy | Primary keys should not be editable on maintenance edit action |
Assignee | Jeff Covey [ jcovey ] | Tadas Paegle [ tpaegle ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Link | This issue is relied upon by KULRICE-10459 [ KULRICE-10459 ] |
Comment | [ The generic case can be tested against Travel Account. For the specific case a data object and database table where the principalId is part of a composite key would need to be created (probably in the labs area). ] |
Remaining Estimate | 1 day [ 28800 ] | 0 minutes [ 0 ] |
Time Spent | 1 day [ 28800 ] | |
Worklog Id | 93012 [ 93012 ] |
Status | In Progress [ 3 ] | Open [ 1 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Complete [ 6 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |