- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Shweta,
To answer your question directly: There is no native "Test in Teams" feature within the Virtual Agent Designer.
The "Test" button in ServiceNow only launches the Web Client Simulator. It cannot push a draft topic directly to the Microsoft Teams interface for a quick preview.
How to achieve this (The Standard Workaround): To test exactly how your enhancements will look and behave in MS Teams (e.g., Adaptive Cards, button rendering) before Production, you must utilize a Sub-Production (Dev or Test) Instance.
Connect Sub-Prod: You need to integrate your Dev/Test instance with your Microsoft Teams tenant (typically creating a separate bot named "ServiceNow Dev").
Publish to Dev: You must Publish (not just Save) your topic in the Dev instance.
Test: Open MS Teams and chat with your "ServiceNow Dev" bot to see the changes.
Summary: You cannot test directly in Teams from a Draft. You must publish to a connected non-production instance first.
If this response helps clarify the limitations, please mark it as Accepted Solution.
Best regards,
Brandão.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Shweta,
To answer your question directly: There is no native "Test in Teams" feature within the Virtual Agent Designer.
The "Test" button in ServiceNow only launches the Web Client Simulator. It cannot push a draft topic directly to the Microsoft Teams interface for a quick preview.
How to achieve this (The Standard Workaround): To test exactly how your enhancements will look and behave in MS Teams (e.g., Adaptive Cards, button rendering) before Production, you must utilize a Sub-Production (Dev or Test) Instance.
Connect Sub-Prod: You need to integrate your Dev/Test instance with your Microsoft Teams tenant (typically creating a separate bot named "ServiceNow Dev").
Publish to Dev: You must Publish (not just Save) your topic in the Dev instance.
Test: Open MS Teams and chat with your "ServiceNow Dev" bot to see the changes.
Summary: You cannot test directly in Teams from a Draft. You must publish to a connected non-production instance first.
If this response helps clarify the limitations, please mark it as Accepted Solution.
Best regards,
Brandão.
