Use Custom Metadata in Policies and Reports

Once a Custom Property or Custom Relation exists, it shows up as an operand anywhere a built-in property does: in the Segment builder, in Report filters, and in Policy scopes. The operators offered match the property’s data type, for example equals and is empty for Text, before and after for Date.

Grouping and Totals

In a Report, group by a Custom Property or Custom Relation the same way you group by a built-in field. To total storage or license cost per cost center, for example, relate each Team to a Cost Center Custom Object, then group the Report by that Relation.

Excluding Objects From a Policy

To keep an Automation from touching an object, add a Yes-No Custom Property, for example Do not touch, and set it to Yes on the objects you want to protect. Then add a condition to the Policy or Segment scope excluding objects where that property equals Yes. Objects matching the exclusion produce no violations and trigger no Automation for that Policy.

Setting a Value From an Automation

The Set a custom property value Automation action sets a Custom Property you choose, on the object that triggered the Automation, to a value you choose. Use it to keep metadata current without a manual edit, for example marking a workspace after it passes a Review.