Quick start

The first ten minutes: the palette, the update set panel, and the three settings worth changing before anything else.

Installed, and on an instance. This is the order that gets you to the useful parts fastest.

Press `/`

Anywhere on the instance, outside a field. Type two letters of a table name and press Enter.

That one box reaches most of the product. /incident -a -u5d is an active incident list updated in the last five days. /br assign finds business rules with "assign" in the name. /sysid with a pasted 32-character id finds which table owns it.

If / does nothing, you are in a field. Click outside it and press / again.

Look at the panel

The button in the corner of the instance opens it. The top of it is what is worth knowing first: the profile you are on, the application scope, and the active update set, always visible, without opening a form to check.

While you are there, the guard is already running. If you save something that would land in Default, you are told at the save rather than at release time.

Turn on Auto-Insert if you are building

Only if you are working on tables the platform does not track. It captures your saves into the active set as you go. It cannot capture what happened before you armed it, which is what the Orphans button is for.

Three settings worth a look

Open settings from the panel, or type /settings.

Profiles. A profile carries your scripts, your snippets, your custom commands and your preferences. One per customer, or per kind of work, is the usual arrangement, and switching is one click.

The assistant's permissions. Four switches, all off, and they stay off until you decide otherwise. What each one unlocks is worth two minutes before you turn any of them on.

Instances. If you work across more than one, list them here. That is what /env, /diffenv and the alignment check read.

Then learn three commands

/tt for dark mode across the whole instance, with no reload.

/code <text> to search every script field on the instance, including the tables the platform's own code search leaves out.

/bgp on the background script page, for history, output, and what the run actually changed.