Extension points in Declaritive Actions

cjchalmers
Tera Contributor

Hi all,

 

I was using the links below to add a new button to open a Modal so that a user can choose specific records from a m2m list. The modal works, which is great! 🙂

 

Now I want to filter the records available to the user and since my implementation is based on an existing implementation and extension Point I was looking to copy that code and adapt. In the example we see the extension Point=DEFAULT , the code I want to review is for ENTITY_ELEMENT_FILTER.

 

If DEFAULT & ENTITY_ELEMENT_FILTER are the handles defined within the code, is there a way to search the scripts on these to ensure we review the correct code as easily as possible?

 

1. https://www.servicenow.com/community/next-experience-articles/next-experience-using-extension-points...

2. Next Experience - Using Extension Points in Declar... - ServiceNow Community

2 ACCEPTED SOLUTIONS

Shruti
Mega Sage
Mega Sage

Hi,

For Default extension points, 

Navigate to System Extension points - > Scripted Extension points

Search "RelatedListItemCandidateFilter"

Shruti_0-1753854144944.png

 

 

For ENTITY_ELEMENT_FILTER,

Navigate to System definition -> Script includes

Search "ENTITY_ELEMENT_FILTER'

Shruti_1-1753854252039.png

 

 

View solution in original post

Hi

Navigate to sys_extension_instance.LIST

Create a new entry

Point - global.RelatedListItemCandidateFilter

Class - Select the new script include "ENTITY_BA_FILTER"

Active - true

View solution in original post

4 REPLIES 4

Shruti
Mega Sage
Mega Sage

Hi,

For Default extension points, 

Navigate to System Extension points - > Scripted Extension points

Search "RelatedListItemCandidateFilter"

Shruti_0-1753854144944.png

 

 

For ENTITY_ELEMENT_FILTER,

Navigate to System definition -> Script includes

Search "ENTITY_ELEMENT_FILTER'

Shruti_1-1753854252039.png

 

 

cjchalmers
Tera Contributor

Hi Shruti,

Perhaps you could help with something else in this regard.
The reason I was looking for ENTITY_ELEMENT_FILTER is because I wanted to copy the implementation to apply to a different Use Case.
This filter queries the profile table on a specific class type, element. I want the same functionality but for Business Application (BA). When I use the ENTITY_ELEMENT_FILTER include script and change the query to BA it works as expected. However, when I copy the code and save with a new name ENTITY_BA_FILTER it's as though the filter is not found / not being applied.
Do I have to register this include script code as an extension point somewhere?

Hi

Navigate to sys_extension_instance.LIST

Create a new entry

Point - global.RelatedListItemCandidateFilter

Class - Select the new script include "ENTITY_BA_FILTER"

Active - true

cjchalmers
Tera Contributor

Brilliant, thanks for your help!