- 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-23-2024 10:52 PM
Hello @ClayS,
Mandatory fields ensure that required information is captured before a record can be saved. The impact can be:
- Mandatory fields can block the progression of a record through a workflow if the required information is not provided.
- Mandatory fields can be frustrating for users if they are not clearly communicated or if the fields are not intuitive.
- This can lead to delays and inefficiencies if users are not aware of the mandatory fields or do not have the necessary information to complete them.
For example, mandatory fields on the incident form, including Short Description, Caller, Impact, Urgency, and Category, are essential for creating an incident, as they provide a concise summary of the issue to facilitate better resolution.
If my answer helped you in any way, please then mark it as helpful.
Thank you
Anusha Bonthu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2024 11:59 PM
Question is not clear, can you explain more?
Regards,
Nikhil Bajaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 12:08 AM
Hello Nikhil,
As a system administrator, I would like to fulfill the requests of my employees, such as "I want to change fields that are currently required input,'' or, conversely, "I want to make them mandatory.'' However, I have heard that changing the required fields in OOTB may affect the version upgrade. Therefore, when changing the required settings for a field, I would like to check whether it will affect other functions and to what extent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 05:37 PM
Hi Mirai,
If you are thinking in the way that setting any field mandatory or making any customization will cause any issue during version upgrade then it will not. During Upgrade it will check all your customization and skip all those and will create Skip items. After upgrade you need to work on your skipped items so decide whether you want to go with customization or want to go with OOB behavior. If you will select to go with your customization then your fields will be mandatory even after upgrade but if you will go with OOB then your fields will not be Mandatory. I hope i was able to understand your question and provided best answer. If you want to know something else as well, let me know.
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj