[KULRICE-10120] Attribute Definition: Conversion Guide Created: 08/Aug/13  Updated: 21/Apr/14  Resolved: 23/Aug/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Claus Niesen Assignee: Daniel Seibert (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 days
Original Estimate: 2 days

Issue Links:
Rely
is relied upon by KULRICE-10121 Attribute Definition: Conversion Script Closed
Similar issues:
KULRICE-10121Attribute Definition: Conversion Script
KULRICE-9916Do checkbox conversion in LookupInputField only when specified through attribute definition
KULRICE-9361KNS to KRAD Conversion Guide
KULRICE-7152Selenium tests for Attribute Definition Lookup
KULRICE-9923Conversion Guide: Multi Value Lookup
KULRICE-9924Conversion Guide: Other Lookup Features
KULRICE-10543Verification of Inquiry Conversion Guide
KULRICE-11561Check that Lookup conversion guide and conversion scripts are up to date
KULRICE-11562Check that Inquiry conversion guide and conversion scripts are up to date
KULRICE-11563Check that Maintenance conversion guide and conversion scripts are up to date
Epic Link: Data Dictionary Equivalence
Rice Module:
KRAD
KRAD Feature Area:
Data Dictionary
Application Requirement:
Rice
Sprint: 2.4.0-m2 Sprint 1
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

Identify differences in the attribute definition between the KNS and KRAD data dictionary and document these in the conversion guide.

Known differences exist in:

  • controls
  • formatters / property editors
  • validation patterns became constraints
  • business object entry


 Comments   
Comment by Daniel Seibert (Inactive) [ 23/Aug/13 ]

Updated KNS2KRAD-ConvGuide.
Also added worksheet to Gap Analysis Data Dictionary confluence page

Generated at Fri May 29 04:39:03 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.