New section on Overview tab Service Operations Workspace

[Enrique Avello]

Hello all,

I am trying to add a new Section on the Overview Change page for Service Operations Workspace.

Going through the  Service Operations Workspace Admin Center I see the Change Overview Containers having one for each state to configure which sections are visible in each state

When I open one I see a list of Change Overview Cards which seem to be the different sections... but if I want to create a new one... I only get a set of names already defined (Tasks, Summary, Impact...) I do not see the way to create a totally custom section and linking this with a UI Builder Variant.

Is this possible?

Best regards,

Enrique

[Ankur Bawiskar]

@Enrique Avello 

You want to add new section in Overview tab in SOW for which table?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Enrique Avello]

Hello @Ankur Bawiskar as I said on the question this is for Changes

[Ankur Bawiskar]

@Enrique Avello 

if you are talking about this then you should add form section to this view "sow_change_overview"

check this link which has the detailed steps

Service Operations Workspace - How to edit "Overview" section on a change record? 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[ShreepriyaC]

Hi ,

I have a similar requirement, were you able to figure this out? @Enrique Avello 

[mackinley]

We have successfully done this. Here is how:

1. Create a new Form Section for Change Request under the "SOW-Change-Overview" (sow_change_overview) View.
   • The name of the section must be unique
   • We have only tested using names with letters only (EX: "reviewclosure", "approval")
   • Take note of/copy the Name, you will need it later
2. Add your new Section to as an Choice (Optional* if you choose to set the value via not through UI: SN Utils, script, ect.)
   1. Open up the Dictionary Field Record on the “Change Overview Containers” table for the Name field.
   2. Add a New choice to the field, with the value being the name of the Form Section you created.
      • This should be exactly the same. Copy and Paste to be sure.
3. Create a new "Change Overview Card" [chg_overview_card] under the desired "Change Overview Container" [chg_overview_container]
   1. Change -> Workspace Configuration -> Overview Container then select the desired Container or create a New one.
   2. Create a New Change Overview Card using the Related List of the Overview Container
   3. Set the Name field to the new Choice matching the Form Section you previously created.
   4. Fill everything else out as desired.
4. Create new records under the Service Operations Workspace (SOW) Experience in UI Builder (UIB) for your new Card.
   1. Open SOW in UIB and open the editor for the "Chg Overiew Viewport" page -> "Chg Overiew Viewport SNC" variant
      • Note the typo! It's SNs typo not mine. The Page and Variant are missing a 'v' and are "Overiew" instead of "Overview"
   2. Click on the "Section Viewport" element on the left under Content
   3. In the Configure tab on the right, under "Sub-Pages", scroll down and select "Edit Content". This will take you to a "Sub-page overview" screen.
   4. Create new "UX Screen Collection" (aka: Variant Collection), "UX Screen" (aka: Page Variant), and "UX App Route" (aka "URL path") NOTE: There are many ways to achieve this. The following is what we did:
      1. Open the Settings page for the "Chg Overview Summary" -> "Chg Overview Summary SNC" variant.
      2. Duplicate the Variant with the following name: "Chg Overview Summary SNC (vX.X.X)" where X.X.X should be replaced with your current version of the "Change Management for Service Operations Workspace" app.
      3. Deactivate and Save the duplicate Variant you just created.
         • This duplicate is for comparing the against the variant you are about to create so you will have a reference to what the base was during an update of Chg for SOW.
      4. Duplicate the Variant again
         • Give this Variant a meaningful name but also append (vX.X.X Chg Summary Overview) as a reference to what this was originally duplicated from.
      5. Open the "UX Screen Collection" and "UX Screen" records on the Platform for the new Variant
         • Go to the Settings page of the new Variant -> Open records -> Variant collection/Variant record
      6. From the "UX Screen Collection" select the "UX App Routes" related list, and open the only record listed in a new tab
         • You should now have new 3 tabs open: A "UX Screen Collection" (aka: Variant Collection), "UX Screen" (aka: Page Variant), and "UX App Route"
      7. On the "UX Screen Collection" create a new record by changing the name to something meaningful and performing an "Insert and Stay"
         • You can use the "3 line hamburger menu" button at the top left or right-click the record header to find the "Insert and Stay" action
      8. On the "UX App Route", create a new record by changing the following and performing an "Insert and Stay":
         • Name: Something meaningful
         • Route: IMPORTANT - value must be "chg-overview-<section_name>" where "<section_name>" is the name of the corresponding form section created in Step 1!
         • Screen Collection: IMPORTANT - set to the Screen Collection created in Step 7
      9. On the "UX Screen" record, just update the Screen Collection the one created in Step 7 and Save.

That should render but have some values still referencing "Overview Summary". Further customize your variant for your needs being careful of how the components, events, state parameters and scripts are tied together.

Here is a warning for 1 specific quirk we noticed but don't understand why:

DO NOT CHANGE THE ID OF THE "Summary Form" [summary_form] component. That seems to break some event propagation when selected the magnifying glass button on reference fields.

Good Luck.

P.S.

It seems like SN had the intention of making these easier to add to and configure, and maybe they will in the future, but ran out of time/resources to fully implement. It's an interesting way to have a specific component render based on a key value (in this case the Form Section name which maps to the UX Route) without having a bunch of "Hidden" components and being able to add new ones without altering the UIB page they are displayed on.