Business Rules: Data Actions > Set attribute to NULL

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When looking to Business Rules, Attribute Update rules we can take Data Actions to set an Attribute to a given value, but there is no feasibility to set an attribute to NULL 

Is this intended?

Environment

Any supported Clarity release

Resolution

This is by design:

You cannot configure a Set Attribute value to NULL, Blank, or No Value.

Workaround: Use Classic PPM processes instead to set a field value to NULL

Things to remember with Business Rules for Attribute Updates

• Supported data types for Set Attributes data actions include Lookups, Date, Boolean, String, Number, Money, and Percent.
• The following attributes cannot be used with Set Attributes data actions: Auto-numbered, Audit Attributes and attributes marked Read-Only in Classic PPM.
• When defining data actions, you can choose between Set Attributes or Send Action Items, which need to be defined on the Action Items page in Clarity.
• UI actions, such as Hide Actions and Hide Attributes, will be applied after Data Actions.
• If the Target Attribute is deleted or inactivated, the rule will be disabled.
• You cannot configure a Set Attribute value to NULL, Blank, or No Value.
• Set Attribute will always run first regardless of the order of the Data Actions.
• Regardless of whether the Data Actions succeed or fail, the rule will still execute the UI Actions.
• You cannot configure set attribute data action on the Target Attribute of the business rule or trigger another set attribute rule (rule chaining).
• Creating a new record will not trigger a set attribute rule.
• Set attribute rules for dates will set the date based on the Clarity server time.
• Set attribute rules will not override any Clarity locks on attributes or records (process engine, MSP, Interactive Grants, etc.).
• Set attribute rules will override attributes configured with read-only attributes and records based on another business rule.
• Set attribute business rule will set the attribute value even if the attribute is not visible to the end-user (field-level security).
• If you want to make a REST API call that triggers the set attribute rule, you need to include "x-api-rule-engine": "ui" in the header of your call

If this is important for you, please raise this an idea