Flow
Last updated
Was this helpful?
Last updated
Was this helpful?
the client initiates a flow, specifying the flow ID. the initiate call response contains an invite code and other flow session details.
ti-server fetches the flow from FlowDB and starts the flow session. at this point, the client and server are waiting for customers to connect to flow and consume. when the server starts the flow session two channels, one for flow events and the other for interaction events will be initiated.
The flow events channel is a bi-directional channel passing events between components.
Similarly, the interaction events channel acts as a bridge for communication data exchange between components.
note: currently, we have tested the framework with one customer. but it is designed to be extendable to multiple customers connecting to the same flow session.
the client connects to the flow session, by connecting to both flow and interact event channels.
note: the TI SDK handles this step and conveniently provides the client application listeners/callbacks for the flow and interact events.
The client shares the invite code he received in step-1 with the customer. the customer enters the invite code, to register and connect to the flow session.
the register-connect API response also contains the flow session details to persist on customer application.
note: the TI SDK handles this step and conveniently provides the customer application listeners/callbacks for the flow and interact events.
as the customer completes each task, those task complete events are updated to the ti-server via the SDK.
the ti server as it gets updated about the task complete events from the customer, it updates the client, and records these flow events in the DB.
most importantly it will perform calculations if criteria have been met for task-stage-flow to be deemed complete. this is where the custom implementation of flow state can be added.
once the client connects to the flow session that it initiated on the server. It would receive all the flow and interact event updates via the flow and interaction listeners/callbacks that it passed on to SDK. until the flow is completed by the customer and the server deems it complete, the channels will be terminated.
