Uploaded image for project: 'JOC - JobScheduler Operations Center'
  1. JOC - JobScheduler Operations Center
  2. JOC-1743

The /orders/add API should handle missing leading slashes in the workflow path

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 2.5.0, 2.6.0
    • 2.5.9, 2.6.6, 2.7.0
    • None
    • None

    Description

      Current Situation

      When providing the workflow path("workflowPath":"folder_name/workflow_name"), without a leading slash in the /joc/api/orders/add API, the API is executed successfully with exit code 200, but the orders are not triggered.

      And when we add a workflow path with a leading slash, e.g. "/folder_name/workflow_name", the API triggers the order after it is executed successfully.

      Desired Behavior

      The name of a workflow identifies a workflow so that a path without a leading slash will be accepted.

      Patches

      Attachments

        Issue Links

          Activity

            People

              oh Oliver Haufe
              rajrani-upadhyay Rajrani Upadhyay
              Divyani Rathore Divyani Rathore
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: