Skip to Main Content
Tenjin Ideas Portal
Status Shipped
Created by Guest
Created on Oct 19, 2021

Flow: A Flow can be triggered from a pro-active message

Copied from the Azure DevOps board: https://biomni.visualstudio.com/BottKitt/_workitems/edit/3338


A flow should be able to be triggered from a pro-active message similar to how send message works today.

Need to think about input and return parameters, the caller would like to get the return values back (async).

Needs to work from inside an Agent Handoff.

Message type

{
?SessionID? for agent handoff optional
"type": "CallProjectFlow",
"FlowRef": "Project1.Flow1",
"InputArguments": [],
"ReturnCallBackUrl": ""
}


[Todo] Both proactive apis need to validate the CallProjectFlow, exists etc same number of params etc

[Todo] In the Bot kick off the project flow

[Todo] In the Bot make sure you can do this whilst in a agent handoff - agent handoff takes over all bot input so this wouls circumvent that until the flow is complete.

[Todo] If a ReturnCallBackUr is supplied then send any return values to it



Returns part 2

- can we use activity?

[Todo] Both proactive apis refactor to return an ID this id can then be used to Poll for completion and obtain the return values

[Todo] Both proactive apis on acceptance of the message create and store the return ID - can we use activity table?

[Todo] In the bot on complete of the flow update the return values in the table or activity.

  • Attach files
  • Guest
    Reply
    |
    Mar 17, 2022

    A new proactive flow was created as part of the Add the ServiceNow skill into Flow story, which allows you to call out to project flows from a proactive message, it's all configurable within the standard flow editor.

    Update from Dev on this specific feature request:

    • Might need to have a new proactive message type adding though to allow us to handle it - but might be able to get away with the existing default one (think it just expects a single string) and then some assign variable stuff to parse it and pull it apart.

    • I don't think theres any work for dev, might be a tricky job for services, etc to actually implement

    • but do-able with the tools we have atm


    If additional work is required, it can be reviewed based upon the specific use case.