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.
The examples below show what changes would need to be made to turn off certain default Field Profiles that may not be used in workflows for a thesis or dissertation. The workflows for hierarchical and non-hierarchical will be the same. However, fewer edits are needed to achieve the same results for hierarchical workflows.
By default, the Field Profile for Middle Name displays in Vireo. If "Hierarchical Organization Management" is turned OFF and the institution did not wish to display the field in any workflow, staff would need to disable the Middle Name Field Profile for the dissertation workflow and again for the thesis workflow in the first set of examples below.
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 |
If "Hierarchical Organization Management" is turned ON and the institution did not wish to display Middle Name in any workflow, staff would need to disable the Field Profile at only a higher or parent level. The change will be reflected in the lower or child level organizations like the Dissertation and Thesis workflows which share a parent level named "Submission Type" in the example below.
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 Field Profiles, that should be identical across all workflows, on the parent level before making any changes to the child level.
Every change made to a Field Profile at the parent level will automatically appear in the child level with these exceptions:
- The child "Workflow Step is Overridable" is marked No.
- The Field Profile at the a child level "Overridable" is marked No.
- The Field Profile at the child level has been changed from the original inherited value.
IMPORTANT NOTE: Once a change has been made at child level Field Profile, it will not inherit subsequent changes made at the parent level.