Configuration activities for Service Operations Workspace in ITSM

[Subha V]

Refer to the attachment for information about basic and advanced configurations in Service Operations Workspace.

[Vamshi_ch123]

Hi Subha,

Please respond can we able to replicate the event management dashboard to operator workspace? in same format.

[Premnath M]

Hi @Subha V ,

I have installed the Service Operations Workspace ITSM and ITOM plugins. Both plugins were installed in the latest version.

Right now, the ask is:

I am able to see the Service operations Workspace in ITOM view, but unable to see the Service operations Workspace in ITSM view.
Thanks,
Premnath M

[Matteo11]

Hello @Subha V.
This guide does not fully work on UTAH.
I tried to follow the guide in order to "Add a data visualization donut component for the landing page" beginning on Page 40. The Landing page has changed significantly from the explained version. There is no "Viz carousel" component anymore (as described on page 43) and it's been replaced by a Repeater component having 1 Carousel component, that is controlled by some Data Source (via Client State params and Client Script).
I did not find the solution on the new approach with the Repeater yet.

Is there any updated document for this for UTAH? And since SOW will be more and more significant, are there any plans on integrating those configuration steps in the official docs/nowcreate?

[Matteo11]

I found the solution for my issue to add a new donut to the Landing Page of SOW. For configuration of the Landing pages in UTAH, follow this guide: https://docs.servicenow.com/bundle/utah-it-service-management/page/product/service-operations-worksp...

You need to be a bit careful with the code though. For example, i wanted to add IncidentSLAs to the 2nd Tier Landing page. So i copied the following code (as stated in the docs) and added it:

This will lead to the donut not rendering. The issue is the line "evamId", where it used a constant "evamDef", which is not defined. In the end i had a look into the code of UX Client Script Include "SowIncidentLandingPageUtilsSNC" and found this line:

In the manner of all the other configurations, I just hardcoded the sys_id.

Hope that helps 🙂

[Bradley Marin]

Does anyone know how to change the table that the card view renders from by default? Currently it loads incidents upon page loads but I'd like to change this to universal requests. I've tried changing the first donut to universal requests and it still renders incidents first in the card view below.

[teduard]

hi @Subha V 
could you please advise SowIncidentLandingPageUtilsSNC ux client script is different between instances?
In mycase I am not sure why, but DEV and QA (UAT) differ from each other as seen below
at first glance same plugins are installed
thanks!

  

[PaulSylo]

I did the same, but this not works when i switch between my work and my Team work drop down. @Matteo11  @Subha V 

[Chris Shakespea]

To answer a few of the questions

1) Ideally, the information included in the guide will be integrated into docs. Providing in this format allows us to deliver it quickly and get feedback

2) What landing page you see is governed by the audience. See section 2.7

3) The document was written for SOW v5.0+.  There are configuration differences to earlier versions e.g. use of EVAM on some landing page components.  So check not just the family release but the release of SOW you are working on.

[Tclar]

ok