-
Bug
-
Resolution: Done
-
Critical
-
None
-
False
-
-
False
-
-
Description of the problem:
There are several issues for the basic assessment software template as currently exists in v.0.2.28:
1. Confusing user experience:
The user is required to fill in many fields that have unclear meanings:
"Workflow ID" field: Why should the user know that the workflow's ID will be the workflow identifier in Sonataflow? It implies that the user needs to check SF for an unique already existing ID. This field and description should be changed to "Workflow Name".
"Default Infrastructure Workflow Name/ID" - The meanings of these fields are extremely unclear to a first time user. If I am creating a workflow for the first time on my cluster, how can I know from the docs or from the fields' description that I already should have deployed an existing infrastructure workflow? "Default workflow available in the cluster" implies that it was already deployed automatically.
In addition, there appears to be no difference between Name and ID. The fields should be combined.
- The Assessment workflow should stand alone, and not be dependent on another workflow to be created, especially if this is a basic template that should work "out of the box". These fields should be optional or removed altogether.
2. The user is expected to know that after the workflow is created, if the user enters "default" as the "someText", the default Infrastructure workflow will appear as the result. Although this does appear in the generated README file and in the source code, it is not clearly spelled out to the user in the documentation or in the workflow UI itself.
How reproducible: 100%
Expected results: Better user experience for basic template creation.