- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2024 10:09 PM
To determine the impact of setting a field to mandatory,
I would like to know the screen or function that I can check this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 01:32 AM
Hi, making a field mandatory will not have impact as you are concerned.
Only thing can happen if you make a field mandatory now, it will be mandatory for legacy data (records created before you make it mandatory). It is no issue, just to inform you - imagine an example incident form have 1000 records created, now you will make a specific field (e.g. Category) mandatory, it will require being mandatory even for the incidents created before, so if proceeding with the lifecycle it might require additional actions.
But it is nothing to worry from the upgrade perspective. The upgrade is challenging with the scripts, widgets, etc.
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 12:08 AM
@ClayS If a fields become mandatory then a user can't submit a form unless the value in mandatory field is provided.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 12:21 AM
Hello Sandeep,
Thank you for your reply.
But what I'd like to know is system impact like version up errors.
Now I can't tell which field's mandatory settings should not be changed, and how it effects to other fields and functions.
So I'd like to know how to determine that.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 01:23 AM
What do you mean? There is no impact I believe, any field being mandatory is to prevent having garbage/inconsistent data.
Imagine: open an incident where a caller is not mandatory, how would you know whom to contact or whom to send notifications if it is resolved... therefore the field is mandatory and a value is required.
If you want to know how to make a field mandatory, there are millions ways, it really depends on your situation. It can be ALWAYS mandatory at all circumstances, or WITH CONDITIONS - for example incident in New state does not require Close notes, but Incident moving to Resolve it does require that.
Please, try to re-phrase your requirement, it does not seem to be clear
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 01:33 AM
@ClayS wrote:
To determine the impact of setting a field to mandatory,
I would like to know the screen or function that I can check this.
Do you mean how to find out what makes the field mandatory?
There could be several options, first of all - click the right mouse button on the field > Configure dictionary and you will see whether the Mandatory checkbox is marked true (it can be inherited Task > Incident, etc). Another way is to click the Context menu > Configure all and there you can check related scripts and UI Policies:
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2024 09:42 PM
Hello Kamil,
Thank you for your reply.
I would like to determine if there is any impact on the system if I set a mandatory field in OOTB as optional. For example, I am concerned about errors occurring during version upgrades.
Regards.
