JITL - JobScheduler Integrated Template Library
  1. JITL - JobScheduler Integrated Template Library
  2. JITL-487

JITL Job checkHistory does not set error attribute when checking job chains

    Details

    • Type: Fix Fix
    • Status: Released (View Workflow)
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.12
    • Fix Version/s: 1.12.6
    • Labels:
      None

      Description

      Current Situation

      When checking a job chain or an order in a job chain with the checkHistory JITL job, all checks for errors will not work as the error flag is not set correctly for orders. E.g. the query=lastcompletedrunEndedSuccessful always returns true even if the last completed run was not successful.

      Desired Behavior

      When checking a job chain or an order in a job chain with the checkHistory JITL job, all checks for errors should work. E.g. the query=lastcompletedrunEndedSuccessful should return the correct value depending on the value for RESULT_ERROR in the table REPORTING_TRIGGERS

        Activity

        Hide
        Aditi Dubey added a comment -

        Hi Uwe Risse
        While I was testing the issue by referring to this statement. While checking a job chain or an order in a job chain with the check history JITL job. How can I check the status for the order? I tested this issue with job and Job chains and its working as expected.

        Show
        Aditi Dubey added a comment - Hi Uwe Risse While I was testing the issue by referring to this statement. While checking a job chain or an order in a job chain with the check history JITL job . How can I check the status for the order? I tested this issue with job and Job chains and its working as expected.

          People

          • Assignee:
            Uwe Risse
            Reporter:
            Uwe Risse
            Approver:
            Alan Amos
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: