Adding groovy script path in Assets automation on windows get absolute path error

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • None
    • Affects Version/s: 5.3.1, 5.4.0
    • Component/s: Assets - Automation
    • None
    • 1
    • Severity 2 - Major

      Issue Summary

      Recent translation changes changed the Assets UI to be ' MUST_START_WITH_SLASH_PATTERN' state. Meaning absolute path are only considered for unix-like paths. No windows support retained.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Assets -> Schema Configuration -> Automation -> Create Automation
      2. Add action -> type : execute groovy script
      3. *Attempt to add windows path: example C:\\example
        it.groovy

      Expected Results

      Accept windows absolute path

      Actual Results

      Customer receives UI error message:
      Script file path must be absolute

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Louis (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: