A reference that is refused, and other things Contents says
What each message in the Contents section means, and the permission each task needs.
What Contents says, and who can change it
| What you see | What it means |
|---|---|
| "This version carries nothing yet" | No reference has been added. The version can still be published; its lock records nothing. |
A reference marked refused | It cannot be carried; the sentence says why. Remove it, or fix the artefact, before publishing. |
| "a published version's contents do not change" | The version is published: its contents are its lock. Changing what the package carries takes a new version. |
| "published before the manifest existed" | The version was published before contents could be recorded, so nothing is locked for it. |
| "no storage for a capability's contents yet" | This database does not have the contents' storage yet. Nothing can be added; publishing works as before, without a lock. |
Tip A platform workflow is carried at its published version, with the actions its effects run; an entity brings its validation rules, computed fields and record actions. Forms are listed under What a package can carry as not yet carried, with the reason. An application's runtime is authored at the platform in the Application Runtime Designer; reference records in the Metadata Designer, on a reference entity's page.
| Task | Permission key needed (in the platform scope) |
|---|---|
| See the contents | capability.read |
| Add or remove a reference | capability.write |
| Publish and lock | capability.publish |