---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Add a client extension point in the base application code

# Add a client extension point in the base application code {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add the UI extension point into a UI script in the base application code. To add the
extension point, place an API call that identifies the location at which registered custom
artifacts execute.

## Before you begin

You must first create a UI extension point before you can add it to a UI script in the application code.Role required: admin or the specific role for the developer or administrator of the application  
Note:  
To learn about application-specific administrator roles and delegated development, see [Access control rules in
application administration apps](https://www.servicenow.com/docs/access?context=ACL-access-checks&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US) and [Delegated development and
deployment](https://www.servicenow.com/docs/access?context=c_DelegatedDevelopment&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US).

## Procedure

1. In the application code, access the existing UI script that you want to add a scripted extension point to, or create a new one.  
   To learn more about creating UI scripts, see [UI scripts](https://servicenow-prod.fluidtopics.net/wRIgGGLtuNffgOnKwS5uEw#c_UIScripts "UI scripts provide a way to package client-side JavaScript into a reusable form, similar to how script includes store server-side JavaScript. Administrators can create UI scripts and run them from client scripts and other client-side script objects and from HTML code.").
2. In the UI script, add a line of code at the location that you expect to collect and process the custom UI script output.  
   The code must contain the `getExtensions` command that identifies the client extension point against which the custom UI scripts are registered. This line of code is similar to what is in an application code
   script include for scripted extension points. For an example, see [Add a scripted extension point in the base application code](https://servicenow-prod.fluidtopics.net/Pgrswx_AxR1atecTIG6XOg "Add the scripted extension point into a script include in the base application code. To add the extension point, include an API call that identifies the location at which registered custom artifacts execute.").
{#add-client-ext-pt-base-code-ui-script__steps_mfs_mgn_pdb}