jacobs | 2018-04-11 14:54:31 UTC | #1
Using /api/v2/conversations/chats with content
{
"queueId": "some-queue",
"provider": "My Customer Provider",
"customerName": "name",
"attributes": {
"BR_URLPop": "link to chat app conversation"
}
}
we can successfully pop the chat app conversation. Is there a different attribute to use in order to open the url to pop within an existing embedded client app? Or a specific protocol which can be used to tell PureCloud to use an embedded client app to open?
If conversations/chat is not the right resource to do something like the above, what would be?
mwilbanks | 2018-04-12 13:47:43 UTC | #2
bumping this to the top
KevinGlinski | 2018-04-12 17:23:54 UTC | #3
so you are using PureCloud for Chrome and are routing 3rd party chats. BR_URLPop should be the attribute you want. When you ask about an "embedded client app" what app is embedded where?
What is happening vs what are you expecting to happen?
jacobs | 2018-04-13 03:09:55 UTC | #4
Using the BR_URLPop attribute works as expected opening a 3rd party chat item.
The application is embedded into pure cloud using the "custom client application" web integration.
KevinGlinski | 2018-04-13 13:46:51 UTC | #5
BR_URLPop will only pop to a new browser tab. For what you are doing, sounds like you want to handle screen pop yourself by subscribing to a notification topic for the user's conversations and then do the navigation yourself within purecloud. The only problem with this is your app has to be open to receive the notifications. I believe sidebar apps are always running, so you could setup a sidebar app to subscribe and then have it do a navigation to your app.
@Justin_Ray any suggestions here? Seems like this is a separate use case which could benifit from a "viewless" app
Justin_Ray | 2018-04-19 18:08:15 UTC | #6
We are beta testing the Embedded Client Apps SDK at the moment. It will allow you to "pop a toast", i.e. send an alert message, if your app was blurred/backgrounded and it has relevant information for them.
We haven't implemented it yet, but we have been getting feedback from devs that they would like the click action on the toast to focus the app. This makes a lot of sense and we hope to add it when priorities allow.
This does presume that the user has loaded the app at least once. Lazy loading is an important tenant to the apps framework as we need to be cognizant of loading too much at bootstrap and degrading the user experience. Once a user has activated an app, it will continue to run unless the user activates too many and one will need to be evicted. Eviction uses a LRU-based algorithm, so if the user is regularly using an app, eviction is less likely.
We have definitely discussed headless apps but we have some other ideas on how to address this without adding a bunch of weight to the PureCloud experience.
Hopefully the toast will suffice in the interim.
system | 2018-05-20 18:08:16 UTC | #7
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 2727