Discrepencies between form view and workspace view in the same record

[C_dric Chen]

Greetings, folks.

After spending half a day trying to configure the extended Impact-Urgency-Priority mechanism without success (and narrowly escaping a scolding by my teacher), I took the other path and built one from scratch, using both UI policies and automated flows. Ever since then, I've been experiencing weird discrepancies between the form view and the workspace view. To make things worse, when I try to update the "Impact" field and/or the "Urgency" field in the workspace view, the "Priority" field in the form view would be updated:

But the "Priority" field in the workspace view would refuse to react:

Does anyone have any idea why this would happen?

[Allen Andreas]

Hello,

It's unfortunate regarding the use of the priority data lookup, as I have discussed this with you a few times in your other thread here:  https://community.servicenow.com/community?id=community_question&sys_id=ee7b69c21b3bc5d0587a11751a4b... - I'm unsure where the confusion is as when I've called out the specific record you need to make and was shown missing from your screenshots of the custom app, several times, and now it appears you've abandoned it altogether and further went the custom route. Which...as you can see...has now led to additional issues by going down this path.

I'd recommend revisiting your other thread and carefully reading my responses there as it would appear you only need to create a data definition record, and re-create or associate your custom matchers to that definition record. You can easily use the out of box global incident definition record for how to accomplish this.

Please mark reply as Helpful/Correct, if applicable. Thanks!