Working with Form Settings
Last updated
Last updated
Form Settings allow to set Source object, customize form name, labels, look and feel, buttons and configure form events.
When new Form created user is redirected to the form page with Settings section opened:
Name - Name of the Form in the list of the forms.
Note: Name can differ from the Header which is shown to the user
ID - System Id of the form. Used when you need to refer the form from other places. Value is read-only. The field is not visible when you create a new form and will be displayed after first save.
Description - Just a description, that will be shown only in the builder and list of forms. Not mandatory.
Data Source - Select the object which you want to work with in the current form. When Data Source is selected, all fields from the object will become available for adding to the Form on Data Source Fields section.
Multi Page Form - Check this checkbox if you want to make form look as a wizard with many pages (wizard steps). The page will be visible only if it has at least one non-empty component inside (list, nested from or section with at least one element added).
CSS Styles - Allows to customize form appearance using CSS. Click to show a proper popup. You can customize each component on the form separately and even write own styles for necessary elements, even not for form. Select Component to easily add proper selector to the input text area and add needed CSS rules.
Note: @@
and ##
in the styles builder will be substituted with actual unique prefixes generated by SalesForce for Form and Form container. Do not replace them with hard-coded values because they are not constant.
Show Navigation Panel - this allows to show/hide navigation panel which allows to navigate between forms if you redirect to other form from the current one.
Use Standard FLS Settings - if checked Form will render sObject fields in accordance with Field Level Security settings for the current user's profile.
Field behavior when "Use Standard FLS Settings" turned on:
If field is not visible for current Profile in FLS, it won't be displayed in Data Source Fields form builder section (so it could not be added to the form canvas) and in Form Renderer.
If field was added to the form, and after that Profile got updated so that field is not visible for user, field will be displayed on the canvas in Form Builder, but won't be visible in Form Renderer.
If field is visible but not editable for profile, Form Renderer will display field in read only mode.
Allows to show/hide specified buttons in Edit/View mode of the form.
Also you can customize each button Label.
Select Settings icon next to the button to change the label. Some buttons allow to set additional functionality.
Also you can customize each button Label.
Click Settings icon next to the button to change the label. Some buttons allow to set additional functionality.
Save - allows to add confirmation message on form Save. It allows to specify the following settings:
Label - change text on the button.
Show on edit layout - may be turned off on form that shown with editable fields. Is usable in situations when user wants to override standard Save function with custom actions.
Confirmation message - allows to modify message that will be shown after form saving.
Close - just closes the form without saving changes. Has only Label and Show on edit layout options to configure.
Reset - reverts form fields to values they got from server on from load. Has only Label and Show on edit layout options to configure.
Record View - allows to Open the record which data form is displaying. Has these options to configure:
Label
Show on edit layout / Show on view layout - turn off if no need to show this button on the form in edit/view mode.
Open in New Window - specify if record will be shown in new window or current.
Note: If no record has been passed to the form, the Record View button will not be shown.
Allows to set heading for the form in each mode. By default there are "New Form" texts, you can change it to any necessary. Merge fields are supported here:
Allows to handle the form events.
Click "Add New" button to add event handler.
Events can be executed in different cases:
OnLoad - when the form is loaded
OnBeforeSave - action will be executed when user clicks Save. It will run before the form is Saved.
OnAfterSave - action will be executed when user clicks Save. It will run after the form is Saved.
OnActivate - action will be executed when user navigates between forms using links in Navigation Panel.