How to apply Condition field on Custom Greeting and Setup

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2021 02:15 AM
Hi all,
Anyone been working on the new "Custom Greetings and Setup" yet with Quebec? Just wondering if anyone has gotten this working correctly.
What I'm encountering now, is when I setup a new Custom Greetings and Setup record, it's always being used. Even if I add an incorrect portal in the condition, it's still being used on SP portal, ISC portal, etc..
See this for example, an incorrect portal:
Though on SP, ISC, etc, it's still being applied:
While on ISC, the settings are:
Any ideas?
Kind regards,
Mark
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-10-2021 12:21 PM
Wondering if using an Advanced condition mode can be a workaround...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2021 10:33 AM
What are the full requirements for this feature to work?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2022 07:51 AM
Good Day,
I am experiencing this issue as well. Trying to set up a new Custom Greetings and Setup on a CSM portal. I set the condition portal is Customer Support, but the Virtual Agent is still grabbing the default chat experience.
We are on the Rome version.
Can anyone advise on what I might be doing incorrectly?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2022 06:14 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2022 12:07 PM
Hi Rod,
Thank you that did work, but only after I figured out another issue that was happening. I had created a widget, and even though the widget was on the portal, it did not have the portal context, so portal was coming up as undefined.
Once I figured that out I was able to get the condition to work.