Details

    • Feature
    • Status: Released (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.3.2, 2.4.0
    • None

    Description

      Current Situation

      • JS1 offers the JITL history job that allows to check if a given job or job chain was executed in some interval.
        • This includes to check successful and failed executions and running jobs.
        • This includes a number of complex rules when a job or job chain started or completed.

      Desired Behavior

      • A number of functionalities of the JS1 history job are not relevant for JS7
        • particularly when it comes to job execution for the same daily plan date: notice boards offer a better mechanism for synchronization within the same daily plan date.
      • A number of functionalities are relevant for JS7 including
        • to check past execution of jobs and workflows in intervals longer than 1 day
        • to check execution of jobs and workflows from a different Controller (registered with the same JOC Cockpit instance).
        • to check return values of past job executions and workflow executions.

      The job should accept the following queries from the query argument with one of the following values:

      • isCompleted
      • isCompletedSuccessful
      • isCompletedFailed
      • lastCompletedSuccessful
      • lastCompletedFailed

      The scope of queries is specified from the following arguments:

      • workflow: specifies the name of the workflow to be looked up. The placeholders * for any number of characters and ? for a single character can be used.
      • job: specifies the name of the job to be looked up. The placeholders * for any number of characters and ? for a single character can be used.
        • If the job argument is specified then the JS7 Task History is looked up.
        • If no job argument is specified then the JS7 Order History is looked up.

      All queries accept parameters for the date/time interval:

      • startedFrom
      • startedTo
      • completedFrom
      • completedTo

      When no interval is specified then the default values are

      • isStarted: startedFrom=0d, startedTo=0d
      • isCompleted*: completedFrom=0d, completedTo=0d. When startedFrom or startedTo is specified then the default values are for startedFrom, startedTo=0d. Otherwise startedFrom and startedTo are not considered.

      Attachments

        Issue Links

          Activity

            People

              ur Uwe Risse
              ap Andreas PĆ¼schel
              Kanika Agrawal Kanika Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: