Skip to content
Permalink
Browse files

Updated based on feature #343 - sync_locations_on_merge and sync_beac…

…ons_on_merge
  • Loading branch information...
lmmendes committed Jun 13, 2019
1 parent 242c30f commit f7ca822368d8ded8dd3fc54d6bec78d1e1c66e0e
Showing with 15 additions and 0 deletions.
  1. +5 −0 CHANGELOG.md
  2. +2 −0 v2/sections/coupon.md
  3. +2 −0 v2/sections/event_ticket.md
  4. +4 −0 v2/sections/generic.md
  5. +2 −0 v2/sections/store_card.md
@@ -3,6 +3,11 @@
This file is a manually maintained list of changes for each release. Feel free to add your
changes here when sending pull requests. Also send corrections if you spot any mistakes.

## v2.9.1 (2019-06-08)

* Feature
- Ability to opt-out syncing of geo-locations and beacons collections while updating the campaign by setting sync_locations_on_merge and sync_beacons_on_merge flags to false. This allows that you to update a campaign and merge it with the passes without overriding the beacons and locations defined per pass. (lmmendes)

## v0.7.0 (2018-11-24)

* Documentation
@@ -175,6 +175,8 @@ The `code_type` indicates the type of numbering that is going to be applied to t
| user_info | hash | Optional. This field can be used to store user related data. On Apple Wallet this field will be available as a JSON encoded string. |
| max_distance| Integer | Optional. Maximum distance in meters from a relevant latitude and longitude that the pass is relevant. This number is compared to the pass’s default distance and the smaller value is used. Maximum 1000 meters for Event Tickets and 100 for everthing else. |
| remote_form_url | url | Optional. Please see [advanced features](https://github.com/passworks/passworks-api/blob/master/v2/sections/advanced-features.md). |
| sync_locations_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign locations are synced or not with the passes when the campaign is updated.|
| sync_beacons_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign beacons are synced or not with the passes when the campaign is updated.|


### Code Type (code_type)
@@ -151,6 +151,8 @@ In case of success HTTP 201 response code is returned with the following body co
| stylesheet | String | CSS that will be rendered inside the download page and form, allows users to override the page css |
| user_info | hash | Optional. This field can be used to store user related data. On Apple Wallet this field will be available as a JSON encoded string. |
| remote_form_url | url | Optional. Please see [advanced features](https://github.com/passworks/passworks-api/blob/master/v2/sections/advanced-features.md). |
| sync_locations_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign locations are synced or not with the passes when the campaign is updated.|
| sync_beacons_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign beacons are synced or not with the passes when the campaign is updated.|


### Field hash object format
@@ -154,6 +154,10 @@ Response
| og_description | String | Open Graph description. Optional, default: "" (empty string)
| javascript | String | Javascript that will be rendered inside the download page and form, Allows the user to run their own javascript code eg: Google Analytics or Facebook Pixel |
| stylesheet | String | CSS that will be rendered inside the download page and form, allows users to override the page css |
| user_info | hash | Optional. This field can be used to store user related data. On Apple Wallet this field will be available as a JSON encoded string. |
| remote_form_url | url | Optional. Please see [advanced features](https://github.com/passworks/passworks-api/blob/master/v2/sections/advanced-features.md). |
| sync_locations_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign locations are synced or not with the passes when the campaign is updated.|
| sync_beacons_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign beacons are synced or not with the passes when the campaign is updated.|

### Field hash object format

@@ -143,6 +143,8 @@ NOTE: The API date fields (e.g `created_at`, `updated_at`) use the [ISO-8601](ht
| stylesheet | String | CSS that will be rendered inside the download page and form, allows users to override the page css |
| user_info | hash | Optional. This field can be used to store user related data. On Apple Wallet this field will be available as a JSON encoded string. |
| remote_form_url | url | Optional. Please see [advanced features](https://github.com/passworks/passworks-api/blob/master/v2/sections/advanced-features.md). |
| sync_locations_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign locations are synced or not with the passes when the campaign is updated.|
| sync_beacons_on_merge | boolean | Optional. Default `true`. Allows you to choose if you with that campaign beacons are synced or not with the passes when the campaign is updated.|

### Field hash object format

0 comments on commit f7ca822

Please sign in to comment.
You can’t perform that action at this time.