At the Company level, you can define the setup of the automatic update of project statuses of active projects based on triggering conditions which are defined using various data sources as parameters. For example:
- A selected activity on the schedule sheet is in the Completed status
- A single-record business process record is set to a specified status
- A business process workflow reaches a specified status
Depending on the setup and the conditions that are set, the status of the shell can change from Active to a non-active status (On-Hold, View-Only, or Inactive). You can define multiple setups for each shell. After you define these setups, they can be used on shell instances, or on templates to enable the automatic update of shell status.
The data sources that you use in the triggering conditions can be either from shell level or from the Company level. This data sources can be business processes, sheets or attribute forms. You can define the frequency at which Unifier evaluates the conditions to see if a particular active shell should change its status, and can define a list of users or groups to be notified when the shell status is changed. The highest frequency is daily.
This automatic update of shell status can be useful for users that have a large number of shells and want many of these shells to change their status based on certain triggering conditions, and thus the users do not have to search for and modify these shells manually. For example, you can define a setup at the Company level that contains a triggering condition that changes of the status of an active shell On-Hold if the shell funds consumption exceeds the funds appropriated for that shell. This allows the shell manager to review the shell and take appropriate action. If, in this case, the shell manager is able to get additional funding for the shell, the Administrator can change the shell status back to Active to restart the shell activities.
Note: Automatic shell status update can change the status of a shell from Active to an inactive status. If you want the inactive shell to status to revert to Active, you must activate the shell manually.
Step 1: Create setups - general information.
Step 2: Verify the order of shell statuses.
Step 3: Define shell status triggering conditions.
Step 4: Define the schedule for automatic update of shell status.
Step 5: Activate the automatic update of shell status.
Step 6: Define permissions.