Forum Discussion
Ability to add metadata to manifest to inspect when receive chat for routing to different pipelines
Thanks Nivedipa for the reply.
Are any of those values passed through the Azure Bot payload so that we can take a look at them on the receiving side of the bot conversation?
I'd like to just add one custom property, or use a property, and have that property included on every chat conversation, as part of the message payload, so that we can inspect it on the receiving side (other side of the chat)
Here is what we are building and we'd like to split out the IT, Sales, and HR channels into 3 different manifest based icons - for example
https://www.chimev5.com/
Peyton
Microsoft@PeytonMcM - You can include custom properties in the channelData object of the message payload. This allows you to pass additional information that can be accessed on the receiving side.
Thanks Nivedipa-MSFT
We will look at the channelData object. Just to be clear, we want to place some value into the manifest when we install the icon on the left side of the Teams UI - and this value will be added to the conversation structure - so we can inspect it (make a conditional branch for example) on the receiving side.
So, those 2 icons would have 2 different images, and slightly different metadata, but go to the same conversational channel - and then when we receive the chat, we would branch it to say
- HR
- Sales
- IT Support
Of course, we could put a menu system on the inbound chat side (some adaptive card with options for example), but we have customers who would like to have one chat platform (i.e. https://www.chimev5.com/) but create different chat workflows for IT Support, HR, Operations