Understand how content that is dependent on other content
is propagated to tenants.
To ensure the proper execution of content and overall
system stability, content dependencies are propagated to tenants
together with parent content, irrespective of their propagation
labels. Such dependencies will appear during the Sync process even
if their propagation labels don’t match that of the tenant, as long
as the labels of the parent content do match the tenant’s.
For example, consider the following “Playbook With Dependencies”
sample playbook that contains two automations:
The automations are dependencies of the playbook, which needs
them to execute properly. You can view playbook dependencies under
the Propagation Labels field in Playbook Settings.
For other content items,
you can view dependencies in the same location in the relevant settings
The playbook itself has a propagation label of
matches the propagation label of the sample “Dependencies” account
that it belongs to.
However, the automations contained within the playbook have a
propagation label of
, which differs
from that of the playbook.
Even though the propagation labels of the automations do not
match that of the account, they will still be propagated to tenants
during the Sync process.