Considerations for Creating and Editing Measures

Access to Objects and Fields When Building Measures

When you’re creating a measure, if you can’t see objects or fields that you want to add, contact your Salesforce admin. Sometimes Salesforce admins can correct the issue by adjusting Enablement settings or object- or field-level security settings. See Resolving Access to Enablement Measures Objects and Fields.

Availability of Prebuilt Measures

Most prebuilt measures are available right away on the Enablement Measures page and in program templates. Sometimes it can take up to 1 hour for prebuilt measures to become available. If you don’t see prebuilt measures in that that time, contact Salesforce Customer Support.

Sometimes prebuilt Einstein Conversation Insights (ECI) measures require Salesforce admins to create the ECI measure manually from Setup.

Important ECI isn’t supported in Developer Edition, isn’t supported in Partner Enablement programs in Experience Cloud sites, and isn’t included with Enablement Lite. However, if you’re trying Enablement Lite and your company already uses ECI, you can still use ECI measures with Enablement Lite programs.

Customizing Prebuilt Measures

Save time creating Enablement measures by starting from a prebuilt measure that you want to modify. We recommend that you clone a prebuilt measure rather than editing it. Program templates reference prebuilt measures. If you modify a prebuilt measure directly, you permanently change the behavior of any program template that references the prebuilt measure, and the measure no longer functions as the program template describes. To undo changes you make to a prebuilt measure, you must manually reset each parameter.

Editing Measures in Assigned or Enrolled Programs

You can edit the measure name or description for a measure at any time. Measure names are visible to users when they take a program and they view the details of an outcome or milestone, but descriptions aren’t visible. Changing the name or description doesn’t affect programs where the measure is used.

But we recommend that you avoid editing these measure parameters if the measure is used in a program that users are taking.

• The object the measure is based on
• The User Field, Display Field, and Date Field
• Field filters
• Any related objects and their field filters

To see whether a measure is used in a program, check whether the measure is marked as active. Then to see whether any user is assigned to or enrolled in the program, check the Enrolled Users related list on the program record detail page.

When you edit a measure used in program outcomes or milestones that users have achieved, their progress isn’t recalculated. Instead, the changes you make skew completion analytics across that program. Users who previously completed the program were assessed according to the original measure criteria, and the next users who take the program are assessed according to the changed criteria.

Likewise, in users’ view of the program, progress continues to appear according to the criteria set at the time the user completed the outcome or milestone.

To avoid these issues, preview your measure to make sure that you built it accurately before you include the measure in a program.

Before you edit a measure that’s used in a program that users are taking, first allow the enrolled users to complete the program. Then, retire the program. This strategy avoids disrupting progress data in your analytics. To start using an edited measure, clone it, modify it, and add it to a new program. The new program has specific analytics that your Enablement team can track separately. One exception to this guideline is when you’re fixing an invalid measure, where the progress analytics are disrupted anyway.

Invalid Measures

A measure can become invalid and stop tracking progress under these circumstances.

• An object or field is removed.
• An object label or API name is renamed.
• A field’s API name is renamed.

Only measures in a program that users are taking can be invalid. Measures are flagged as invalid only after a breaking change is saved and the corresponding outcome or milestone progress is calculated. By default, progress for outcomes and milestones is calculated daily at 6:59 AM, 11:59 AM, 4:59 PM, and 11:59 PM, according to your Salesforce org’s time zone setting. Users can also refresh outcome and milestone progress on demand when they take the program.

To avoid disruptions in your program analytics, periodically check the validity of all measures. From the Enablement Measure record detail page, check the status of the Valid field.

In most cases, we recommend that you avoid editing measures used in a program that users are taking so that you don’t disrupt your analytics. But for an invalid measure, because analytics are disrupted anyway, editing the measure can be worth the extra work. For the least disruption, try to update an invalid measure so that it tracks the same activity but with the corrected object or field information.

To help you avoid invalid measures, ask your Salesforce admin to stay in touch about changes to objects and fields that you’re using with Enablement programs.

Previewing Measures

You can test the accuracy of your measures during the Preview step. Previewing checks that the measure accurately tracks user progress toward the goals you set in a program and avoids introducing issues to programs where you reference the measure.

To determine whether a measure works correctly, try to verify three to five users during the preview. If the preview doesn’t show the records that you expect to qualify, consider these steps.

• Reconsider the user and start date that you previewed.
• Return to the measure parameters and verify them. After an unsuccessful preview, the parameters that most commonly require adjustments are the User Field and field filters.
• If the measure follows a newly introduced process for tracking a user behavior or goal, verify that users have started using the process. You can always wait to activate the measure until you’re sure the new process is working.
• If your company uses Salesforce reports for tracking the same behavior or goal that you’re measuring, the filters on that report can inform how to build this measure. The report can also inform which users and start date to test.
• Sometimes your company’s object-level security or sharing settings prevent you from seeing records that qualify for a measure, even when it’s built correctly. Ask your Salesforce admin whether your security or sharing settings can be adjusted to allow you to preview the measure. Or consider using different objects or fields to identify the user goal or behavior that you want to track for this measure.

• You can track measures built on ECI objects only up to 180 days in the past. When previewing ECI measures, select a start date that occurs within the last 180 days. Records that qualify for the measure more than 180 days ago don’t show up during the preview.

Working with Related Objects

To follow user behavior that’s tracked on a related object, create a measure for the parent object and add the related object from the Field Filters step. Indicate the fields and field values that you want to follow by adding field filters on the related object. See Create and Activate Enablement Measures. If you want to add field filters for both the parent object and the related object, the filter logic across all objects is AND (all conditions are met) by default. You can’t set OR or custom logic across parent and related objects. You can’t apply Contains and Does Not Contain filter operators on related object fields.

Working with Custom Objects and Custom Fields

In some cases, measuring the right job-related activity can require a custom object or field, but use caution. If you associate a measure with a custom object or field, and then the custom object or field is deleted, the measure is broken.

Warning Take care when creating other measures that reference a custom object or field installed from a managed package. Uninstalling the package also uninstalls the custom object or field and breaks the unpackaged measures.