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. Use it to scope, group, and exclude by the fields you defined.

Before you begin

• Your Rencore role can create the Segment, Report, Policy or Automation you want to use the metadata in. Owner, Admin and Contributor can. See Rencore roles.
• Custom Metadata is included in the Enterprise Plan and available as an add-on to the Premium Plan.
• The Custom Property or Custom Relation exists. See Create a custom property.

Steps

Filter by custom metadata

1. Open the Segment builder, a Report filter or a Policy scope.
2. Select the Custom Property or Custom Relation as the operand, the same way you select a built-in property.
3. Choose an operator. The operators offered match the property’s data type, for example equals and is empty for Text, before and after for Date.

Group and total in a report

1. Relate each object to the instance you want to total by, for example each Team to a Cost Center Custom Object.
2. In the Report, group by that Custom Relation or by a Custom Property, the same way you group by a built-in field.

For example, this totals storage or license cost per cost center.

Exclude objects from a policy

1. Add a Yes-No Custom Property, for example Do not touch.
2. Set it to Yes on the objects you want to protect.
3. Add a condition to the Policy or Segment scope that excludes objects where that property equals Yes.

Objects matching the exclusion produce no violations and trigger no Automation for that Policy.

Set a value from an automation

1. In an Automation, add the Set a custom property value action.
2. Choose the Custom Property and the value. The action sets it on the object that triggered the Automation.

Use it to keep metadata current without a manual edit, for example marking a workspace after it passes a Review.