Under Community Review
over 2 years ago

R&D is considering both options in regards of Workflow Designer update: migrate Visio extension to .NET (so it will support the latest version of Visio, both x86 and x64) and implement it as part of CME (no dependency on Visio at all). Second option is preferable, but it is more expensive.

Please share your experience on defining Workflow Definitions:

  • How many step does it usually contain? How many manual, automatic or decision activities?
  • Visio stores activities position on the diagram after you moved them. Is it important feature for you?
  • Any missing features?

Have the Workflow Designer support the latest 64-bit editions of Visio

Currently, the Workflow Designer requires a 32-bit version of Visio (2010, 2013 or 2016). Most people (I would guess) have the 64-bit version installed. They need to uninstall that and install the 32-bit version. 

Please start supporting the 64-bit editions.
Also, if you could add support for Visio 2019 (the latest version), that would be even better.

  • First of all, workflow is not used much, because a Tridion workflow is seen as something that obstructs the editor in their work, rather than help them achieve tasks.

    If I do implement workflow, a typical process definition may contain between 6 and 12 activities.

    The physical layout of the diagram is not so important, I'd rather have the system figure this out for me. In general, I think SDL shouldn't invest a lot of time in this feature. If an upgrade to a 64-bit Visio is easy to do, I'd prefer that to a bigger refactoring.

  • I agree, Dominic. It's probably quicker to upgrade the plugin to 64-bit, so R&D can focus on other tasks :)

  • This gets an upvote from me, but I think we should also be looking at whether Visio is the right tool for the job considering what's possible in the browser these days.