Required contract custom fields
To download the document in PDF format, click here
Required contract custom fields
In Lease, the administrator manages custom fields.
There are two kinds of custom fields in Lease:
- the Entity custom field
- the Contract custom field
The new functionality introduced by the April 2020 release relates to the Contract custom field.
Application of a required contract custom field
This explanatory note provides you with the instructions to apply and understand the notion of required custom field in Lease.
Repository
Creation of a required custom field
In the Lease repository (as illustrated in the screenshot below), the field is created via the “Champs personalizes” (Custom fields) menu, and then the “Contracts de location” (Lease contracts) sub-menu.
The button lets you create a new custom field.
Note: It’s important to remember what the different types of fields mean:
- Boolean => YES or NO switch
- Alphanumeric => Free text field up to 256 characters
- Date => Choice from a calendar
- List of Values => Choice from the values maintained by the administrator
The notion of required field when inputting a contract will be managed in this area, which should be checked or left unchecked.
Note:
Activating this choice will invalidate contracts for which the field has not been input. If the field has been input, there will be no effect on the contract.
The field will be positioned in one of the 4 zones available in order to be able to complete it in the contracts. This choice is made via the position menu.
Update of an existing field
This new functionality also lets you modify the settings of existing custom fields so as to make them required or not required.
For this, the administrator performs the following actions:
In the Lease repository (as illustrated in the screenshot below), a field is modified via the “Champs personnalisés” (Custom fields) menu, and then the “Contrats de location” (Lease contracts) sub-menu.
The custom field should be opened.
The notion of required field when inputting a contract will be managed in this area, which should be checked or left unchecked.
Note:
Activating this choice will invalidate contracts for which the field has not been input. If the field has been input, there will be no effect on the contract.
The following message must be confirmed to make the field a required field.
Effect on the contracts
On “unvalidated” contracts
Below is an extract of the Contrathèque (Contract library) before the activation:
After the required notion is activated, a “comptabilité incomplete” (accounting incomplete) alert is set up to warn the user that a field required for the contract is missing.
You can see the reason for the alert by hovering over the alert icon.
The user must input the field to cancel the alert.
The field to be input is identified by an asterisk and the note “Champs requis” (Required field), as shown in the screenshot below.
Note that a custom field can be imported. In this case, see the explanatory note “How do I import custom fields to my Lease contracts?”.
On “validated” contracts
Below is an extract of the Contrathèque (Contract library) before the activation:
After the required notion is activated, a “comptabilité incomplete” (accounting incomplete) alert is set up to warn the user that a field required for the contract is missing.
The contract that was “validé” (validated) has been invalidated by the administrator’s action.
You can see the reason for the alert by hovering over the alert icon.
The user must input the field to cancel the alert.
The field to be input is identified by an asterisk and the note “Champs requis” (Required field), as shown in the screen shot below.
Note that a custom field can be imported. In this case, see the explanatory note “How do I import custom fields to my Lease contracts?”.