Glific v5.1.6

View Source Glific.Processor.ConsumerFlow (Glific v5.1.6)

Given a message, run it thru the flow engine. This is an auxilary module to help consumer_worker which is the main workhorse

Link to this section Summary

Functions

load_state(organization_id)

Load the relevant state into the gen_server state object that we need to process messages

move_forward(arg, body, context, opts)

In case contact is not in optin flow let's move ahead with the regular processing.

start_new_flow(message, body, state, opts \\ [])

Start a flow or reactivate a flow if needed. This will be linked to the entire trigger mechanism once we have that under control.

Link to this section Functions

Link to this function

load_state(organization_id)

View Source 
@spec load_state(non_neg_integer()) :: map()

Load the relevant state into the gen_server state object that we need to process messages

Link to this function

move_forward(arg, body, context, opts)

View Source 
@spec move_forward(
  {Glific.Messages.Message.t(), map()},
  String.t(),
  Glific.Flows.FlowContext.t(),
  Keyword.t()
) :: {Glific.Messages.Message.t(), map()}

In case contact is not in optin flow let's move ahead with the regular processing.

Link to this function

start_new_flow(message, body, state, opts \\ [])

View Source 
@spec start_new_flow(
  atom() | Glific.Messages.Message.t(),
  String.t(),
  map(),
  Keyword.t()
) ::
  {Glific.Messages.Message.t(), map()}

Start a flow or reactivate a flow if needed. This will be linked to the entire trigger mechanism once we have that under control.