Decision table is not reading the entire string when I use 'contains' in the condition
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi everyone,
I am using Decision table in a flow designer to set the assignment group and subcategory based on the mailbox address. The mailbox has multiple addresses and hence I am using the 'contains' when I am building the condition in the decision table.
When I use the “contains” condition in a Decision Table (for example: checking if a string or list contains a certain value), it only matches when the value appears first in the string or comma-separated list and is not giving any output if the string does not appear first.
Has anybody run into this issue before? Does anybody have any pointers for me to try?
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
share screenshots please
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi @Ankur Bawiskar ,
Please find the screenshots. I have tried to hide some information.
This is the decision table, where I have used the 'contains' condition to get the mailbox value and set the fields accordingly.
In this screenshot, since the mailbox id is not the first value of string, it's not populating the country, assignment group and sub - category.
In this screenshot, since the mailbox id is the first value of string, so it is populating the country, assignment group and sub - category.
Thanks,
Poorva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
did you Test decision table and it worked?
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
it worked fine for me when I tested, seems the value is not getting passed properly in your case from flow to decision table
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader