Inlorus
How-to

Add a domain and its applications

At the platform, the Domains screen is the domain catalogue: you create a domain at the top level or under another, add applications to it, rename and order them. Every account and tenant sees the catalogue and opens what it needs.

For: Platform administrator, Builder

Prerequisite

domain.write at the platform (the platform administrator holds it; domain.read is enough to look). Without it the tree is shown read only and the screen names the missing key.

Open the catalogue

  1. Switch the console to the platform.
  2. Open Domains under Settings. The screen is titled Domain catalogue and shows every domain with its sub-domains and applications, each with its key.

Add a domain

  1. For a top-level domain, type its name under New top-level domain — for example “Consulting” — and press Create domain.
  2. For a domain beneath another, press Create sub-domain on the parent's row, type the name — for example “Executive Education” under “Education” — and press Save.
  3. The screen says what was created and the key it got, e.g. executive_education.

Add its applications

  1. Press Create application on the domain's row, type the name — for example “Courses” — and press Save.
  2. Repeat for each application. Move up and Move down set their order in the domain.

Rename and order

  1. Rename on a row changes its name; its key stays as it was.
  2. Move up / Move down on a domain changes its place among its siblings.

Good to know

  • A key is made from the name once, when the row is created, and never changes. If another domain (or application) already has that key, the name is refused; choose a different one.
  • A new domain or application is open in every account and tenant where its parent is open, until one of them closes it on its own Domains & Applications screen: availability is open unless closed.
  • A new application has no runtime yet; a tenant's Applications screen says so.
  • Retire names what uses the domain (sub-domains, applications, domain fields, validation rules, EntityViews, availability settings, members' choices). When nothing uses it, Retire retires it: the row is kept, it leaves the catalogue, the availability screens and every picker, and its key stays taken. An application has its own Retire, refused while a field, A_EntityView, runtime, availability setting, member's choice or capability version uses it.
  • A domain has no description yet: a name and a key only.
  • Every change is recorded in the audit trail at the platform.