Sequential Workflows HTML Architect: Take UX/UI Inspiration from OpenText's Workflow Editor

ideas
1

When we implement sequential workflows in HTML Architect, I’d like to propose to take inspiration from OpenText Content Management as a UX/UI reference.

References:

Important: This is strictly about UX and UI — the visual presentation and interaction model. I’m making no claims about their workflow engine. Our engine stays as-is; the goal is to make the editor experience more intuitive and visually engaging.

Why OpenText: Their workflow visualization is noticeably clearer and cleaner than what’s currently in Origam Architect Desktop. Steps are easy to follow, transitions are obvious

2

What we have in Origam Architect Desktop

image
image928×693 46.6 KB

What Open Text have

image
image1908×964 188 KB

3

@DanilTkachenko
Have you checked whether it’s possible to define your own set of elements for use in workflows? We need to adapt this to the specific capabilities of the Origam model. For example context stores are something that needs to be treated…

4

From scratch it’s impossible, if I understood this correctly. But we can combine these two approaches the OpenText one and Origam’s and by combining them we can deliver something better than what we currently have in Origam Desktop

@vikter