The Admin at Universal Containers recently created a new custom field referenced on the Target Field on a Price Action in a Price Rule. While testing the Price Rule, the Admin noticed that the Price Action failed to

populate the custom field. The Admin checked the CPQ Package Setting and noticed that the Triggers Disabled checkbox was checked. After unchecking Triggers Disabled, the custom field still failed to populate.

How can the Admin ensure this custom field can be referenced by the calculator?