Improvement for Automation rule validation.

XMLWordPrintable

      Issue Summary

      If a downstream group declares an input parameter that is never produced as an output by any upstream group, the rule:

      1. Gets stuck on “In Progress”.
      2. Passes the built‑in Validate rule check with “No problems found”.

      As an automation creator, we need the “Validate rule” to identify such issues. If a downstream component requires an input parameter, but this has not been published by another group as an output parameter or is global anyways (e.g., issueform), this should result in an error message during validation. The validator should issue a warning for this particular case as there might be occurrences where the validation fails.

      Expected Results

      When the rule is validated it should thrown an error for not output data has been added.

      Actual Results

      Currently validator is not looking into these values.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Abishek . (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: