Hi @CarolineS - We have fixed the issue on 21.7. It will be applied to Cisco in the next maintenance window. You should get it in next 2-3 days. I will keep you updated anyways. CC: @AbhinnG  Thanks Noor ... View more

Hi @CarolineS, Yes, we are taking this on priority. I will keep you updated. CC: @AbhinnG  Thanks Noor   ... View more

Hi @CarolineS , @djondinium  We fixed an accessibility issue in 21.6, wherein fix involved correcting the tab order on header elements. This fix changed the position of the icons on the header. We have a quick workaround to this. It can be fixed by putting the following CSS in the skin from the studio. Please see the attached image We are also looking towards changing the fix on priority. Thanks Noor       ... View more

Hi @Finney0225 - You can integrate Slack integration on both stage and prod environments. The potential problem that you can encounter with stage environment is that it is usually behind an HTaccess. Since this is a third party integration, it is important that site should be publicly accessible.  CC: @AshishKe  ... View more

Hi @CarolineS  There are two parts to Comments syndication. Creating a widget when topic already exists - In this case topic exists in the community and you syndicate existent comments (if present) on an external page. In order to test this on stage, you can simply use Demo URL or even use the widget on any dot com page. The widget would syndicate comments and discussions would be mirrored to and fro from community and dot com page. Syndicate a topic - In this case, topic does not exist in the community. In this feature, we have designed a flow where a topic gets automatically created in the community. The  topic that is created corresponds to the dot com page where the widget is syndicated. Please note that here the widget is simply a comment box and this comment box would load on dot com page only when topic gets created in the community, else it will not load. Now the topic would only be created if this widget is put on a page that has a public URL and has a valid topic. The reason we need a valid public URL is because we are using a 3rd party API that fetches title/description information from the page and creates a topic on community with these details. Now in order to test this flow on stage, Please let us know a page URL of any site (which is public) where you would be syndicating this widget. We will whitelist that domain under a particulate config and update you. We will also whitelist this domain under CSP policy. You should be able to test this then. We have kept these checks in place because of security reasons.  Please let me know the URL and any other queries you have. Thanks Noor CC: @AbhinnG , @StevenT  ... View more