Restrict workflow name characters

[Dave Lebbing]

v1.9 build 19113

Workflow names should be restricted to only use alphanumeric characters, dashes, and underscores.

A problem was observed if a workflow name contains a semicolon and the workflow installs macOS, causing the workflow to fail when run.

[timothy perfitt]

Please verify and close. Fixed in build equal to or later than: 20064

[Dave Lebbing]

Build 20069: when editing an existing workflow with unallowed characters in title, editing the title field shows unallowed characters being removed but when workflow is saved the title still shows the unallowed characters. Inspecting the ssd shows the workflow folder name is what was shown when editing the workflow but not what is shown after the workflow is saved.

If a different workflow is later edited and saved, the first workflow name appears to get updated appropriately. So this appears to be a temporary refresh issue in which unallowed characters get shown immediately after saving the workflow.

Also it could be good to add an info popover near the workflow title field that says what characters are allowed.

[timothy perfitt]

Please verify and close. Fixed in build equal to or later than: 20070