Developer

BigLedger’s platform developers register a new applet here so that the product can load it; it is not something a customer opens. Registering makes the applet known to the platform in no catalogue and installed for nobody, since placing it in a catalogue is Platform SysAdmin’s job, and deleting one does not first show the catalogues and installations that still point at it.

Your job, and the screen for it

The job	Screen or tab	Read
Register a new applet so the product can load it — BigLedger platform developers only	Applet Listing › New Applet	Fields; Lifecycle and effects
Put a registered applet in a catalogue and install it — registering alone installs it for nobody	Platform SysAdmin applet	Lifecycle and effects
Find an applet missing from your tenant’s Applet Store	Applet Store; otherwise ask your BigLedger contact	Troubleshooting
Create the vendor and store a registration needs	Vendor in Developer SysAdmin Applet; store in Platform SysAdmin › Applet Stores	Configuration

Overview

The Developer applet is the original, four-screen registration console for the platform’s applet registry: a listing of registered applets, a New Applet form, an Edit Applet form with a delete button, and a one-toggle settings page. It is a platform applet: BigLedger’s platform developers use it to register a new applet so that the product can load it. It is not something a customer opens.

The fuller console is the Developer SysAdmin Applet, which adds vendors, store listings, pricing, images and installations.

If you are a customer, you will never need this applet. What it registers reaches you through the Applet Store once BigLedger has placed the applet in a catalogue you are offered.

Where it fits

Direction	What	Why
Sibling	Developer SysAdmin Applet	The complete registry console, over the same applets.
Downstream	Platform SysAdmin	Places a registered applet into catalogues and stores and installs it for users.
Downstream	Applet Store	Where the registered applet is eventually seen and installed.

Screens and menus

Applet Listing, New Applet, Edit Applet (with Delete) and Settings, whose single toggle, 3 UI Column View, is a layout preference that is not saved and resets on reload.

Configuration

Only BigLedger platform staff can use this applet, and it has no settings a tenant can reach. An applet store and a vendor must exist before an applet can be registered, and they are made in two different consoles. The vendor is created in the Developer SysAdmin Applet; the store is created in Platform SysAdmin, under its Applet Stores menu. This applet only lists the stores that already exist, so a missing store is fixed there, not here.

Fields

The registration form records an applet’s name, code (no spaces), two-character short code, type, the address the product loads it from, its store and vendor, a description, the permissions it needs and a logo. The code cannot contain spaces; the short code is two characters by convention only. A new applet is registered as ACTIVE.

Lifecycle and effects

Registering an applet makes it known to the platform, in no catalogue and installed for nobody — placing it in a catalogue is Platform SysAdmin’s job. Deleting an applet removes it after a confirmation; the catalogues and installations that point at it are not shown first. Nothing posts: no journal, no stock, no document.

Related applets

Developer SysAdmin Applet — the same registry with vendor, store, pricing and installation management.
Platform SysAdmin — catalogues, stores and installations for what is registered here.
Applet Store — the end of the chain.

Troubleshooting

Symptom	Cause	Fix
An applet you expect is missing from your tenant’s Applet Store	It is not registered, not active, or not in a catalogue you are offered	Ask your BigLedger contact