Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

My priorty is not changing for a custom table inheriting Incident Table

Navaneeth1
Tera Guru

I have a custom-scoped application with a table inheriting from the incident table. I have Impact, Urgency, and Priority inherited from the incident table for this scoped application table and I've created Priority lookup rules but the priority still does not change when I change impact and urgency for this. 

Could someone please help me fix this issue?

1 ACCEPTED SOLUTION

Not applicable

Hi @Navaneeth1 ,

You will need to create the Priority lookup rule for your custom table properly, for that:

1)First you need to create a table extended by data lookup matcher rules(dl_matcher)table.

2)in this table create 3 fields below:

Impact, urgency and Priority

and set the value next process is 
 
3)create Data Lookup Definitions like this
 
 
 
SandeepDutta_0-1704797895797.png

 

Also please watch this video:

https://www.youtube.com/watch?v=upq2NF_RrYU

 

View solution in original post

2 REPLIES 2

Not applicable

Hi @Navaneeth1 ,

You will need to create the Priority lookup rule for your custom table properly, for that:

1)First you need to create a table extended by data lookup matcher rules(dl_matcher)table.

2)in this table create 3 fields below:

Impact, urgency and Priority

and set the value next process is 
 
3)create Data Lookup Definitions like this
 
 
 
SandeepDutta_0-1704797895797.png

 

Also please watch this video:

https://www.youtube.com/watch?v=upq2NF_RrYU

 

I followed the YouTube video, and though my lookup has the "Run on Change" flag marked as true, it will not update until I save the record.  Did I miss something?