PeterM | 2019-10-22 02:29:20 UTC | #1
Hi
Using v68 of the .NET SDK I want to be notified when a user is assigned a queue or has a queue assignment revoked.
I've added subscriptions to the v2.routing.queues.{id}.users topic and mapped that to the QueueUserEventTopicQueueMember class.
When a user is assigned to or revoked from a queue the subscription two events are raised. However, the QueueUserEventTopicQueueMember class included with the event only contains information about the queue and nothing about the user.
I found the following forum article and it suggests I should be receiving queue and user information with the events: Queue membership notification
Could there be a problem with the JSON decode with the .NET SDK for the QueueUserEventTopicQueueMember class or can someone tell me if I'm doing something wrong? Thanks.
tim.smith | 2019-10-22 14:24:20 UTC | #2
It looks like the notification schema information is incorrect, and therefore the class in the SDK doesn't match. The notification actually uses the property id, but the schema documents a property memberId. I'll create an issue to get this fixed.
As a workaround until this is fixed, create your own version of QueueUserEventTopicQueueMember and change the MemberId property to Id like so:
[DataMember(Name="id", EmitDefaultValue=false)]
public string Id { get; set; }
PeterM | 2019-10-22 19:06:57 UTC | #3
Thanks for the prompt reply Tim. For this type of issue, can you give me some guidance on how long it's likely to be before a fix is available? With that information we can then decide how to proceed.
tim.smith | 2019-10-22 19:47:26 UTC | #4
It's a quick fix, but it will likely be 1-2 weeks before the fix makes it to production as the fix relies on an API deployment.
PeterM | 2019-10-22 20:43:04 UTC | #5
OK - thanks for that. I'll keep an eye on Github. If you could post a message here when you know the date the fix will be released that would be appreciated. Cheers
tim.smith | 2019-10-22 22:24:46 UTC | #6
I was going to fix this myself, but the fix needs some input from the dev team first. If you can open a case with PureCloud Care to report the problem with the notification topic response schema, that will help with prioritization. You can reference AS-1416 in the case.
PeterM | 2019-10-23 09:05:24 UTC | #7
I've cloned and corrected the QueueUserEventTopicQueueMember class as you suggested and that has worked well. Thanks for that suggestion - it was easier than I thought!
As a contract developer for a big organisation I don't have access to PureCloud Care to report the problem. I've escalated the problem up the line and asked for a case to be lodged but the "wheels grind slowly" here. In the interim whatever you can do to permanently resolve the problem with a fix to QueueUserEventTopicQueueMember would be appreciated.
PeterM | 2019-11-15 03:51:43 UTC | #8
Hey Tim - I didn't get to log a case for this (other things got in the way and raising a case is difficult). I've just had a look at the releases since this issue was logged and can't see anything which looks like a fix. Is there a fix on the way or do you need me to grit my teeth and get the organisation I work for to raise a case?
tim.smith | 2019-11-15 04:07:18 UTC | #9
The fix is currently in testing and should be deployed on the next API deploy, which should be next week.
PeterM | 2019-11-15 21:37:11 UTC | #10
That's great news. Thanks very much Tim.
system | 2019-12-16 21:49:31 UTC | #11
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: 6311