DPM: Issue or "Bug" with "Needs Attention Attributes"

Robin J_
Tera Guru

Hello Community!

I have been digging deeper into "Needs Attention Attributes" on the Digital Portfolio Management Workspace. I have also used this KB: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1519343

The issue I have is that both Inputs (grAttrib + grSolution) seems to be empty which are utilized by OOTB Script Include (DPMNeedsAttentionUtilsSNC).

OOTB it is configured this way:

RobinJ__0-1717578036163.png

The query itself here is OK, but the issue is that both (grAttrib + grSolution) are empty when adding new Solution Cards. This results in that I get ALL incidents no matter which Solution, the only thing which matters is the "query". This seems in my head to be a "bug" OOTB.

I for example tried customizing and logging the variables (grAttrib + grSolution):

RobinJ__2-1717578217773.png


It shows clearly that these to variables looks to be empty:

RobinJ__3-1717578303076.png


This results in the query to apply to ALL solution cards:

RobinJ__4-1717578354344.png

 

Any ideas? I also created a Support ticket, but thought I could also post this on the Community!

- Robin

1 ACCEPTED SOLUTION

mikehall
ServiceNow Employee
ServiceNow Employee

Hi Robin,

 

This has been confirmed as a new product defect on the homepage.  I found your case task and messaged the TSE to route it to our team for remedy.  If all goes well, there will be a fix in the August release of DPM.

 

As a work around, if you click on the card to view the solution (aka the service, offering, etc), you will see the correct Needs Attention numbers in the right side panel.

 

I authored that KB btw, so if I can be of any help with NA, please ask!

 

Mike

View solution in original post

7 REPLIES 7

Hi Natalie, Did you get any resolution on this? i am facing the same issue. 

mikehall
ServiceNow Employee
ServiceNow Employee

One more thing.....  there is a one hour caching delay on the homepage.  If you make a new incident against your solution, you need to manually refresh the cache (using a refresh icon on homepage) to see it.  There may be a separate issue here, but I wanted to make sure that was brought up for awareness.

Great to know and will note that down! Thanks a lot 😁