🤖 This article was translated by AI.
🚨 Please note
This feature is available for customers subscribed to an Advanced, Enterprise, or Business plan.
If you want to learn more about these plans, you can visit our website and contact us at [email protected] to discuss with our teams.
In Short
Entry rules make a field mandatory on your records. A rule applies to all records in the module, or only to certain states, types, or Agencies. As long as a required field is empty, saving is refused and Boond indicates which field to fill in.
Relevant modules: Candidates, Resources, Opportunities, Positionings, Contacts, and Companies.
For the administrator: they choose the field to make mandatory and, if desired, limit the rule to certain states, types, or Agencies.
For users: the record displays its required fields, and saving is refused as long as they are empty.
In the module lists view: a filter and a column help you find records with empty required fields.
Before You Start
To create, edit, or delete a rule, you need two permissions:
access to Administration;
the "Entry rules" right, to be assigned to roles that will manage the rules.
Without the "Entry rules" right, the entry does not appear in the administration. Once created, a rule applies to all users, regardless of their profile.
Create and Manage a Rule
You manage rules from Administration > Customize > Entry rules. The screen shows required fields by state, module by module.
Create a Rule
A rule answers three questions: which field to require, on which records, and from when.
Click "New rule": the window will ask these questions in order and summarize the rule as you proceed.
1. The field: what you require.
Choose the module and the field your teams must fill in. For example, a candidate's email or the Daily Sale price of a positioning. A rule applies to only one field per module. If you want to require three, you must create three rules.
2. The perimeter: the records concerned.
If needed, limit the rule to certain states, types, or Agencies. These three criteria are optional and can be combined. A precise perimeter avoids blocking too early: with a rule limited to the Qualified state, a newly spotted candidate can be saved without an email. If you select nothing, the rule applies to all records in the module.
Note
The type choice does not exist for Companies or Positionings, as the type comes from the Opportunity.
3. The requirement: from when.
The "Ignore when creating a record" box decides when the field becomes blocking.
Box checked (default): your teams can create the record without this field, then fill it in when the information arrives. It is checked on subsequent saves.
Box unchecked: the record cannot be created without this field. Reserve this choice for information that is essential from the first contact. The box is only offered for fields in the creation form, and never for Positionings, which do not have one.
4. The reason: why the rule (optional).
Explain in one sentence why this field matters. For example, "Without an email, it is impossible to send a mission proposal to the candidate."
The reason remains attached to the rule: another administrator will understand it before editing or deleting it. Your users see it in the required fields panel, by hovering over the question mark next to the field.
5. The summary: your final check.
Before saving, the window summarizes the rule in one sentence (gray section). For example, "On Candidate records in the states In process, Top profile of all types in all Agencies, the field Email 1 becomes required after creation". This is exactly what your teams will have to follow: review it, then click "Create". The window also shows how many records in your perimeter are already concerned: they will be marked after the next recalculation.
Edit or Delete a Rule
Click on a field label to open its rule for editing.
Delete the rule with the "Delete" button in the same window. Boond will ask you to confirm.
If you have access to the "Activity log" right, the "Activity log" link at the bottom of the screen opens the rule history.
Reading the Screen
The Module filter at the top of the screen selects the displayed module and shows the number of rules for each.
Each line displays the state and required fields in that state. States are shown in the order set in your global settings. A rule set for three states appears on three lines. The label also specifies when the control occurs, for example "on save".
The line "All states" groups rules valid in all states.
The type and Agency of a rule are not shown on its label. You must open the rule to see them.
When a Rule Applies
A rule blocks as soon as it is saved. It does not modify your existing records: a record with an empty required field remains viewable and is checked at its next save, as described below.
Only the status of records awaits an update after each rule creation, edit, or deletion:
An "Update in progress" banner appears at the top of the Entry rules screen. It lists the modules whose records are not yet up to date.
The banner disappears for a module as soon as all its records are up to date. Allow up to 48 hours.
During this time, the required fields panel on the record already displays the new rule, and the header alert shows "unsynchronized record".
The Statuses of a Record
Status | What it means |
Missing required fields | At least one required field for this record, based on its state, type, and Agency, is empty. |
Required fields filled | All required fields for this record are filled. |
During the update, the displayed status may not yet reflect the latest rule change.
On the Record
The record shows required fields before any refusal, in three places: the header, the required fields panel, and the form. Only the fields you see are listed and counted.
In the Header
Next to the record name, an alert shows the number of required fields still empty, for example "2 required fields".
When all are filled, it displays "Required fields completed".
It remains visible on all tabs. Click it to open the required fields panel.
In the Required Fields Panel
The panel opens on the current state of the record. It lists the required fields in that state: a padlock signals an empty field, a checkmark a filled field.
The arrows display the other states, in the order of your global settings. This way, you know what the next state will require.
The panel informs without blocking: the check is done on save.
In the Records
On the displayed tab, required fields for the record are labeled "required", like other mandatory fields, and are highlighted as long as they are empty.
At the top of the Information tab, a banner also lists the record's empty required fields.
The marking appears as soon as the tab is opened, whether the field is filled or not.
On the creation form, only fields required at creation are marked.
The marking follows the record's saved state, type, and Agency. If you change one in the record, it updates after saving.
When Saving Is Refused
Boond refuses to save when a required field is empty. The fields checked depend on what you do.
What you do | Fields checked | The panel opens on |
Save a tab without changing state | The required fields of the record present on this tab and visible to you | The current state |
Change the record's state | All required fields of the target state, on all tabs, even those you do not see | The target state |
When creating a record, only fields required at creation are checked. Others are checked from the next save.
What You See
A message indicates that saving failed.
The required fields panel opens on the state indicated in the table.
In the record, empty required fields are marked as errors. Provider and Service are exceptions: without an area on the screen until you add one, they are only indicated in the panel.
After a refusal, the state selector keeps the state you chose, without saving it.
To unblock, fill in the indicated fields then save again. You can also cancel your change or revert to the previous state.
Wherever You Edit a Record
The same rules apply wherever you save from:
Quick edit from the Overview: same behavior, as soon as you validate.
Kanban views: a refused state change displays the message "One or more fields are required".
Bulk actions: refused records appear in the list of unchanged records, without details of missing fields.
Changing the state of an Opportunity: if you also update its Positionings, those with empty required fields keep their state, and a message notifies you.
Boond Pulse, mobile app, and API: saves are checked in the same way.
Find Records in Lists
In the lists of the six modules, the "Entry rules" filter and the "Required fields status" column show you records with empty required fields.
The "Entry rules" Filter
It replaces the old "Validation" filter and offers two values: "Missing required fields" and "Required fields filled".
It takes into account all required fields of the record, including those hidden by your rights.
It is independent of the record quality percentage.
It does not filter by rule or field.
The "Required fields status" Column
Add it from the column configuration, like other list columns.
It indicates for each record if required fields are missing or filled.
You can filter the list from the column.
Your Saved Searches
Those using the old "Validation" filter continue to work.
Those using the value "Partially filled records" open without this criterion, as this value no longer exists.
Current Limitations to Know
Entry rules check that a field is filled. They do not judge what is entered.
Fields: only native fields of the six modules are available. Custom fields are not.
Requirement: only one level exists, Required. A rule does not check for a minimum amount or a minimum number of values.
Perimeter: a rule can be restricted by state, type, and Agency. It does not target a profile, business unit, or expertise area.
States: a field required in one state is not automatically required in subsequent states. Add these states to the rule's perimeter.
Rule management: a rule cannot be suspended or duplicated. To stop it, delete it.
State selector: it does not signal in advance the states with missing required fields. Check the required fields panel before changing state.
Converting a candidate into a resource: it is not blocked. The resource's rules apply at its first save.
Other modules: projects, deliveries, invoices, and other modules do not have entry rules.
FAQ
How many rules can I create?
As many as needed: there is no limit to the number of rules.
Can I require a field for only one Agency?
Yes. Select this Agency in the rule's perimeter. The field remains optional for records in other Agencies.
Can a user be blocked by a field they cannot see?
When saving a tab without changing state, fields the user cannot see never block them.
What happens to my existing records when I create a rule?
They remain as they are. Their next save is checked. To find them, filter the list on "Missing required fields".
What is the link with the record quality percentage?
None. The quality percentage does not take entry rules into account, and the Entry rules filter does not take the quality percentage into account.
A field is required by a rule and recommended for record quality. How is it displayed?
As a required field: required takes precedence.
Do my task lists change?
No. They are configured and checked as before. They do not block saving and do not appear in the required fields panel.