The package

Contents: adding what the package carries

Each kind of artefact a version can carry, what it pulls in, and how it is added and published.

Contents: what the package carries

The Contents section belongs to the capability's latest version. Each reference is listed with its kind, name, key, owner and state — carried or refused with the reason — and a tree of what it pulls in.

You addIt pulls in
An entityIts fields, its ISA parents (and theirs), and every relation definition whose both ends the package carries, with its relation type.
An EntityViewIts entity (as above) and its domain; locked at its latest active version.
An applicationIts domain; its platform runtime at the published version, with that version's workspaces, navigation and default workspace; and the platform's A_EntityViews of it, each with the EntityView it narrows. Without a published platform runtime it is carried as its catalogue row, and the contents say so.
A role, a configuration value, an onboarding journey, a help topic, a domainItself: a role with its permission keys, a value as it is set, a journey at its latest published version, a topic at its current text.
Reference dataA reference entity's records, as published at the platform in the Metadata Designer; it brings the entity with its fields. Locked with a fingerprint of the records as they are at publish. Only an entity whose role is Reference, with at least one record, can be added.
Sample dataA dataset of this version's own Sample data section: its rows, by entity, and the links between them; it brings the entities the rows hold. Locked with a fingerprint of the rows. A dataset is in the contents as soon as it is created.
  1. In Add to the contents, choose a Kind. The sentence under it says what that kind brings.
  2. Choose the artefact from the list. Only what the platform owns is offered; if the platform owns nothing of that kind, a sentence says so instead of an empty list.
  3. Press Add. The reference appears in the list with what it pulls in; Remove takes it out again.
  4. Under At publish, read how many artefacts will be locked, then press Publish version N.

At publish every reference is checked again. A reference to something that no longer exists, that belongs to a tenant, or that the platform cannot ship is refused: the version is not published and the refusal says which reference and why. Otherwise the version is published and the Dependency lock is recorded: every carried artefact — chosen and pulled in — with its revision and fingerprint.