Servicenow Decision table not accepting input from Users Location field Country
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2023 01:45 AM
Hi All,
I am a learner. I have created a custom table for ordering office facility supplies by employees. Record Producer will create records on this. Employees will access the portal and submit request for ordering. Pretty basic fields - Caller who orders, product he want to request, Location. Based on location country, his request will go to a user group (Team). For request from caller in India it will go to India Team, for a caller from China it will go to China Team, for others it will go to Global team. I wanted to leverage decision table to make Team decision based on the input country. I created the decision table, conditions and tested before publishing with already created records. The test simulation is able to pick the country and return the corresponding mapped team. Works fine for different inputs and it gives the correct outputs.
However, when I publish it and test on the same records, it just goes to the default condition (returns the Global Team as output). On checking the execution, I see that country is currently returned, however on hovering over the country value it says "no record found". Don't see a reason why it happens. Any pointers on this will help. Screenshots here.
The above happens when published and tested on record. India is seen in the logs, but the decision output is default, it is not the India team. If I do the same directly on decision table simulation, it returns the correct results. screenshots below.
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-24-2023 04:07 PM
I would try to re-engineer the solution to use as input the Country directly.
And of course that would not be a reference, but a string, as that is how it is defined on the Location table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2024 08:26 AM
Hi, I had the same problem.
You need to pass a string to the decision table and likewise the input in the decision table should also be a string. Using reference fields to cross-reference flow designer and decision table is not supported at the moment.
What you need to do is to create a flow variable on flow designer to transform the location reference field to a string; and likewise you need to create MANUALLY string inputs on Decision Table that would be exactly the same as the string that is coming from the flow designer.
That's the only way at the moment to do the matching between decision table and flow designer.
Hope it helps!
Best,
Firat