Create implementation of a Scripted Extension Point in EAP

Freigeben Version: Australia

Aktualisiert 12. März 2026

1 Minute Lesedauer

Update the default Scripted Extension Point or create a scripted extension point using the default one as a template to filter the data displayed on the EAP dashboard.

Vorbereitungen

Associate the EAP read-only role to the dashboard.

Role required: sn_apw_advanced.eap_admin

Warum und wann dieser Vorgang ausgeführt wird

The Scripted Extension Points enable you to create a custom query to filter the information from different data sources. By default, each EAP configuration is associated with an extension point. Each extension point handles all the team types associated with it. You must create an implementation of the scripted extension point every time you create a new EAP configuration.

Wichtig:

Perform this task only for a custom configuration or if you want to customize a default dashboard. This task is not required if you are using any of the default configurations.

Prozedur

Navigate to All > Scripted Extension Points.
Search for and open the EAPDashboardsEncodedQueryProvider (sn_apw_advanced.EAPDashboardsEncodedQueryProvider) scripted extension point.
Select the Create implementation related link to create an implementation of this scripted extension point.
The new implementation record form is shown.
Update the Name field of the newly created Implementation to a custom name of your choice.
Ensure that you don't include any spaces in the name. For example, rename the implementation to MyConfigEAPDashboardsEncodedQueryProvider.
Select Update.
Open the EAPDashboardsEncodedQueryProvider (sn_apw_advanced.EAPDashboardsEncodedQueryProvider) scripted extension point.
From the Implementations related list, click the Class of your newly created implementation record to open it.

Update the Script field to include the following.

In the getConfigId function, enter the sys_id of your EAP configuration.

In the fetchEncodedQueries function, enter queries to filter the information for each level of your EAP configuration such as iteration ID, team type, and team ID.

The following is an example script for the default Large Solution Configuration.

fetchEncodedQueries: function(teamType, teamId, iterationId) {
        switch (teamType) {
            case "sn_apw_advanced_agile_team":
                return {
                    rm_story: `iteration=${iterationId}`,
                    sn_apw_advanced_eap_iteration: `sys_id=${iterationId}`,
                    sn_gf_goal_m2m_relationship: `table_name=sn_apw_advanced_eap_iteration^entity_id=${iterationId}`,
                    sn_apw_advanced_eap_iteration_db_view: `iter_eap_team=${teamId}`
                };
            case "sn_apw_advanced_agile_release_train":
                return {
                    sn_align_core_feature: `iteration=${iterationId}`,
                    sn_apw_advanced_eap_iteration: `sys_id=${iterationId}`,
                    sn_gf_goal_m2m_relationship: `table_name=sn_apw_advanced_eap_iteration^entity_id=${iterationId}`,
                    sn_apw_advanced_eap_iteration_db_view: `iter_parent=${iterationId}`
                };
            case "sn_apw_advanced_solution_train":
                return {
                    sn_apw_advanced_eap_iteration: `eap_team.parent=${teamId}`,
                    sn_align_core_capability: `eap_team=${teamId}^OReap_team.parent=${teamId}`
                };
            default:
                return {
                    sn_align_core_eap_planning_item: `iteration=${iterationId}`,
                };
        }
    },

    getConfigId: function() {
        return "e4e11e0977243110740fefc0aa5a99f9";
    },

Update.

Ergebnisse

The next time you reload the Home tab for your EAP teams, the dashboard shows the filtered data according to the updates you made to the implementation.