Record is saved without providing mandatory fields
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2025 06:57 AM
Hello,
Can anyone please let me know the exact answer i searched in community and googled it but i didn't find it.
I have a few change requests, for them Ctasks are created. Ctasks records belong to change_task table, these records are closed without providing mandatory fields. These mandatory fields are still editable but rest all are readonly and record is in closed state. What might be the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2025 08:06 AM
Hi @srikanthsan
It might be a cache issue. Is this happening in your PDI?
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2025 08:33 AM
it sounds to me that it might be edited in a list view and the mandatority is applied via client script, similar use case. Please verify this or check how is the mandatory set - ui policy (soft) or data policy (stronger)
/* 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
07-23-2025 08:44 AM
There are a few possibilities that might cause these records to be closed without the mandatory fields being filled:
1. Script Execution: These records may have been closed by a script. There could be a fixed script, background script, or scheduled job that executed incorrectly, resulting in the closure of these records.
2. Form-Level Validation: If you are using form-level mandatory field validation, the user might have updated the state field from the list view, which could lead to this issue.
Please validate how mandatory field validation is occurring in your instance. Consider implementing data policies to prevent this type of issue in the future. Additionally, reviewing the logs for any script executions or user actions that coincide with the closure of these records may provide further insights.
If this solution helps you then, mark it as accepted solution ✔️ and give thumbs up 👍!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2025 08:54 AM
NO script is used, record is closed within 2 minutes of creation by user and form level editing is restricted for user.