Uploaded image for project: 'Gazelle Test Management'
  1. Gazelle Test Management
  2. GZL-3545

Many companies have duplicate webservice configuration entries

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: TestManagement-4.11.0
    • Fix Version/s: Gazelle TM 5.0.0
    • Component/s: None
    • Labels:
      None
    • Account:
      IHE Europe (IHE2012)

      Description

      In the NA2015 testing session, two vendors have complained about duplicate entries in their default configuration.

      Logibec said that had 120 entries (now cleaned out).

      Today, CareEvolution complained about the same thing. See attached screen shot.

      I looked at a few others, and indeed there is a problem.

      I expect that there is nothing that can be done (I am not going to delete and re-generate all configs at this point).

      However, I am writing this jira issue because I think that, when gazelle says it is just generating missing configs, it is actually re-generating everything and making a mess.


      In looking through the configs, I have not seen duplicates in the DICOM, HL7v2 or v3 entries.

      ====
      And Tiani reported this:

      This was not the only problem.
      We entered all our configs end of november or beginning of december. And these were very much in our case!!!
      Then you (or gazelle) created the configuration automatically and we had all entries duplicated, so we had to delete all automatically created entries. And every time after deleting one entry, the list (much more than 10 sides) jumps to the beginning. This is work for one week for one person!

      But we did it :-)


        Attachments

        1. image.png
          101 kB
          Lynn Felhofer

          Issue Links

            Activity

              People

              • Assignee:
                gthomazon Guillaume Thomazon
                Reporter:
                lfelhofer Lynn Felhofer
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 hours Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours, 15 minutes
                  2h 15m

                    Potential Duplicates