Duplicated "Request Catalog Item" topic block Publishing Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-09-2024 09:43 AM
I'm trying to duplicate the Request Catalog Item topic block to do some modifications to the output of a Configuration Item choice selection, but I get this error and can not publish. None of the cards are ID the same error... not sure whats going on:
- No topic variable registered for InputPrompt a9fd61aebbe74d02bdd9438c66e67c5e variable 6e0b667d4dbb4459b52c0dcedcf8b5f1.
- Labels:
-
Virtual Agent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2024 06:00 AM
@Joselin1 Please activate/repair the Virtual agent plugin and then try it again.
Please mark this as helpful and accept it as a solution if this resolves your query.
Thanks,
Sujatha V.M.
Sujatha V.M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2024 06:33 AM
Hi Sujatha,
I have tried this but still showing the same error.
While testing the OOB topic, it shows the same error-No topic variable registered for Input Prompt.
and duplicated topic also showing the same while testing.
Thank you for your response!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2024 06:39 AM
@Joselin1 Thank you for the confirmation. In that case, could you please raise a support case with ServiceNow and ask them to investigate it.
Please mark this as helpful and accept it as a solution if this resolves your query.
Thanks,
Sujatha V.M.
Sujatha V.M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2024 04:52 AM
Hi @Nathan Okh @Sujatha V M @Prashant Ahire
Most of the Vancouver version instances are facing this same issue, we can upgrade our instance into Washington DC version for this issue to be fixed. For confirmation raise a support case with ServiceNow.
Upcoming patch upgrade may resolve this issue if it got fixed by ServiceNow.
Please mark this as helpful and accept it as a solution if this resolves your query.
Thanks,
Joselin