- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2024 02:49 AM
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2024 02:58 AM
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
Also please watch this video:
https://www.youtube.com/watch?v=upq2NF_RrYU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2024 02:58 AM
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
Also please watch this video:
https://www.youtube.com/watch?v=upq2NF_RrYU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-24-2024 06:27 AM
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?