[KULRICE-7666] Implement default existence checks for Maintenance document and support general data objects Created: 16/Jul/12  Updated: 21/Apr/14  Resolved: 14/Feb/14

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

Type: Task Priority: Blocker
Reporter: Jerry Neal (Inactive) Assignee: Martin Taylor (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: 1 day
Original Estimate: 3 days

Attachments: Text File KULRICE-7666_1.patch    
Issue Links:
cloned from KULRICE-7208 Template Closed
fixes KULRICE-10492 IT Failure CountyMaintenanceDocumentT... Closed
relates to KRRM-144 KRAD Equivalency with KNS Open
relies on KULRICE-10655 Maintenance Business Rules missing pr... Closed
is relied upon by KULRICE-11488 M94 demo Closed
Epic Link: Maintenance Equivalence
Rice Module:
KRAD Feature Area:
Sprint: 2.4.0-m4 KRAD Sprint 2
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:


Currently default existence checks are not being ran for KRAD maintenance documents. This is due to the restriction that the object be a business object. We need to allow for general data object support and enable in KRAD

  • Review MaintenanceDocumentRuleBase:processAddCollectionLine

Comment by Kristina Taylor (Inactive) [ 08/Jan/14 ]

I think the hook that I added in MaintenanceDocumentRuleBase.processAddCollectionLine may also be an additional place where this is needed. If, however, the checks are working for both the base maintenance document and all of its collections, then please remove the commented hook.

Comment by Kristina Taylor (Inactive) [ 10/Jan/14 ]

Does this mean that methods in DictionaryValidationService such as validateDefaultExistenceChecks(BusinessObject bo) should change to validateDefaultExistenceChecks(Object bo) or do the old methods need to be deprecated and new ones created?

Comment by Martin Taylor (Inactive) [ 16/Jan/14 ]

Ran through the DictionaryValidationService(Impl) and reset all method signatures from BusinessObject to Object to allow for dataObjects. When running tests found several needed to go through the KradLegacyDataAdapterImpl for testing reference definitions for collections and references. The methods (getReferenceIfExists, allForeignKeyValuesPopulatedForReference) being used were not implemented and produced exceptions. Began process of implementing methods and adding tests for business object and data objects.

Comment by Martin Taylor (Inactive) [ 31/Jan/14 ]

Patch update KRADDataAdapterImpl for reference and foreign key checks, replaces BusinessObject reference with Object in DictionaryValidationService and LegacyDataAdapter and their implementations

Generated at Tue Jan 19 12:42:20 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.