Introduction
The JS7 - Inventory knows of objects
objects include dependencies that are managed by the inventory:
Object Dependencies
Objects hold outgoing references to other objects .
| Area | Object Type | Incoming References | Outgoing References | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Controller | |||||||||
| Workflow | Workflow | Schedule | Workflow | Job Resource | Notice Board | Resource Lock | Job Template | Script Include | |
| File Order Source | Workflow | ||||||||
| Job Resource | Workflow | ||||||||
| Notice Board | Workflow | ||||||||
Resource Lock | Workflow | ||||||||
| Automation | |||||||||
| Schedule | Workflow | Calendar | |||||||
| Calendar | Schedule | ||||||||
| Job Template | Workflow | ||||||||
| Script Include | Workflow | ||||||||
Object dependencies work across folders that hold the objects. Therefore object names are unique within the scope of an object type in JS7. This allows objects to be relocated to different folders without impact on dependencies and without the need for repeated deployment of objects just because dependent objects have been moved to different folders.
Object dependencies require that all dependent objects are available with a Controller. For example, if a Workflow references a Job Resource, then the Job Resource has to be available for the Controller at the point in time of deployment of the Workflow:
- Users can deploy a number of objects in a common operation. For example, a Workflow and a Job Resource can be deployed with a single deployment step using the Deploy operation, which is available in the tree at folder level.
- Users can deploy objects individually, for example, first deploying the Job Resource and later on deploying Workflows using this Job Resource.
Note: For workflow dependencies, for example for the conditional execution of jobs, see JS7 - Workflow Instructions.
Overview
Content Tools