Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-6595

Problem with Data Dictionary Entry hierarchy for transactional documents

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-rc1
    • Fix Version/s: 2.0.0-rc2, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10896KNS transactional documents are unable to mask their fields
      KULRICE-12346NPE in role document if required is null in remote data dictionary entry
      KULRICE-6745Document the Data Dictionary Validation improvements
      KULRICE-12166Two instances of the data dictionary service (and data dictionary) are loaded in Rice context
      KULRICE-1460Implement best of breed for maint and transactional doc frameworks
      KULRICE-8005DataDictionaryIndexMapper change breaks transactional documents when institutions override business object classes
      KULRICE-6217Document the Data Dictionary
      KULRICE-10711Data Dictionary Analysis (items DD1 - DD6)
      KULRICE-10712Data Dictionary Analysis (items DD7 - DD9)
      KULRICE-4721Ability to specify custom actions in data dictionary
    • Rice Module:
      KRAD
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      So, at the moment, transactional documents are pretty much non-operational in KFS. The mapping which allows us to use the DD properties from the JSP layer hinges on being able to use the simple class names of the documents as keys into the DD. Unfortunately, the DataDictionaryIndexer is only using the new KRAD TransactionalDocumentEntry class when choosing how to index the classes. This results in the expected entries being absent and causing a host of problems.

      Either the indexer needs to recognize the KNS version of the TransactionalDocumentEntry class or the KRAD version needs to be moved as a superclass of the KNS version like all the other entry classes.

      Thanks.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          This sounds like a rough one, assigning to Jerry.

          Show
          Eric Westfall added a comment - This sounds like a rough one, assigning to Jerry.
          Hide
          Jerry Neal (Inactive) added a comment -

          Jonathan,

          I made the change to have KNS trans doc entry extend KRAD trans doc entry so it will get picked up by the indexer. Let me know if this fixes the problem. Unfortunately we don't have a KNS trans doc to test with (we will be working on getting something).

          Sorry for all the ugliness here!

          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Jonathan, I made the change to have KNS trans doc entry extend KRAD trans doc entry so it will get picked up by the indexer. Let me know if this fixes the problem. Unfortunately we don't have a KNS trans doc to test with (we will be working on getting something). Sorry for all the ugliness here! Jerry
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Jerry Neal (Inactive)
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel