Redefining a Signal

Suppose that you decide that the insights and rules based on the custom signal you have created need to look up a different custom field. You can implement this change without the need to alter any of the insights or rules.

Instead, simply clone and adjust the signal definition:

1. In Setup, go to Custom Metadata Types.

2. You should see two Max custom metadata types:

   Class encapsulates your existing Max knowledge domains.

   Signal contains the individual signal definitions that already exist in these knowledge domains.

3. Click Manage Records beside Signal.
4. Click Edit for the signal record that you want to redefine.
5. Deselect the signal definition's Enabled check box. When the signal definition is deactivated, you can replace it.
6. Click Save.
7. Open the signal record that you just disabled by clicking its Label value.
8. Click the Clone button.
9. Select the clone's Enabled check box.
10. In the cloned version, leave the unique name in the Mapping field unchanged. This ensures that all the insights and rules that previously pointed to the deactivated version will now point to this version.

11. In the cloned version's Map To field, specify the API name of the custom field that you want to inform the Max signal.

    Make any other necessary adjustments (such as updating the Description field).

    In the example shown below, the signal is now informed by the 'Top Priority' custom field. Previously it was informed by the 'Critical Win' custom field.



12. Click Save.

The cloned signal definition is now in place, and the old version is deactivated.

• The unchanged Mapping name means that insights and rules point to this version.
• The updated Map To name means that the signal value is now provided by the newly entered custom field.