Developer SysAdmin Applet

The platform console behind the applet registry: where BigLedger registers an applet — its code, vendor, store, type and the address the shell loads it from — and maintains what the store shows for it. It is not something a customer opens and has no tenant-level route into it; what it maintains reaches you as the Applet Store listing, and to have an applet added to your catalogue or a listing corrected you ask your BigLedger contact.

Overview

The Developer SysAdmin Applet is the platform console for the applet registry. It is where an applet is registered — its code, its vendor, its store, its type, the URL the shell loads it from — and where its store-facing detail is maintained: languages, images, edition and plugin pricing, which developers own it, which catalogues it sits in, and which tenants have installed it.

It is a platform applet: it does not belong to any tenant module, there is no tenant-level route into it, and it is not something a customer opens. Its tenant-facing counterpart is the Tenant Admin Applet, which governs one tenant’s users, roles and installed applets; this applet governs the registry those tenants draw from.

If you are a customer, you will never need this applet. What it maintains reaches you as the Applet Store: an applet’s name, icon, description, images, pricing and categories as the store shows them, and which applets your catalogue offers. To have an applet added to your catalogue, or a store listing corrected, ask your BigLedger contact.

Where it fits

Direction	What	Why
Downstream	Applet Store and Applet Catalog	Everything a tenant sees in the store — name, icon, description, images, pricing, categories — is the record maintained here.
Downstream	Tenant Admin Applet	A tenant’s Catalogue and Applets menus list the applets registered here; an applet has to exist here first.
Alongside	Vendor and module records	Decide who owns an applet and which module groups it.

Screens and menus

The console’s menus are Applet, Vendor, Modules, Categories and Developer:

Applet — each applet’s code (fixed once created), name, vendor, store, type, status and the help link the product opens for it, with its store detail: languages, images, edition and plugin pricing, and which catalogues carry it and which tenants have it.
Vendor and Modules — who owns an applet, and which module an applet is grouped under.
Categories and Developer — store categories and developer records.

Configuration

There is nothing for a customer to configure: only BigLedger platform staff can open this applet, and it has no settings a tenant can reach.

Fields

The forms are used by BigLedger staff only and are not described here. What reaches customers is what they produce: the applet’s name, icon, description, images and pricing as the Applet Store shows them.

Lifecycle and effects

Everything here is the platform’s applet registry. Nothing posts a journal, moves stock or creates a document in any tenant. Setting an applet INACTIVE is how it is withdrawn from the store; its code cannot be changed once it has been created.

Related applets

Tenant Admin Applet — the tenant-side counterpart. It reads the registry this applet writes.
Applet Store and Applet Catalog — the customer-facing view of the same records.
Platform SysAdmin — places the applets registered here into catalogues and stores, and installs them for users.

Troubleshooting

Symptom	Cause	Fix
An applet’s store listing is wrong or out of date	The listing is maintained here, by BigLedger	Tell your BigLedger contact what is wrong
An applet you expect is missing from the store	It is not registered, not active, or not in your catalogue	Ask your BigLedger contact