Push Static Application Attributes (Workflow Action)

Description: This guide explains how to use the Push Static Application Attributes workflow action to set or clear specific attribute values on a single application — commonly used to blank out a field like Manager during a Leaver workflow.

Tags: Dynamic Workflow, Provisioning, Termination, Active Directory, how-to

Estimated time to complete: 5 minutes

Overview

Push Static Application Attributes is a Dynamic Workflow action that pushes an explicit, author-configured set of attribute values to a single application. Unlike other provisioning actions that compute and push a full attribute set to every write-enabled application, this action only touches the exact attributes you list — nothing else on the identity’s record in that application is modified.

The key feature of this action is that empty values are allowed and preserved. This makes it the tool to use whenever a workflow needs to blank out a field — the most common example being clearing an employee’s Manager field in Active Directory during a termination, since that relationship should no longer exist once someone has left.

Before You Begin

• This action is added as a step inside a Dynamic Workflow (for example, your Leaver/offboarding workflow).

• You’ll need an earlier step in the same workflow that already has the identity available — typically the workflow’s trigger step, or a prior action step.

How to Configure

Step 1: Add the action

In your workflow builder, add a new Action step and choose Push Static Application Attributes from the Provisioning category.

Step 2: Configure the three fields

Step 3: Save the step

Once the required fields are filled in, save the action step.

Example: Clearing the Manager field in Active Directory during termination

A common use case is blanking a person’s Manager field in Active Directory once they’ve been off-boarded, so the reporting relationship doesn’t linger after they’ve left.

1. Add the action to your Leaver workflow, after the step where the identity is deactivated.

2. Set Get Identity From to the step that already resolved the identity (e.g. your termination trigger).

3. Set Application to your Active Directory application.

4. Under Attributes, add one row (see sub-items below).

5. Save.

• Attribute name: manager_identifier

• Value: (leave blank)

Note: The attribute name for Active Directory’s Manager field is manager_identifier — this is Clarity’s internal field key, not the literal Active Directory attribute name.

Dynamic Values

Non-blank values support placeholder interpolation, so you can reference other values from the workflow — for example {identity.email} — instead of typing a fixed value. Blank values are never interpolated, so they stay blank.

Tips & Best Practices

• Only the attributes you list are touched. Any attribute you don’t explicitly add is left completely alone in the target application — this action will never overwrite something you didn’t configure.

• This action works for both on-premises applications (via Clarity Connect) and cloud/API-based applications, as long as the application’s connector supports attribute overrides.

• Because blank values are preserved rather than skipped, this is the action to reach for whenever a workflow needs to actively clear a field — not just avoid setting one.

• Test in a non-production environment first, especially for a field like Manager where an incorrect attribute name will simply do nothing (rather than error), which can be easy to miss.

Need Help?