SET Priority in Architect VS PATCH Priority

Platform API
1

Hello,

I would like modify interaction priority in a In-Queue Email flow.
Making tests, I have observed the same behavior between the SET priority action in architect inqueue email flow and the API PATCH /api/v2/routing/conversations/{conversationId} which enables also to modify the priority.
My result, for the PATCH and SET is the following : the priority configured replaces the current priority , is there documentation that confim my tests. Can you confirm my result?

thanks
jeremy

2

Hi Jeremy,

I validated with the architect team does a replace of the current priority. I have forwarded your inquiry to the conversation team to see if they can validate what they do with priority. Can you provide the payload you used for the patch? Please make sure you obfuscate any sensitive data.

Thanks,
John Carnell
Director, Developer Engagement

3

Hi John,
Making extra tests, I have observed the SET and PATCH have the same behavior and replace the current priority in queue, in other words, when we use these methods the age of the interaction is not taken in consideration. Can you confim? I have modified my original post accordingly.

below the details for the PATCH API :
PATCH /api/v2/routing/conversations/f972bea8-3965-4aed-8dfa-aa66e669433b HTTP/1.1
{"priority":50}

thanks
jeremy

4

Hi John,
any feedback from the conversation team?

thanks
jeremy

5

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.