View Source Glific.Flows.MessageBroadcastContact (Glific v5.1.6)

When we are running a flow, we are running it in the context of a contact and/or a conversation (or other Glific data types). Let encapsulate this in a module and isolate the flow from the other aspects of Glific

Link to this section Summary


Standard changeset pattern we use for all data types

Link to this section Types

@type t() :: %Glific.Flows.MessageBroadcastContact{
  __meta__: Ecto.Schema.Metadata.t(),
  contact: Glific.Contacts.Contact.t() | Ecto.Association.NotLoaded.t() | nil,
  contact_id: non_neg_integer() | nil,
  id: term(),
  inserted_at: :utc_datetime | nil,
    Glific.Flows.MessageBroadcast.t() | Ecto.Association.NotLoaded.t() | nil,
  message_broadcast_id: non_neg_integer() | nil,
    Glific.Partners.Organization.t() | Ecto.Association.NotLoaded.t() | nil,
  organization_id: non_neg_integer() | nil,
  processed_at: :utc_datetime | nil,
  status: :string | nil,
  updated_at: :utc_datetime | nil

Link to this section Functions

Link to this function

changeset(message_broadcast_contact, attrs)

View Source
@spec changeset(t(), map()) :: Ecto.Changeset.t()

Standard changeset pattern we use for all data types