Registered Application

An app's event feed: the record types it follows. A manifest installs it.

Area: Your app: its install, its user and its doors · Why it is here: contract event_feed; recipe event_feed; recipe integration_user; recipe system_sync · Fields: 4

iVendNext's own description: This registry is site-wide and carries no company dimension: every registered application receives document change events for every company on this site.

Read and write it

Every call runs as your app's own user, with its key in one header, at the retailer's own address. The user reads and writes only what its role allows: your app's user, and the rights the retailer gives it.

Read a list (only name unless you ask for fields):

curl -s "https://⟨site⟩/api/resource/Registered%20Application?fields=%5B%22*%22%5D&limit_page_length=20" \
  -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Read one, with its tables:

curl -s "https://⟨site⟩/api/resource/Registered%20Application/⟨name⟩" -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Your app reads it; it does not write it here: your manifest installs it (registered_applications). All the record calls and their answers: the API reference.

Samples that use it

s7_system_sync · s9_bi_feed · s22_customer_loyalty

Fields

Read from the product at POS 2.1.0.667 (till app 60147699c): its own fields, the fields iVendNext adds to it, and iVendNext's changes to any of them. Read-only fields are set by iVendNext; a hidden one is not on the form but can be read. Every record also has name (its id, in the address), owner, creation, modified, modified_by and docstatus (0 a draft, 1 submitted, 2 cancelled), all read-only.

Table: Registered Application Events

The rows of registered_application_events. Each row also has idx (its place), parent, parentfield and parenttype.

All record types · What you can use

This record type in the kit