Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-6015

Clicking the '-' button next to 'The Value for' Reconciliation Query Filters in the Admin UI throws JavaScript errors in the console

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: OpenIDM 4.5.0, OpenIDM 5.0.0
    • Fix Version/s: OpenIDM 5.0.0
    • Component/s: Module - Web UI
    • Environment:
      OSX w/Chrome Version 51.0.2704.84 (64-bit)
    • Sprint:
      OpenIDM Sprint 62, OpenIDM Sprint 63
    • Story Points:
      2

      Description

      Within the OpenIDM 4.5.0 and 5.0.0 mapping association pane, performing the following steps fails to remove the defined Reconciliaiton Filter and throws a Javascript error within the browser's console.

      1. Navigate to 'Association' -> 'Reconciliation Query Filters'
      2. Define a new Source Query using 'The Value for', for example: /givenName sw 'Chr'
      3. Save the changes
      4. Open the browsers Javascript console
      5. Click the '-' button in an attempt to delete the Query Filter
      6. Note that the Query Filter is not removed and the browser throws the following errors:

      FilterEditor.js?v=4.5.0:85 Uncaught TypeError: Cannot read property 'pop' of undefineddeleteNode @ FilterEditor.js?v=4.5.0:85removeNode @ FilterEditor.js?v=4.5.0:65r @ lodash-3.10.1-min.js?v=4.5.0:26dispatch @ jquery-2.1.1-min.js?v=4.5.0:3r.handle @ jquery-2.1.1-min.js?v=4.5.0:3
      

      7. Attempt to remove the Query Filter by changed 'The Value for' to 'No Filter', notice that the console displays the following errors:

      FilterEditor.js?v=4.5.0:118 Uncaught TypeError: Cannot read property 'length' of undefinedupdateNodeValue @ FilterEditor.js?v=4.5.0:118r @ lodash-3.10.1-min.js?v=4.5.0:26dispatch @ jquery-2.1.1-min.js?v=4.5.0:3r.handle @ jquery-2.1.1-min.js?v=4.5.0:3
      

      8. Save the changes
      9. Notice that the changes are saved correctly and the Query Filter is removed from the mapping

      Note that a user can workaround the issue as described in #7 but that the change is not reflected in the UI immediately. Rather the change to 'No Filter' is persisted in the config when saved and is reflected in the UI upon a refresh of the page.

      Also note that I have only tested this with the Chrome browser on OSX. The problem may or may not exist with other browsers.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                javier.quiroz Javier Quiroz
                Reporter:
                cgdrake Chris Drake
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: