Uploaded image for project: 'XNAT'
  1. XNAT
  2. XNAT-5936

Prevent bad UX when submitting event subscription that fails to validate

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 1.8
    • 1.8.4
    • Event Services
    • None
    • Rank:
      0|0hzycd:zzzr07xzi

    Description

      If you attempt to submit an event subscription, but the backend blocks it when validating it, the back-end returns a 424. The front-end does a nice job of displaying this information in a dialog. However, once that dialog is closed, the attempted subscription is lost. I can think of two (non-exclusive) ways to address this:

      1. Do front-end validation on the fields before submitting. The most important one is probably the JSONPath filter, since it is an actual code snippet, and can get complicated.
      2. If the back-end returns an error code, keep the creation dialog open with the submitted values, or reopen the dialog with the previous values repopulated.

      Attachments

        Issue Links

          Activity

            People

              hortonw@wustl.edu Will Horton
              moore.c@wustl.edu Charlie Moore (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified