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

"Enabled" checkbox should be checked for creating new DICOM SCP Receiver

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7
    • Component/s: Admin UI
    • Labels:
    • Environment:

      xnat-dev05

    • Sprint:
      Prebeta push
    • Rank:
      0|ii0v2f:
    • Sprint:
      Prebeta push

      Description

      If you're creating a new DICOM SCP Receiver, I'm guessing you're much more likely to want it enabled than disabled upon creation.

        Activity

        Hide
        hortonw@wustl.edu Will Horton added a comment - - edited

        The SCP receiver IS being enabled by default, but the GET /xapi/dicomscp and /xapi/dicomscp/ID REST calls are not returning the 'enabled' property properly. In fact, attempting to set the 'enabled' property using PUT /xapi/dicomscp/ID/enabled/FLAG actually removes the "enabled" property from the GET /xapi/dicomscp/ID returned value.

        Two tasks:

        • add the "enabled" property to the GET /xapi/dicomscp results.
        • ensure that the PUT /xapi/dicomscp/ID/enabled/FLAG does not actually remove the "enabled" property from either GET /xapi/dicomscp or GET /xapi/dicomscp/ID
        Show
        hortonw@wustl.edu Will Horton added a comment - - edited The SCP receiver IS being enabled by default, but the GET /xapi/dicomscp and /xapi/dicomscp/ID REST calls are not returning the 'enabled' property properly. In fact, attempting to set the 'enabled' property using PUT /xapi/dicomscp/ID/enabled/FLAG actually removes the "enabled" property from the GET /xapi/dicomscp/ID returned value. Two tasks: add the "enabled" property to the GET /xapi/dicomscp results. ensure that the PUT /xapi/dicomscp/ID/enabled/FLAG does not actually remove the "enabled" property from either GET /xapi/dicomscp or GET /xapi/dicomscp/ID
        Hide
        hortonw@wustl.edu Will Horton added a comment -

        This blocks Day 1 Practical Session 2 from working, so this is an extremely high priority.

        Show
        hortonw@wustl.edu Will Horton added a comment - This blocks Day 1 Practical Session 2 from working, so this is an extremely high priority.
        Show
        mfmckay@wustl.edu Mike McKay (Inactive) added a comment - Fixed by https://bitbucket.org/xnatdev/xnat-web/commits/9b89838c6a67ec336463c502f280b37caa8c5f85 and https://bitbucket.org/xnatdev/xnat-web/commits/7f90251837d9ef165700da03af2eb266103d551a

          People

          • Assignee:
            moore.c@wustl.edu Charlie Moore
            Reporter:
            moore.c@wustl.edu Charlie Moore
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile