Copied from Azure DevOps (ref: #2834) When starting a new conversation with an Agent, make sure they're sent the history of the conversation from Tenjin, care being taken that we only send what's relevant to the Agent - how do we identify what's r...
Moved from an Azure DevOps story (#2897) Allow the admin flow persona to see what part of the flow is currently running, making it easier to build flows.
User Power virtual assistant to see how it works there.
Assistant on the Tenjin site se...
Supplied to the Dev team by Costas Sub / multi flows:
A single flow is difficult to manage when trying to develop a real world process. Components like multi-choice and when-if do make a difference but the ability to have more than one flow and ...
Flow - HTTP action and returning data (singular and multiple)
Supplied to the Dev team by Costas HTTP:
I think the current plans are OK (e.g. variable inclusion, POST, GET etc).
It is not clear how the flow will make returned data available for further processing within the flow, I see 2 main scenarios, ...
Ability to provide a wizard and/or prompts to help onboard new accounts and users in a self-service fashion, whilst also making sure the wizard / prompts are always available if a user would like a reminder. At the moment there's a lot of talk aro...