Proca.ActionPage (proca v3.0.2)

Action Page belongs to a Campaign, and represents a page (widget) where members take action.

Action Page accepts data in many formats (See Contact.Data) and produces Contact and Supporter records.

Link to this section Summary

Link to this section Functions

Link to this function

all(query, list)

Link to this function

changeset(attrs)

Link to this function

changeset(action_page, params)

Casts and validates values to change an Action Page.

The name validation is a pattern that allows two styles of action names:

  1. identifier/path1/path2/path3 - where identifiers and paths are alphanumeric + - _
  2. domain.com.pl/some/campaign - url style (very similar but _ is not allowed for domain part) See test/action_page_test.exs for examples of valid and invalid names
Link to this function

contact_schema(action_page)

Link to this function

create(chset, kw)

Link to this function

create_copy_in(org, ap, attrs)

Link to this function

go_live(action_page)

Link to this function

kept_personalization_fields(action_page)

Link to this function

location(action_page)

Link to this function

name_domain(name)

Get the name part before /

Link to this function

name_path(name)

Link to this function

new_data(params, action_page)

Link to this function

remove_schema_from_name(name)

Link to this function

update(chset, list)

Link to this function

upsert(org, campaign, attrs)

Upsert query of ActionPage by id or by name.

org - what org does it belong to campaign - what campaign does it belong to attrs - attributes. The id and name will be tried in that order to lookup existing action page. If not found, it will be created.

XXX what about live status ? probably the upsert API needs to have an optional live=true param