Submit Your Suggestions for Viewpoint for Projects

The current workflow filters allow a great deal of flexibility in which items trigger a workflow however a common problem, particularly with design review style workflows (a very common use) is that in order to target specific items to specific users/groups for comment/vote one of a few workarounds is required:

1. Multiple workflows need to be created (with differing triggeres - usually resulting in duplicate revision statuses) eg:

- For Comment - Architectural

- For Comment - Mechanical etc

OR

- For Comment - Groundworks

- For Comment - Substructure etc

2. A single workflow is created with an initial QA node responsible for voting the item onto one of any number of decision nodes for different review panel permutations eg QA node votes onto 1 of 6 nodes with the following panels:

- Architectural, Structural & M&E

- Architectural & Structural

- Structural Only etc

- M&E Only

- Structural & M&E

- Architectural Only

The ability to use Custom Fields as a filter would allow users to set up a workflow for each package - as generally each package has a set group of disciplines required to comment/vote. Each workflow is identical in process but the panel members for each changes to reflect the commenting/voting groups required for that package only. Using the ability to template workflows, creating any number for all packages reqiured would not take long.

Benefits:

- No duplicate revision statuses required

- Targeted Voting/Commenting - parties only receieve items they specifcally are required to vote/comment on

- Ability to combine custom fields with other filters such as revision status - only items for 'Package A' and with revision status 'For coment/approval' are captured and sent only to the appropriate parties.