About Predefined Values in Actions

When you configure action layouts, it’s better to use fewer fields. Most users, especially mobile users, don’t like to fill in a lot of required fields. They want to get things done and move on to their next task. A good way to use fewer fields in action layouts is to set predefined values for as many fields as possible. The more fields you can set predefined values for, the more you can remove from the layout and make the action easier and quicker to use. Balance ease of use with the need for required information. However, don’t remove required fields from an action layout without setting a predefined value for those fields, or when a user applies that action, the record won’t save properly.

If you set predefined values for fields on object records created through an action, you don’t need to add those fields to the action layout. For example, when you configure an action that lets users create opportunities, set Prospecting as the predefined value for the Stage field. All new opportunities users create through that action are automatically assigned to the prospecting stage. You can remove the Stage field from the action’s layout, because the field is going to be assigned a value automatically.

Predefined values for fields on actions are different from default values that you can set for fields on records. If a field is included in an action, it can have both a predefined value set for the action and a default value set. If a field on an action has both a predefined value and a default value set, the action uses the predefined value, not the default value.

Let’s set a predefined value for one of the fields on our Create a Case action.