Usage Design Targets

The m3ter Connector for Salesforce managed package offers the Usage Design Targets (UDTs) feature as a guided way to quickly link m3ter Aggregations to the Salesforce Revenue Cloud records they represent. This topic introduces and explains how to work with User Design Targets:

• Usage Design Targets - Overview
• Usage Design Targets - Definition and Details
• Launching the Wizard
• Wizard Workflow

​

Usage Design Targets - Overview

Usage Design Targets (UDTs) connect a m3ter Aggregation to the Salesforce Revenue Cloud records that describe how that usage is designed:

• The resource being metered.
• The unit it is measured in.
• The policy that governs it.

Instead of having to manually create and stitch together several records, as a Salesforce admin you can launch a wizard and then quickly work through a guided series of steps to define these links in a single workflow.

​

Usage Design Targets - Definition and Details

​

Definition

A Usage Design Target is:

• A configuration record that binds one m3ter Aggregation to a set of target records in your Salesforce Org. Key points:
  • Each Usage Design Target is captured as a binding made up of a role, a target object, and a target record.
  • One Aggregation can have more than one Usage Design Target, and a Usage Design Target can be re-pointed to a different Aggregation later.

​

Three Core Targets

Every Usage Design Target requires all three core targets to be set before it can be saved:

• Usage Resource — the resource being metered.
• Unit of Measure — the unit the usage is measured in.
• Usage Aggregation Policy — the policy that governs how the usage is aggregated.

​

Additional Targets

• Beyond the three core targets, you can add any number of additional targets.
• Each additional target is a role, an object, and a record — pointing to standard or custom objects as required.
• Additional targets must be complete or removed: a partially filled row (for example, a role with no record) is flagged and blocks saving until it is completed or deleted.

​

Launching the Wizard

There are two entry points, both as record-page actions:

• Link Usage Targets — on a m3ter Aggregation record. The Aggregation is pre-filled, so the wizard opens at the Targets step.
• Edit Usage Targets — on an existing Usage Design Target record. The wizard opens in edit mode with the existing bindings loaded, ready for you to edit as required.

​

One-time setup: adding the actions to the page layouts

The two quick actions are included in the package but are not added to any page layout automatically, so as a Salesforce admin you need to add them once before the buttons appear on the record pages. Each action lives on its own object’s layout.

​

Add “Link Usage Targets” to the Aggregation layout:

1. From Setup, open Object Manager and select m3 Aggregation.
2. Click Page Layouts, then open the m3 Aggregation Layout.
3. In the palette at the top, select Mobile & Lightning Actions.
4. Drag the Link Usage Targets action into the Salesforce Mobile and Lightning Experience Actions section (click override the predefined actions first if the section is still inheriting defaults).
5. Click Save.

​

Add “Edit Usage Targets” to the Usage Design Target layout:

1. From Setup, open Object Manager and select m3 Usage Design Target.
2. Click Page Layouts, then open the Usage Design Target Layout.
3. In the palette, select Mobile & Lightning Actions.
4. Drag the Edit Usage Targets action into the Salesforce Mobile and Lightning Experience Actions section (override the predefined actions if needed).
5. Click Save.

​

Wizard Workflow

You will need to work through four steps to complete the User Design Targets wizard workflow:

1. Usage Design — confirm or select the Aggregation this target applies to (pre-filled when launched from an Aggregation):

2. Targets — set the three core targets - Usage Resource, Unit of Measure, and Usage Aggregation Policy. The Next button remains disabled until all three have a record selected:

3. Additional — optionally add extra targets. This step can be left empty:

4. Review — check every selected target laid out by role, object, and record name before saving:

• On Save, a success toast appears and you are taken to the Usage Design Target record. Editing a Usage Design Target replaces its bindings with the current selections.