Where does the highlighted state value on EVAM Cards come from?

Vegard S
Kilo Sage

Looking through the EVAM View Configs for Incidents, used in Service Operations Workspace, I notice in the mappings object, it says  "highlightedHeaderLabel": "state"

But where does the actual highlighted labels come from?
I assumed it's from UX Highlighted values (sys_highlighted_value), but there's no records there for the State field for example, only Priority. 

VegardS_0-1695278266901.png

I'm adding another set of cards for Universal Request and I use the exact same EVAM config and EVAM View Template as Incident, but all state fields are just gray. 

1 ACCEPTED SOLUTION

Bradley Marin
Giga Guru

Wanted to add, I've found this documentation but it's fairly lacking and I have still not been able to get this figured out, even with the doc.

View solution in original post

5 REPLIES 5

Bradley Marin
Giga Guru

So, I'm a little stumped by this as well. I created a new "Highlighted Values" record under the "SOW Highlighted Value Config" UX Highlighted Value Configuration. I also made sure the EVAM Definition I created for Universal Requests has the "highlightedHeaderLabel" set to "priority", because that is the table field I chose for UR's. 

Strangely enough, the card view in SOW doesn't show the correct colors, but now the list view does (see attached image). 

Does anyone have any idea why it's just not showing in the card despite being mapped to the correct field in the EVAM Definition?

Bradley Marin
Giga Guru

Did you ever find a solution to this?

Bradley Marin
Giga Guru

Wanted to add, I've found this documentation but it's fairly lacking and I have still not been able to get this figured out, even with the doc.

Aha! This is it actually. 

So it's essentially a script includes which the scripts on the landing page uses to get the colors it needs. 

VegardS_0-1697788669159.png
So the procedure is most likely to open the SNC script, copy the this.CHART_COLORS object and paste it into the other script. 

Then just append whatever other tables or states that you need. 

 

Next step is to dig through the UI Builder page to see how it's actually manipulated and passes into the evam data set component. Cause I'm gonna need this elsewhere too 🙂