Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-2240Rewrite RoleLookupableImpl to use KNS framework
      KULRICE-2234Rewrite DocumentTypeLookupableImpl to use KNS framework
      KULRICE-2235Rewrite RuleAttributeLookupableImpl to use KNS framework
      KULRICE-2236Rewrite RuleTemplateLookupableImpl to use KNS framework
      KULRICE-2237Rewrite EDocLiteLookupableImpl to use KNS framework
      KULRICE-2239Rewrite RuleBaseValuesLookupableImpl to use KNS framework
      KULRICE-2249Rewrite Remove/Replace User Document using the KNS
      KULRICE-12564Analysis of Data Dictionary Contstraint Rewrite
      KULRICE-3827NoteConfigComponent in EDL is using getPersonByPrincipalName where it should be using getPerson
      KULRICE-4839Field Size - KREW_EDL_DMP_T.CRNT_NODE_NM
    • Rice Module:
      KNS, KEW

      Description

      I'm not sure exactly what this means but it would be ideal if EDL could leverage the KNS document infrastructure and just provided an alternate view implementation. This would allow for lots of flexibility in EDL and reduce code duplication dramatically. Lots of analysis would need to be done prior to undertaking a task like this to determine how best to design it (and whether or not it's even feasible).

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel