Configuration

How the installation is set up for each object type: its subtypes, its custom properties and the layout of its forms. What a client reads before drawing a form or writing the custom_properties block of an object.

📄️ Custom properties of an object type

What an integration needs before reading or writing the `custom_properties` block of a

📄️ Define a custom property

Adds a custom property to an object type, or to one of its subtypes with `subtype`.

📄️ Change a custom property

Partial; `PATCH` behaves the same. Only the fields sent change: everything else the

📄️ Disable a custom property

Disables the property: it leaves the forms and the API's `custom_properties` blocks, but

📄️ Change how a subtype shows its properties

What a subtype changes of the custom properties of its type: label, description, whether

📄️ Subtypes of an object type

The subtypes an object type is split into (an invoice's credit and debit notes, for

📄️ Form layout of an object type

How the desktop lays out the form of an object type for the caller: its groups ('Details',

📄️ Add a group to a form

Adds a group to the form of a content object type. `name` is required; `alignment`

📄️ One group of a form

The group as it is configured: every field it holds, in order, disabled ones included,

📄️ Change a group of a form

Partial; `PATCH` behaves the same. Only what is sent changes. `fields`, when sent, is the

📄️ Delete a group of a form

Deletes the group. Its fields are left in no group, so the form no longer draws them until