Uploaded image for project: 'i2b2 Web Client'
  1. i2b2 Web Client
  2. WEBCLIENT-25

Locked out status for obfuscated user is not understood and causes query to appear to run continuously

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.5.00
    • 1.5.2
    • CRC Cell, Web Client
    • None
    • Issue occurs in all supported browsers (I.E., Firefox & Safari)
    • Query Tool
    • Obfuscation, Roles Based Access

    Description

      As part of the roles based access enhancement those users who are set up as an obfuscated user will be "locked out" if they run a query more than 8 times. The CRC will return the following status in the received xml:

                 <status>
                      <condition type="ERROR">LOCKEDOUT error : User account locked on [Wed Dec 08 09:43:07 EST 2010]</condition>
                  </status>

      Currently the web client does not know what to do with this status and will display the following error message to the user:

      "Cell status message could not be understood."

      When you click on OK you will notice in the Query Status section/box of the page the time is continuing to advance leaving the user to believe the query is still running. In addition, the previous query will not display that the query had an error. It will display the patient set with a count of zero which can be misleading to other users.


      WHAT SHOULD HAPPEN:

      When the above status of LOCKEDOUT is returned the following message should be displayed to the user.

          "Unable to process the query because your account has been locked out. Please contact your administrator."

      Once the user clicks on OK to close the message box the query status should be updated to say either Completed or Error. In addition the result set in the Previous Query view should be updated to display ERROR.

      Attachments

        Activity

          People

            mem61 Mike Mendis
            jmd86 Janice Donahoe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: