proca v3.4.1
proca

Proca.Stage.Event (proca v3.4.1)

Define JSON format for events in proca system.

These events are mostly CRUD operations that happened on different records.

If and only if the org has custom_event_deliver or event_backend set, a special message with schema "proca.event.2" will be injected into deliver queue, along action data.

If instance org has events enabled, it gets events from ALL orgs.

The event backend enables you to send events to SQS or webhook, and the custom_event_deliver means events are stored in custom delivery queue you can read.

Link to this section Summary

Functions

emit(event, record, org_id, opts \\ [])
metadata(event, record)
put_data(data, atom, confirm, opts)
routing_key(event, arg2)

Routing key for the event message is two-element topic routing key for confirms (because they have subtype), and one element key for CRUD events.

Link to this section Functions

Link to this function

emit(event, record, org_id, opts \\ [])

Link to this function

metadata(event, record)

Link to this function

put_data(data, atom, confirm, opts)

Link to this function

routing_key(event, arg2)

Routing key for the event message is two-element topic routing key for confirms (because they have subtype), and one element key for CRUD events.

Examples:

  • confirm_created.add_staffer - for new add_staffer confirm XXX remove!
  • supporter.email_status_changed
  • system.campaign_updated - for any campaign update