Tenant-specific data

Some fields in workflow conditions and actions automatically populate with data from your tenant environment and do not require manual input. Workflows then operate on the actual resources and users in your tenant. Tenant-specific data includes user email addresses, protection plans, scripts, and hostnames, for example.

So, for example:

• You can select recipients directly from the list of users in your tenant when you configure a Send email action.

• You can select from the scripts and protection plans that are available in your tenant when you configure a Run script or Apply protection plan action.

Warnings for missing or outdated data

If tenant-specific data that is referenced in a workflow condition or action becomes unavailable or outdated (for example, a user was deleted or a protection plan was removed), the platform displays a warning indicator on the affected step. The workflow cannot be executed if tenant-specific data is invalid. Review the affected steps and update them with valid data, or reset them to their default state.

Behavior during workflow operations

Tenant-specific data behaves as follows during common workflow operations:

• Propagation: Tenant-specific data is reset to its default state in all propagated copies of the workflow.

• Cloning: Tenant-specific data is retained in the cloned workflow.

• Workflow version change: Tenant-specific data in existing conditions and actions is not affected when the workflow version changes.

• Adding a new condition or action: Adding new steps to the workflow does not affect the tenant-specific data already configured in existing steps.