Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KEW, KRAD
    • Labels:
      None
    • Rice Theme:
      Development Ease of Use
    • Priority Score:
      4
    • Functional Justification :
      eDocLite is still implemented using the old pre-Rice workflow Cascading Stylesheets and look-and-feel. This results in inconsistencies between EDL-based applications and KRAD-based applications.
    • Technical Justification:
      Hide
      EDL duplicates some of the functionality that KRAD components like the data dictionary provide. It also duplicates lots of other stuff including validation, field rendering, and others.

      In addition to this, EDL could also benefit from many of the features that KRAD has (like security, KIM permission integration, etc.) which it does not currently support if it was better integrated with the framework. Bridging the gap here results in some technical challenges, but those should be researched and cataloged as part of the effort to address this roadmap item.
      Show
      EDL duplicates some of the functionality that KRAD components like the data dictionary provide. It also duplicates lots of other stuff including validation, field rendering, and others. In addition to this, EDL could also benefit from many of the features that KRAD has (like security, KIM permission integration, etc.) which it does not currently support if it was better integrated with the framework. Bridging the gap here results in some technical challenges, but those should be researched and cataloged as part of the effort to address this roadmap item.
    • Impact if not Implemented:
      eDocLite and KRAD will continue to have to evolve in parallel, resulting in additional duplication of functionality as we have to continue to enhance both frameworks.
    • Priority - KFS:
      Low
    • Priority - KC:
      Low
    • Priority - KS:
      No Priority
    • Priority - Rice:
      Medium
    • Theme:
      Development Ease of Use, Ease of Implementation, Project Standardization
    • Application Impact:
      Medium
    • Effort Estimate:
      Very High ~ 2500 hrs

      Description

      eDocLite is actually very similar to what the KRAD does, except it's all configured in XML that is "installed" to the Rice standalone server as opposed to Data Dictionary files that are "loaded" at system startup time.

        Attachments

          Issue Links

            Activity

            ewestfal Eric Westfall created issue -
            ewestfal Eric Westfall made changes -
            Field Original Value New Value
            Priority - Rice High Medium
            ewestfal Eric Westfall made changes -
            Effort Estimate Epic
            kymber Kymber Horn made changes -
            Priority - KFS No Priority Low
            lschultz Lori Schultz (Inactive) made changes -
            Priority - KC No Priority Low
            coppola Chris Coppola (Inactive) made changes -
            Priority Score 0 4
            coppola Chris Coppola (Inactive) made changes -
            Fix Version/s Unspecified Future Release [ 15670 ]
            coppola Chris Coppola (Inactive) made changes -
            Fix Version/s KR 1.2 [ 15641 ]
            Fix Version/s Unspecified Future Release [ 15670 ]
            coppola Chris Coppola (Inactive) made changes -
            Fix Version/s Unspecified Future Release [ 15670 ]
            Fix Version/s KR 1.2 [ 15641 ]
            ewestfal Eric Westfall made changes -
            Assignee Eric Westfall [ ewestfal ]
            Hide
            gpro Gary Prohaska (Inactive) added a comment -

            what's the motivation for doing this? Especially if the effort estimate is epic?

            Show
            gpro Gary Prohaska (Inactive) added a comment - what's the motivation for doing this? Especially if the effort estimate is epic?
            Hide
            ewestfal Eric Westfall added a comment -

            Regarding this, I think it only makes sense to do this after some of the KRAD functionality is in place. I think that some of the functionality planned for that will help us bridge the gaps between EDL and the current KNS framework.

            Show
            ewestfal Eric Westfall added a comment - Regarding this, I think it only makes sense to do this after some of the KRAD functionality is in place. I think that some of the functionality planned for that will help us bridge the gaps between EDL and the current KNS framework.
            ewestfal Eric Westfall made changes -
            Technical Justification EDL duplicates some of the functionality that KNS components like the data dictionary provide. It also duplicates lots of other stuff including validation, field rendering, and others.

            In addition to this, EDL could also benefit from many of the features that KNS has (like security, KIM permission integration, etc.) which it does not currently support if it was better integrated with the framework. Bridging the gap here results in some technical challenges, but those should be researched and cataloged as part of the effort to address this roadmap item.
            Functional Justification eDocLite is still implemented using the old pre-Rice workflow Cascading Stylesheets and look-and-feel. This results in inconsistencies between EDL-based applications and KNS-based applications.
            Impact if not Implemented eDocLite and KNS/KRAD will continue to have to evolve in parallel, resulting in additional duplication of functionality as we have to continue to enhance both frameworks.
            ewestfal Eric Westfall made changes -
            Effort Estimate Epic Very High ~ 2500 hrs
            Hide
            masargen Matt Sargent added a comment -

            After talking to Jerry Neal and Eric Westfall, the change should be to KRAD instead of KNS. As such I've updated this JIRA to reflect that

            Show
            masargen Matt Sargent added a comment - After talking to Jerry Neal and Eric Westfall, the change should be to KRAD instead of KNS. As such I've updated this JIRA to reflect that
            masargen Matt Sargent made changes -
            Technical Justification EDL duplicates some of the functionality that KNS components like the data dictionary provide. It also duplicates lots of other stuff including validation, field rendering, and others.

            In addition to this, EDL could also benefit from many of the features that KNS has (like security, KIM permission integration, etc.) which it does not currently support if it was better integrated with the framework. Bridging the gap here results in some technical challenges, but those should be researched and cataloged as part of the effort to address this roadmap item.
            EDL duplicates some of the functionality that KRAD components like the data dictionary provide. It also duplicates lots of other stuff including validation, field rendering, and others.

            In addition to this, EDL could also benefit from many of the features that KRAD has (like security, KIM permission integration, etc.) which it does not currently support if it was better integrated with the framework. Bridging the gap here results in some technical challenges, but those should be researched and cataloged as part of the effort to address this roadmap item.
            Summary Rewrite eDocLite to use the KNS Rewrite eDocLite to use the KRAD
            Functional Justification eDocLite is still implemented using the old pre-Rice workflow Cascading Stylesheets and look-and-feel. This results in inconsistencies between EDL-based applications and KNS-based applications. eDocLite is still implemented using the old pre-Rice workflow Cascading Stylesheets and look-and-feel. This results in inconsistencies between EDL-based applications and KRAD-based applications.
            Impact if not Implemented eDocLite and KNS/KRAD will continue to have to evolve in parallel, resulting in additional duplication of functionality as we have to continue to enhance both frameworks. eDocLite and KRAD will continue to have to evolve in parallel, resulting in additional duplication of functionality as we have to continue to enhance both frameworks.
            Description eDocLite is actually very similar to what the KNS does, except it's all configured in XML that is "installed" to the Rice standalone server as opposed to Data Dictionary files that are "loaded" at system startup time. eDocLite is actually very similar to what the KRAD does, except it's all configured in XML that is "installed" to the Rice standalone server as opposed to Data Dictionary files that are "loaded" at system startup time.
            Component/s KRAD [ 13352 ]
            Component/s KNS - UI Struts Framework [ 12850 ]
            Rice Theme Development Ease of Use
            masargen Matt Sargent made changes -
            Issue Type Suggestion [ 28 ] Rice Enhancement [ 57 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            ARC Review Pending Review [ 14619 ]
            Hide
            masargen Matt Sargent added a comment -

            From Eric: I think the effort estimate on this may end up being on the high side nowadays thanks to work that the KRAD team has done on the User Interface Framework and work that is being done on the new krad-data module for 2.3/2.4. Two of the thornier technical challenges (dynamic loading/reloading of data dictionary/UI configuration at runtime and the ability to leverage schemaless data models with dynamic type support backed by a custom datastore) are being addressed in the implementation of the UIF and the design of krad-data. Still, it doesn't hurt to keep the estimate high for now until the functionality required to support this has been implemented in full.

            Show
            masargen Matt Sargent added a comment - From Eric: I think the effort estimate on this may end up being on the high side nowadays thanks to work that the KRAD team has done on the User Interface Framework and work that is being done on the new krad-data module for 2.3/2.4. Two of the thornier technical challenges (dynamic loading/reloading of data dictionary/UI configuration at runtime and the ability to leverage schemaless data models with dynamic type support backed by a custom datastore) are being addressed in the implementation of the UIF and the design of krad-data. Still, it doesn't hurt to keep the estimate high for now until the functionality required to support this has been implemented in full.

              People

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

                Dates

                • Created:
                  Updated: