canderson | 2019-10-23 13:48:47 UTC | #1
I'm working on a background application that needs to monitor user behavior for all users. Due to the limit of the number of notification channels and subscriptions I can have I want to make sure I'm not subscribing to notifications for users who aren't logged in.
The problem is, I can't find a notification channel that tells me when a user logs in. If I could have that, I could only subscribe to the appropriate topics when a user logs in.
Is there something out there that I'm missing that would help me out?
tim.smith | 2019-10-23 13:54:31 UTC | #2
PureCloud doesn't have a concept of logged in/out. A user can have multiple valid access tokens for multiple applications at any given time, but that does not imply whether or not they're actively using any of those applications. The closest concept in PureCloud is the user's presence. If they're offline, then they're probably not using an application. But you still need to watch each user's presence individually; there isn't a system-wide presence change notification.
Can you list the topics your app is subscribing to for each user? There may be some ways to condense the number of subscriptions.
canderson | 2019-10-23 14:48:10 UTC | #3
Thanks for the response.
I'm still working out the plan for my overall solution so I don't yet have a full list of topics that I'd be subscribing to for each user. The only one I know for sure is that I need a notification when a user receives a conversation. So I might just need to subscribe to v2.users.{id}.conversations for every user and then parse/handle them appropriately.
I'll reply to this thread in the future once I got more information.
Thanks.
tim.smith | 2019-10-23 14:56:03 UTC | #4
These topics may be useful:
v2.users.{id}.activity aggregates routing status, presence, out of office, and active queues into a single notification.v2.users.{id}.conversations for all conversation events or v2.users.{id}.conversationsummary if you just need a summary and not details of the conversations.v2.routing.queues.{id}.conversations could drastically cut down the number of subscriptions required if you only care about ACD conversations.
Also, be sure to read up on Combining Related Topics where you can subscribe to similar topics with a single topic request, which will allow you to register for more topics than if you registered for them individually.
Your max topics will be 1000 topics per channel * 10 channels for a total of 10,000 topics. Unless you have a very large org or are subscribing to a whole lot of topics, the app should be able to stay under the limit.
system | 2019-11-23 14:56:06 UTC | #5
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: 6332