Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

How can I configure the roadmap filter condition reference qualifiers in SPW?

Dinsdale
Tera Expert

Hi all

 

I have a bit of headscratcher. 

 

In SPW, you can create a free-from roadmap and in doing so, you select criteria - this works fine. For example, if I want to select a roadmap for Demands that have the Department of "IT", I can see these.

 

We get our department data from an external source, so when they offline a department, we want it to reflect in ServiceNow - and this works well. However, if the department record has a custom "active" flag set to "false", this is obviously ignored in the SPW query. 

 

On the classic dmn_demand view, I can simply add a reference qualifier on the dictionary entry to get past this.

 

How do I set a reference qualifier for fields on the SPW roadmap screen? Screenshot attached for reference.Roadmap.jpg

2 REPLIES 2

sandeepdutt
Tera Patron

Hi @Dinsdale ,

As you said , "On the classic dmn_demand view, I can simply add a reference qualifier on the dictionary entry to get past this ". So have you already done that? 

As if you do so, it will definitely work on workspace as well as it's being done at Dictionary entry level.

What you can do is, Navigate to dmn_demand table, then look for the Field , configure Dictionary and follow the steps to add your Refernce Qualifier.

 

From the Workspace itself, you cannot add any reference qualifier.

 

Thanks,
Sandeep Dutta

Please mark the answer correct & Helpful, if i could help you.

Yes, the reference qualifier is on the table but it is ignored in workspace. 

I thought "that actually makes sense" because the workspace looks at the alignment/integration config. 

So I added the same reference qualifier on the fields on sn_align_core_demand, made sure the flow was both ways on the integration mapping, hoping it would be what would reflect on the workspace, which I thought would make sense. 

But that didn't work either. I fear this config is buried 10 layers deep in some code and I am reluctant to touch it even if I found it. 

I should state that client has departments with the same name (long story) - hence the problem, users don't know which "IT"

department to pick.