- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 01:19 AM
Hello,
I'm encountering an issue when trying to create System Properties within a custom application scope in our ServiceNow development instance.
When I try tto create a new property(sys_properties) on the form—the "Name" field is both blank and read-only. This prevents me from creating the property , effectively blocking the creation of any new system property in the Custom scope. This issue does not occur in the global scope, where I can create and name system properties as expected.
This restriction is currently impacting our ability to define environment-specific configurations or control feature flags within Custom scopes.
Is there a known workaround or a configuration setting that would allow property creation within scoped applications?
Thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 09:25 AM - edited 05-12-2025 09:31 AM
this is OOTB platform behavior when you create system property in scope.
1) if you are in scoped app, name field is read-only and you only enter suffix, name field gets auto populated with the scope name and suffix
2) if you are in global scope then name field is editable as there is no concept of scope prefix etc
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 09:33 PM
This is the expected out-of-the-box (OOTB) behavior of the platform when creating a system property within a scoped application.
While in a scoped app, the Name field is read-only — you only need to enter the suffix, and the system automatically prefixes it with the application scope (e.g., scopedapplication.suffix).
Whenever you reference this property, be sure to use the full Name field format: scopedapplication.suffix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 09:25 AM - edited 05-12-2025 09:31 AM
this is OOTB platform behavior when you create system property in scope.
1) if you are in scoped app, name field is read-only and you only enter suffix, name field gets auto populated with the scope name and suffix
2) if you are in global scope then name field is editable as there is no concept of scope prefix etc
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 08:16 PM
Hope you are doing good.
Did my reply answer your question?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2025 06:25 AM
Thank you Ankur, it helped
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 09:33 PM
This is the expected out-of-the-box (OOTB) behavior of the platform when creating a system property within a scoped application.
While in a scoped app, the Name field is read-only — you only need to enter the suffix, and the system automatically prefixes it with the application scope (e.g., scopedapplication.suffix).
Whenever you reference this property, be sure to use the full Name field format: scopedapplication.suffix