Vireo 4 introduces the concept of workflow hierarchies where settings at a higher, or parent, level can be inherited by related lower, or child, level workflows. This feature helps to enforce consistency and reduces the need to replicate data entry across workflows.
If Hierarchical Organization Management is turned off, the workflows are considered flat. Multiple workflows can be added but each will need to be created and maintained separately.
Workflow examples with hierarchical and non-hierarchical management.
...
In the examples below the theses workflows are identical, and the doctoral workflows are identical
...
, but the flat organization requires
Creating Non-hierarchical workflow (flat organization)
Changes to make
| Vireo Default fields | Dissertation workflow / submission form | Thesis workflow / submission form |
|---|---|---|
| Middle Name | Disable field | Disable field |
| Program | Disable field | Disable field |
| Current address | Disable field | Disable field |
| Submission to ProQuest | No change | Disable field |
| Abstract | No change | Disable field |
Creating a hierarchical workflow
Changes to make
| Vireo Default fields | Parent level | Dissertation workflow / submission form | Thesis workflow |
|---|
...
| / submission form | |||
|---|---|---|---|
| Middle Name | Disable field | - | - |
| Program | Disable field | - | - |
| Current address | Disable field | - | - |
| Submission to ProQuest | No change | - | Disable field |
| Abstract | No change | - | Disable field |
The key to efficient hierarchical workflows is to first set up the fields in the parent level that will be identical across all workflows.
Every change made the parent level will automatically appear in the child level, unless the "Workflow Step is Overridable" is marked No, or "Overridable" is marked No on a the Field Profile at the a child level.
Field profile of Middle Name at child level
