Need to show unassigned catalog tasks donut on service operations workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-08-2023 04:29 PM
Since there is a donut called unassigned incidents in Service Operations Workspace landing page, i have a requirement to create a new donut for unassigned catalog tasks. I have already done the donut but my problem is the data/list below does not update when I click on the Unassigned Catalog tasks donut. Do you know how i can may it work like an interactive filter like the other donuts (Unassigned incidents) in the landing page?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2023 09:05 AM
I had the same issue - then I populated the LabelMap section of the SOWIncidentLandingPageUtils in the UX Client Script Includes and it started working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2024 09:05 AM
Kim, could you share what you populated in the LableMap section?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2024 03:40 AM
@jparman May i please know how did you configure the new donut and the steps to be performed.
Also are you able to gets list of unassigned catalog tasks in the list below ? if yes, can u pls guide the steps to be followed ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2024 12:35 AM
Hi i have similar requirement I need to create a new widget so i have duplicated the variant trying to update on new variant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2024 09:19 AM
Hi @jparman ,
Update the SOW plugin and look for the UX client script include 'SowIncidentLandingPageUtils' and 'SowIncidentLandingPageUtilsSNC'.
The data comes from a script. You can easily change this in the script, but it is a nightmare from the UI builder.
Overwrite the 'getVisualizationConfig()' method.
You will need to copy the whole method into SowIncidentLandingPageUtils so you have full control of the output.
This method creates the cards and what data it will contain.
Here you can switch the cards around to have to order you want, create new cards, or configure if queries to your liking.
A card looks like this:
//visualizationConfig is an array holding objects that will be made into cards.
const visualizationConfig = [{
"id": "incident_assigned",
//Here is the table the query will use
"tableName": "incident",
"tableDisplayValue": "Incident",
//Here are the queries as encoded queries, you can alter these queries to get the incidents you want.
//The two different queries are for "My work" and "My teams work".
"myWorkQuery": "active=true^assigned_toDYNAMIC90d1921e5f510100a9ad2572f2b477fe",
"myTeamQuery": "active=true^assigned_toISNOTEMPTY^assignment_groupDYNAMICd6435e965f510100a9ad2572f2b47744",
"listView": mode == "your_work" ? "sow_landing_page_assigned" : "sow_landing_page",
"header": mode == 'your_work' ? await helpers.translate("Incidents assigned to me") : await helpers.translate("Incidents assigned to my team"),
"groupByField": "state",
"evamId": evamDef['incidentEvamDefinitionId'],
"updated_on": "^ORDERBYDESCsys_updated_on",
}
Please let me know if this reply helps your situation.
Thanks & Regards,
sumanth meda