catalog task templates are not editable after upgrade to yokohama servicenow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2025 11:59 PM
catalog task templates are not editable after upgrade to yokohama servicenow version
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-23-2025 04:06 PM
Maybe the write permissions were granted by ACLs that have no roles (which in Yokohama are no longer valid)?
Yokohama places new restrictions on ACLs to be valid and not-valid ACLs - as expected - no longer grant access.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-11-2025 01:11 PM
I found this via Copilot
It looks like the Yokohama release of ServiceNow introduced changes that are affecting how Templates work with Catalog Tasks, particularly around field selection and editability.
What Changed in Yokohama
Stricter ACL Enforcement:
- In Yokohama, Access Control Rules (ACLs) that do not have roles assigned are now considered invalid.
- This means templates that previously worked (but relied on ACLs without roles) may now fail silently or not populate fields as expected
Templates Not Editable or Not Applying:
- Users have reported that Catalog Task templates are not editable or do not populate fields after the upgrade
- This includes fields like Short Description, Assignment Group, or Due Date not being set when a template is applied.
Standard Change Templates Also Affected:
- Similar issues are seen with Standard Change Templates, where fields are not being populated post-upgrade
What You Can Do
1. Check ACLs on Affected Fields
- Go to System Security > Access Control (ACL).
- Search for the field/table (e.g., sc_task.short_description).
- Ensure the ACL has a valid role assigned.
- If it doesn’t, the ACL is now ignored in Yokohama.
2. Test with Elevated Role
- Temporarily elevate to security_admin.
- Try applying the template again to see if it works.
- If it does, it confirms a permissions issue.