> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/forms/basics/working-with-form-settings.md).

# Working with form settings

Form Settings allow to set Data Source Object, customize Form name, labels, look and feel, buttons and configure form events.

When [new form created](/forms/basics/how-to-create-a-form.md) user is redirected to the Form Builder page with Settings tab selected:

![](/files/bf0a8eb9dd1db44cccefe19c801827bf7fd0ad1a)

## General settings

* **Name -** Name of the Form in the list of forms.

{% hint style="info" %}
Name is not the same as Form Header which is shown to the user.
{% endhint %}

{% hint style="warning" %}
Do not forget to go to "Header Configuration" section and set up form headers for all modes.
{% endhint %}

* **ID -** system Id of the form. Used when you need to refer the form from other places. Value is read-only and becomes populated after form has been saved first time and reloaded in builder (so, this field is not shown yet when you just creating a form).
* **Description** - give a description to form. Not mandatory.
* **Data Source Object** -select the object which you want to work with in the current form. When Data Source selected, all fields from the object will become available for adding to the Form on Items Tab.
* **Multi Page Form** - check this checkbox if you want to have many pages on the form (in this case form will look as wizard). The page will be visible only if it has at least one visible component inside. Starting release 8.4 Multi Page form is also can be represented as a [tabbed](/forms/basics/making-multi-page-form.md) form, not as a wizard:

  ![](/files/a036249cec1a0335ac2085957508615661892bcf)
* **CSS Styles -** Allows to customize form appearance with 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, see it's selector in the right input field, and click "+" button add CSS selector to the main area. Then write CSS properties inside of curly brackets:

  ![](/files/71c824cf751a0d60487a729ff5b19a6e975f2339)

  <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><code>@@</code> and <code>##</code> 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. They are needed to make styles affect only the current form and container - this makes sense to avoid affecting one form with styles of another (e.g., when there are nested forms used, navigation to other form is configured, or more than one form on the page are shown).</p></div>
* **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.

  ![](/files/f75cd950886e99582e7952dcfd6bea60a6b5d92f)
* **Save Form on Proceed Step -** if checked Form will be saved when user clicks Proceed on Step.
* **Save Form on Proceed Issue -** if checked Form will be saved when user clicks Proceed on Issue.
* **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 the Field Level Security settings, 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.

## Buttons configuration

Allows to show/hide specified buttons in Edit/View mode of the form and change some their properties.

![](/files/682a7451a935948d076c2759512506d0af4d7d99)

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.
* **Ignore Permissions** - will ignore user permissions related to record update.
* **Disable Validation** - allows to ignore all specified [validation rules](/forms/form-components/components-validation-rules.md) on this form elements.
* **Extended fields** - allows to specify extended fields (fields to be passed and saved in spite of their absence on the form).

![](/files/48493627797fbd8f2b3936fdae1ef5d529dbbbb3)

### 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** - may be turned off on form that shown with readonly fields. Is usable when no need to show this button.
* **Open in New Window** - specify if record will be shown in new window or current.

{% hint style="info" %}
If no record has been passed to the form, the **Record View** button will not be shown.
{% endhint %}

### Go to Dashboard

Opens the Work-Relay Task Manager Dashboard and shows layout for current task/step. Has **Label**, **Show on edit layout** and **Show on view layout** options to configure.

## Header configuration

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:

![](/files/eb08fac8f146076dcdc53fa9d2618d965e5e14a5)

## Events

Allows to handle the form events.

Click "Add New" to add event.

![](/files/a99f79688629d7debbf9fdfb19c5e7364f827146)

Events can be executed in different cases:

* **OnLoad -** when the form is loaded
* **OnBeforeSave -** action will be executed when user clicks Save or Proceed (if Save on Proceed selected). It will run before the form is saved.
* **OnAfterSave -** action will be executed when user clicks Save or Proceed (if Save on Proceed selected). It will run after the form is saved.
* **OnActivate -** action will be executed when user navigates between forms from Navigation Panel.