Mandatory custom fields: Difference between revisions
From Planfix
No edit summary |
m (Aliona moved page Required custom fields to Mandatory custom fields) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
|description=Mandatory custom fields | |description=Mandatory custom fields | ||
}} | }} | ||
Task, contact, and project [[Custom fields|fields]] can be set to ''' | Task, contact, and project [[Custom fields|fields]] can be set to '''Mandatory'''. This can be done when editing the object: | ||
https://pic.planfix.ru/pf/Wq/WONBmO.png | https://pic.planfix.ru/pf/Wq/WONBmO.png | ||
We find the desired field in the left-hand panel and open its settings by clicking the three dots. Then we click the checkbox next to ''' | We find the desired field in the left-hand panel and open its settings by clicking the three dots. Then we click the checkbox next to '''Mandatory''': | ||
https://pic.planfix.ru/pf/HT/bT1Hwe.png | https://pic.planfix.ru/pf/HT/bT1Hwe.png | ||
| Line 18: | Line 18: | ||
You won't be able to save the task, project, or contact without entering a value for these fields. | You won't be able to save the task, project, or contact without entering a value for these fields. | ||
== | ==Mandatory system fields== | ||
*As of April 2019, system fields in tasks, projects, and contacts can also be | *As of April 2019, system fields in tasks, projects, and contacts can also be mandatory fields. | ||
*The steps for making a system field | *The steps for making a system field mandatory are the same as for a custom field. | ||
==Important== | ==Important== | ||
*The requirement to fill in a field is configured at the template level for tasks or contacts that determine the system object type. Therefore, the same field can be mandatory for one object type and optional for another. For example, the "Address" field can be optional for a customer inquiry but mandatory for a delivery order. | *The requirement to fill in a field is configured at the template level for tasks or contacts that determine the system object type. Therefore, the same field can be mandatory for one object type and optional for another. For example, the "Address" field can be optional for a customer inquiry but mandatory for a delivery order. | ||
Latest revision as of 13:16, 26 December 2024
Task, contact, and project fields can be set to Mandatory. This can be done when editing the object:
We find the desired field in the left-hand panel and open its settings by clicking the three dots. Then we click the checkbox next to Mandatory:
When creating or editing a task, project, or contact, required fields will be marked with a red asterisk:
You won't be able to save the task, project, or contact without entering a value for these fields.
Mandatory system fields
- As of April 2019, system fields in tasks, projects, and contacts can also be mandatory fields.
- The steps for making a system field mandatory are the same as for a custom field.
Important
- The requirement to fill in a field is configured at the template level for tasks or contacts that determine the system object type. Therefore, the same field can be mandatory for one object type and optional for another. For example, the "Address" field can be optional for a customer inquiry but mandatory for a delivery order.