{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1250,"path":"api-reference/web-services/create-scripted-ext-pt.md","title":"Create a scripted extension point","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a scripted extension point\n\nCreate a scripted extension point that can be placed in a script include in the base application code. By placing the scripted extension point, you designate the specific location in the application code where data or objects can be sent to a customization and where data is returned.\n\n## Before you begin\n\nRole required: You must have the specific role for the developer or administrator of the application, or you must have the admin role.\n\n**Note:** To learn about application-specific administrator roles and delegated development, see [Access control rules in application administration apps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/ACL-access-checks.md) and [Delegated development and deployment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/c_DelegatedDevelopment.md).\n\n## About this task\n\nDefine the content and structure for an extension point. This definition should describe how a customization should be structured, how it interacts with the application code, and how the data that is returned by a customization at the extension point is processed.\n\nBy creating a good definition, you provide a structure for the extensions.\n\n## Procedure\n\n1.  Navigate to **All** > **System Extension Points** > **Scripted Extension Points**.\n\n2.  Click **New**.\n\n3.  On the form, fill in the fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Name|Unique name for the extension point. The name can be up to 100 alphanumeric characters, including special characters.|\n    |API Name|Name of the extension point API that is pre-pended with the application scope to which it applies. This is a system-assigned name and cannot be changed.|\n    |Application|Application scope against which the extension point is assigned. This is system-assigned and cannot be changed. For more information about the protections that are offered by the use of scoping, see [Application scope](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/c_ApplicationScope.md).|\n    |Restrict to this scope|Option for restricting the extension point to the application scope only.|\n    |Description|Requirements for the custom script include, such as how the UI script should be structured and how it should operate with the application code.|\n    |Example|Example of how a custom script include that interacts with this extension point should be structured so it operates with the application code.|\n\n4.  Click **Submit**.\n\n\n**Parent Topic:**[Creating and adding a scripted extension point](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/impl-scripted-ext-pts-base-code.md)\n\n"}}