Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-m9, 2.0
    • Component/s: Version Compatibility
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4979Convert Parameter objects and Services to new model object
      KULRICE-4983Convert Campus objects and Service to new model object design
      KULRICE-4984Convert County objects and service to new model object design
      KULRICE-4980Convert Country objects and service to new model object design
      KULRICE-4982Convert State objects and service to new model object design
      KULRICE-4978Convert services and objects to new model object design
      KULRICE-5003Convert PostalCode objects and Services to new model object
      KULRICE-5049Convert KIM Group objects and Services to new model
      KULRICE-5050Convert KIM Role objects and Services to new model
      KULRICE-5051Convert KIM Permission objects and Services to new model
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      For this issue we need to create properly remotable SOAP versions of the following services (there are some notes after each of these):

      1. SearchableAttribute
        • one challenge here we need to deal with is the fact that it returns a list of KNS Row objects, need to determine how best to remote these
        • we need to do this for WorkflowAttribute as well
        • returns WorkflowAttributeValidationErrors as part of this, may be advantageous to promote this as a concept up to krad/kns or the core
      2. DocumentSearchResultProcessor
        • need to review the need for isProcessFinalResults, probably has to do with not executing remote calls when unnecessary?
        • needs to not throw SQLException
        • DocSearchDTO and DocSearchCriteriaDTO need to be reviewed and converted to immutable model objects as needed
      3. DocumentSearchCriteriaProcessor
        • Review this api and figure out how to make it SOAP remotable
        • what are the search managers used for?
      4. DocumentSearchGenerator
        • need to figure out which is of these operations needs to actually be remotable, some of them use java.sql.ResultSet!
        • may need to split this out into a service that isn't remotable and one that is.
      5. SecurityAttribute
        • this probably needs to pass only the principal id and not the entire person
        • this really should only be executed once per applicatable document type from the document search, right now it executes way too many times since it does so once per row in the document search result

      In particular, should look at KC and KFS usages of each of these classes in case there are certain things we can remove from being "remotable".

      For all these cases, we need to set up a pre-packaged set of service bus exporters that client applications can use to export them.

      I suspect that the changes made for this particular jira will be particularly impactful for clients as the current functionality is somewhat hacked together and relying on some of the forgiveness of Serialization that won't translate well into a set of soap-based services.

      Also, need to review the lattix modularity notes because there was some stuff in there related to these classes.

        Issue Links

          Activity

          Hide
          Matt Sargent added a comment -

          With the latest commit, the lookup and quick inquiry icons are missing from the Group Viewer filed in the detailed search view of Document Lookup.

          Show
          Matt Sargent added a comment - With the latest commit, the lookup and quick inquiry icons are missing from the Group Viewer filed in the detailed search view of Document Lookup.
          Hide
          Matt Sargent added a comment -

          After talking to the KAI group, the document search verbiage is too engrained in current applications, etc and a move to Document Lookup on buttons and field names would be too drastic for the 2.0 release. As such it seems, based on the current 2.0 doc search deployed we need to ...
          1. Change the label on the Document Lookup page to be Document Search
          2. Revert the Name This Lookup (optional) label to be Name This Search (optional).

          Show
          Matt Sargent added a comment - After talking to the KAI group, the document search verbiage is too engrained in current applications, etc and a move to Document Lookup on buttons and field names would be too drastic for the 2.0 release. As such it seems, based on the current 2.0 doc search deployed we need to ... 1. Change the label on the Document Lookup page to be Document Search 2. Revert the Name This Lookup (optional) label to be Name This Search (optional).
          Hide
          Eric Westfall added a comment -

          I'm going to be going through the myriad of remaining issues on this jira shortly and creating separate jiras for each.

          Show
          Eric Westfall added a comment - I'm going to be going through the myriad of remaining issues on this jira shortly and creating separate jiras for each.
          Hide
          Eric Westfall added a comment -

          I created new jiras (about 25) for the remaining work on this jira. So everything should be recorded now, so I'm going to resolve this issue.

          Show
          Eric Westfall added a comment - I created new jiras (about 25) for the remaining work on this jira. So everything should be recorded now, so I'm going to resolve this issue.
          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:
              Eric Westfall
              Reporter:
              Jeremy Hanson
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 weeks
                3w
                Remaining:
                Remaining Estimate - 3 weeks
                3w
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel