ITSM Service Operations Workspace - modifying the homepage donut visualisations

[sol95]

Hi all,

I am attempting to modify the ITSM Homepage donut visualizations without changing any OOTB UX client script includes. ServiceNow have advised that I need to modify or replace the "SowIncidentLandingPageUtils" [sys_ux_client_script_include] which holds all the donut visualisation configuration objects.

In an attempt to create a complete new set of donut visualisations for a Problem oriented landing page I have completed the following steps:

1. Duplicated the Sub-page "Service desk landing page overview SNC" to "Service desk landing page overview SNC COPY"

2. Created a new Client Script Include in the sys_ux_client_script_include table called SowProblemLandingPageUtils

- a. Created in the "Problem Management for Service Operations Workspace" scope

- b. Copied all the code from SowIncidentLandingPageUtilsSNC into SowProblemLandingPageUtils

3. Updated all Client Scripts being utilised by the Sub-page "Service desk landing page overview SNC" by replacing any call to importing SowIncidentLandingPageUtils with the new SowProblemLandingPageUtils.

4. Finally I have updated the order of the Sub-page so the new Sub-page copy loads in the workspace before the initial OOTB one.

5. Save all of that, clear cache (just in case) and then reload the ITSM workspace homepage.

After having completed all these steps I am receiving the following error: 

Uncaught (in promise) Error: Attempted to import undeclared client script include: sn_sow_problem.SowProblemLandingPageUtils

If anyone has any ideas why this is happening please let me know!

Update: Client Script Include needs to be declared in Client Script Include list

 

[Aman Kumar11]

Hello @sol95 ,

Ideally we do not recommend to create copies of sub pages. Rather, the methods of SowIncidentLandingPageUtilsSNC can be overridden in SowIncidentLandingPageUtils to have the custom (Add new, modify existing, remove existing) donuts in place. 

Please mark this response as correct and/or helpful if it assisted you with your question 😊

Regards,

Aman Kumar

[sol95]

Hi @Aman Kumar11 

Thanks for your response. Whilst I understand that SowIncidentLandingPageUtilsSNC can be overridden in SowIncidentLandingPageUtils, we have already made these customizations for the original OOTB landing page. We aren't looking to change that as we are currently using it.

What we are looking for is a complete new set of donut visualiasations for a Problem oriented landing page, hence the steps I have laid out above in order to try and achieve this. Hopefully it goes without saying (but if not) that we need to copy the SowIncidentLandingPageUtilsSNC client script include for Problem because all the client scripts are pointing to the overridden SowIncidentLandingPageUtils and if it is modified for one page it will be modified in all pages that point to it.

Is the solution to go custom? I would still like to utilise the OOTB sub-page and the way that it is setup so that it is consistent and we can maintain it in the same way.

Thanks,

Sol

[Pradeep Thipani]

Hi @sol95 ,

Please find below reference which might help you.

https://incident.do/2023/02/21/adding-a-visualization-to-the-overview-section-of-the-servicenow-serv...

Table: sys_ux_client_script_include

https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/service-operations-...

Thanks,

Pradeep