While adding custom fields to forms, users are prompted to declare the properties of fields. Let us discuss each property in detail.
Properties of fields
Field title is the actual title used to identify a field across forms.
Label of the field to be displayed in the form. Field labels vary with each form.
- When a hiring form is created, a custom field titled Name can be labelled, Candidate Name . When the same field is used in a different form, the label can changed to First Name or Last Name .
- While field titles are generic, field labels can be more specific to resonate the form.
- Field title or label, once used cannot be reused in any other forms.
Predefined value of the field. This value gets pre-filled in the form. It can be overwritten while creating or updating a card.
Mandatory fields must be filled before the form can be submitted. Enable the button to make the field mandatory to collect any required information from the user.
You can choose to hide fields from users when they create new cards. However, the user might be able to view this field in the card details page, depending on their set privilege.
For example, the hiring status will not be available while initiating the recruitment. Hence, it will be much relevant to hide the Hiring status field while creating a new card. However, once the result is available after evaluation, it can be recorded in the Hiring status field available in the card details page. You can also choose to hide this field entirely from certain user profiles by setting privileges.
To manage the visibility of any field, toggle and enable the corresponding button.
A mandatory field cannot be made invisible.
Here is a detailed post
to understand field-level permissions in Qntrl.
Field Encryption or PHI
Confidential user data, like the financial details of an organization, or PHI (Protected Health Information) like health records or medical histories can be kept secure using the Encrypt option. Encryption converts your text into a cipher (non-readable text), which can be accessed only by authorized users. Only the encrypted values of the field will be saved in the database. Toggle the button to enable encryption for a field.
- Users with the Admin profile or other profiles with valid permissions will be able to decrypt the fields and view the information.
- Encrypted fields can only be used to set criteria as 'Is' or 'Is Not'.
- You can only encrypt a maximum of 10 fields in an organization.
- When encryption is enabled, the field will be encrypted across all forms.
- The field types which support encryption are: Single-Line, Date, Decimal, Integer, Email Address, Link, and Currency.
Personal or confidential user data can be hidden from the interface by masking the values with asterisks (*). This can be used to hide sensitive details, like a social security number, credit card number, security questions, and so on. Masked fields will not be encrypted but merely hidden with asterisks . If you wish to mask a field, toggle and enable the corresponding button.
If a field’s Mask classification is turned off in a form, the field will no longer be masked in other forms also.
The field types which support Mask are: Single-Line, Multi-Line, Date, Decimal, Integer, Email Address, Link, and Currency.
- Field values will not be masked when displayed during transitions.