iVendNextDevelopers Request a sandbox

One settings page that drives the shop's rules

The customer asks: Change the limits and who is told in one settings page, not in each rule

What you build

A settings record of your own (named Default); when it is saved, your service copies its values into the save rules' limits and the notifications' recipients it names. Recipe section A settings record that drives rules; S22's settings_sync (a standalone, tested function S22 itself does not call).

Limits

Tell the customer

The limits and the people told are changed in one settings page, and the rules follow within seconds.

What next

  1. Tell the customer the 3 limits above, and write them into the proposal.
  2. Follow the recipe: Reading iVendNext's events reliably.
  3. Copy the sample: S22 — Customer-owned loyalty (pp_lyl): your logic outside, the records inside the shop, and change it.
  4. Build and test it on your sandbox (request one if you have none; what is on it).
  5. Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
  6. Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.

Stop your service for a while and start it again: it must catch up from the event feed, missing nothing.

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit