[MGNLWKLED-24] UX review for workflow editor Created: 27/Mar/17 Updated: 04/May/18 |
|
| Status: | Open |
| Project: | Workflow Online Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Adrien Manzoni |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Description |
|
UX review and recommendations on Adrien's Workflow Editor so the editor can be integrated into the product. Publish / UnpublishThe buttons currently only have the functionality to store versions of a workflow but they have nothing to do with the common action of publishing to the public instance. So the action here is not clear to the user.
Export/Import vs. Download/UploadImport/Export buttons relate to the whole JCR node as used everywhere in Mgnl. The Upload/Download button relate to the diagram only (BPMN) so the latter is the standard bpmn format and can be opened by any BPMN tool. The difference is not clear at first glance.
BPMN property panel1. The position of the property panel competes with the Mgnl action bar on the right side.
2. There is a lot of technical wording in labels, input fields, dropdowns.
3. All input fields look same and especially look like they are editable, but some of them are not.
4. There are too many free text input fields where options could be clearly defined (e.g. groups, roles, users)
5. The bpmn logo has quite a prominent position.
Tab nameThe tab name of a currently selected diagram shows the path followed by the word :EDIT. In this way it is most probable that you won't see the actual name of the diagram because the path is too long and cuts off the name of the diagram which actually is the relevant information in this case.
Bugs
|