Digital Assistant and Mobile

Get Involved. Join the Conversation.

Topic

    Luuk
    DA - Response cards visible in the designer test environment...Answered
    Topic posted March 13, 2019 by Luuk Bronze Crown: 15,000+ Points, tagged Bots 
    7 Views, 6 Comments
    Title:
    DA - Response cards visible in the designer test environment but not in web widget
    Summary:
    Response cards visible in the designer test environment but not in web widget
    Content:

    Hi all,

    Maybe someone can help me out here. I've created a skill which returns a set of cards.
    The reponse works perfectly fine in the Digital Assistant UI designer test tool but when I test the same bot from within a web widget, the cards are not displaying at all.
    Does anyone has any ideas what this could be?

    Kind regards,
    Luuk Schalk

    Best Comment

    Grant Ronald

    So this worked before?  What has changed?  What kind of component are you using (in the dialog flow to display the cards).  Is this specific to the browser you are using?  Have you tried one of the in-built skills and see how that performs?  

    Comment

     

    • Grant Ronald

      What version are you on?  18.4.3?  This should work - are your using the Web SDK?

      • Luuk

        I'm quite new to this. Where can I find the version?
        This worked up until last week or the week before.

    • Grant Ronald

      Top right is a circle which shows your initials. click on that

    • Grant Ronald

      So this worked before?  What has changed?  What kind of component are you using (in the dialog flow to display the cards).  Is this specific to the browser you are using?  Have you tried one of the in-built skills and see how that performs?  

      • Luuk

        I've created a custom component which displays the result set nicely in the test environment.
        Has there been a platform upgrade lately?

        It's not browser specific. I've tried cloning the current skill and the same thing happened. I've also tried creating a new channel but that gave the same error.

        I'm now trying to put the backend in an embedded container to see if that changes things.