Uploaded image for project: 'EVSClient'
  1. EVSClient
  2. EVSCLT-797

No Validation Result when xml document is not well formed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 5.10.1
    • Fix Version/s: 5.10.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      All
    • Sprint:
      2018 - S16
    • Account:
      Maintenance 2018 (MAINTENANCE2018)

      Description

      When validating an XML document that is not well formed, the Schematron validation is not performed. In this case no validation status is affected to the object (null in DB). This causes the validation status to be "NOT AVAILABLE" in validation report and empty in log list (see screenshots).
      When xml is not well formed, the validation status could be set to "NOT PERFORMED" as it is indeed not done for not well formed documents.
      Several possibilities to solve the problem :
      - Affect "NOT PERFORMED" status when the file isn't well formed
      - Change log list and validation report pages to better interpret null values (not very compliant as null values may appear in other situations + change code in many places)
      - Add a default value to the validation status field (eg "NOT PERFORMED")

      Example : https://inter-amc.kereval.com/EVSClient/detailedResult.seam?type=XML&oid=1.3.6.1.4.1.12559.11.23.2.149648

        Attachments

        1. image006.png
          image006.png
          33 kB
        2. image005.png
          image005.png
          21 kB
        3. EVSCLT-797_valRes.png
          EVSCLT-797_valRes.png
          38 kB
        4. EVSCLT-797_allLogs.png
          EVSCLT-797_allLogs.png
          16 kB

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            wbars Wylem Bars (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day, 4 hours
                1d 4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day Time Not Required
                1d

                  Potential Duplicates