Introduction
Inventory checks verify the status of objects such as workflows being valid, deployed or released.
Checks
Inventory Summary
The check reports the number of objects in the JOC Cockpit inventory.
| Workflow | Severity |
|---|---|
Self-Test-Inventory-Summary | Warning |
Inventory Deployment Status
This check verifies the number of invalid, undeployed and unreleased inventory objects.
- Invalid objects are inconsistent, for example if the assigned Agent Name does not exist or if required properties for a workflow have not been provided. In other words: invalid inventory objects should be avoided - except for a lunch break. There is hardly any reason why to keep invalid objects in the inventory for a longer period.
- Undeployed and unreleased inventory objects indicate that objects have been modified but have not been deployed/released for test runs. While this is fine for a newly designed workflow that couldn't be completed before end of day, a larger number of undeployed or unreleased inventory objects frequently signals problems. For example, if objects have been imported but have been missed to deploy/release..
Users are encouraged to adjust threshold values when adding their own schedules to run the check on a regular basis.
| Workflow | Severity |
|---|---|
Self-Test-Inventory-DeploymentStatus | Warning |
The workflow makes use of the following arguments:
| Argument Name | Default | Purpose |
|---|---|---|
inv_max_invalid_deployable_objects | 10 | Specifies the max. number of allowed, invalid, deployable objects such as workflows, job resources etc. |
inv_max_draft_deployable_objects | 100 | Specifies the max. number of allowed draft objects that have not been deployed |
inv_max_invalid_releasable_objects | 10 | Specifies the max. number of allowed, invalid, releasable objects such as calendars, schedules etc. |
inv_max_draft_releasable_objects | 100 | Specifies the max. number of allowed draft objects that have not been released |
Overview
Content Tools