iVendNextDevelopers Request a sandbox

Your own records in iVendNext Desk

The customer asks: Keep our own records, such as a warranty register, in iVendNext with their own screens and print formats

What you build

A manifest declares your record types, fields, print formats, notifications and workspaces, with native screens; they can be listed under ours.

Limits

Tell the customer

Your records live in iVendNext Desk, with their own screens, lists and reports.

What next

  1. Tell the customer the 1 limit above, and write it into the proposal.
  2. Follow the recipe: Shipping your own data in a manifest.
  3. Copy the sample: S2 — bin locations (pp_bln): where stock sits inside a store, 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.

Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.

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

This card in the kit