Forum Discussion
Ability to add metadata to manifest to inspect when receive chat for routing to different pipelines
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