Proca.ActionPage (proca v3.4.1)
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
Functions
Casts and validates values to change an Action Page.
Get the name part before /
Upsert query of ActionPage by id or by name.
Link to this section Functions
all(kw)
all(query, list)
changeset(attrs)
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:
- identifier/path1/path2/path3 - where identifiers and paths are alphanumeric + - _
- 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
changeset_copy(page, original, params)
contact_schema(action_page)
create_copy_in(org, ap, attrs)
defaults(arg1)
delete(ap)
delete(multi, page)
find(id)
go_live(action_page)
kept_personalization_fields(action_page)
location(action_page)
name_domain(name)
Get the name part before /
name_path(name)
new_data(params, action_page)
one(kw)
one!(kw)
remove_schema_from_name(name)
thank_you_template_ref(ap)
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