A new custom object type defines its own attributes, place in the application hierarchy, relations, ownership, and behavior. For how object types fit into an application, see Custom applications.
For more information, see Object types.
Prerequisites
- Only administrators can define object types here.
- New object type adds a type to an existing application. For an application with a marketplace package, the type is added as an extension, so the original package stays untouched.
Your work stays in the browser tab until you finish; nothing is stored on the server before that. Leaving the page asks Discard this wizard?, while reloading or closing the tab triggers the browser’s own warning instead. Either one discards your work.
Open the New object type page
| Where | How to open it | Last step | When the object type is saved |
|---|---|---|---|
| New object type | In the top navigation, click the arrow next to Create and select New object type. | Review & create | Right away, when you click Create object type. |
| Application editor | Click + Add object type on the Object types step of New application or Edit application. | Page layout tab | Together with the application, when you create or save it on its last step. |
The editor adds a Page layout tab. Move between tabs freely.
Set the basics
The Basics step names the object type.
| Field | What you set |
|---|---|
| Application | Steps only, required. The application that receives the object type. For a marketplace application, a banner names it as an extension. |
| Name | Required. The singular name users see when creating objects of this type. |
| Icon | Pick an icon from the standard icon library, or click Upload SVG to use your own (see Upload a custom icon for the rules). To clear the icon, click Remove icon, or click the selected icon again. |
| Description | A description of the object type. |
Add attributes
The Attributes step chooses what objects of this type record. Add standard attributes to your object type, or create custom ones.
Custom attributes can also be added later from the application editor, or on their own with New attribute.
| Standard attributes | Custom attributes | |
|---|---|---|
| What it is | Attributes that already exist in Dawiso, each showing its value type and features, such as required, searchable, filterable, or AI summary. | Attributes defined only for this object type. |
| When to use | Reuse where possible; it keeps search, exports, and AI features consistent. | When no standard attribute fits. |
| How to add | Search the catalog and select the ones you need. Description is pre-selected. | Use the quick-add row at the bottom of the table: type a name, pick a Value type (starts as Text, then remembers your last choice), optionally select Required, Searchable, or AI summary, then press Enter. |
A custom attribute installs together with the object type.
A few things to know about custom attributes:
- Dropdown or Code: Gets an extra field for its options or language; see New attribute’s Behavior step for how these work.
- Matching a standard attribute: If the name you type matches one, a suggestion offers Use ‹name› instead or Keep creating new. Reuse where you can.
- Duplicate or installed: A duplicate name is flagged under the row; an installed attribute’s value type is locked, so remove and re-add it to change that.
- Shared attribute: Changing one applies to every object type that carries it.
- Remove: Asks Remove attribute ‹name›? first. An attribute that hasn’t been created yet is simply dropped; one that already exists has its values deleted when you save, with the review showing how many beforehand. A shared attribute stays on the object types you’re not removing it from.
In the application editor, a custom attribute can belong to several object types after you duplicate a type; duplicating works the same way as in New application.
Add relations
The Relations step connects the object type to other object types.
Select any object type to connect to using the default relation. Here you can:
- Click the dropdown to select a different default relation.
- Hover on the selected object type and click + another relation to add more relation to the same object type.
- Use the Create a new relation option. Enter a Name and, optionally, a Name from the other side (defaults to the same name if left empty). Click Use new relation.
Any relations set on another object type are listed as read-only. Click edit there to open that type’s Relations tab.
You can also:
- Click + Connect an object type from another application to search for other applications’ object types and add the one you pick.
- Enable Synonyms to let objects declare other glossary objects as synonyms.
Installed relations are locked to their object type and can’t be swapped for another relation type. Only their names stay editable. Deselecting or removing one asks first, since objects lose relations of that kind they already have.
Define the structure
The Structure step places the object type in the application hierarchy; relations are set on the Relations step.
Hierarchy
Configure the following:
- Can be placed under selects the object types that can contain this type, making them its parents. The first option, ‹type› (this type), lets objects sit under others of the same type.
- Can contain selects the object types this type can contain; leave it empty if objects of this type have no children.
The Preview shows the application hierarchy with this object type marked NEW. A type placeable under itself is marked ↻; two types placeable under each other are marked ↔.
The same type can be picked in both fields, letting two types sit under each other; an info box confirms it, also counting a type that lists this one under its own Can contain. The options come from the same application; its overview page isn’t offered as a parent.
Once the object type has at least one parent (set here, or via another type’s Can contain, but not by nesting under itself), you can restrict where new objects go:
| Option | Effect |
|---|---|
| Anywhere | Default. New objects can be created anywhere in the hierarchy, including at the top level. |
| Only under a parent | New objects can be created only under an object of a parent type. |
Only under a parent needs at least one parent type, and resets to Anywhere if the object type loses its last one. Dawiso also rejects a loop where a type and its only possible parents all require a parent to create the first object; allow one of them to be created anywhere instead.
Configure governance
The Governance step decides who’s responsible for objects of this type and how they’re classified.
Ownership
Assign ownership is on by default, requiring a business owner and a steward (pre-selected under Roles, though you can change them); at least one role is required while it’s on. Roles offers only core roles plus the application’s own, with no retired legacy roles.
Classification & documentation
Each option is on by default:
- Labels: Objects can be tagged with labels from code lists.
- Areas: Objects can be assigned to business areas.
- Documentation: Objects can link documents and document sets.
Define behavior
The Behavior step controls how objects of this type are created, drafted, and found; each option maps to an object type feature (see features (OT) for the technical reference). On this step, a draft is a new object that isn’t published yet; elsewhere in Dawiso, drafts are called concepts.
Object creation
| Option | What it does | Default |
|---|---|---|
| Publish new objects immediately | Skips drafts, objects visible only to their creator until published. Unrelated to workflow states. Recommended for most use cases. | On |
| Only editors and admins can create | Contributors can’t create objects of this type. | Off |
Drafts & workflow
Available only when Publish new objects immediately is disabled.
| Option | What it does |
|---|---|
| Allow comments on drafts | People can comment on an object while it’s still a draft. |
| Check workflow roles when publishing a new draft | Publishing a brand-new draft needs the same workflow role as publishing an existing object. |
Search
- Domain type is required; it categorizes the object type in search results. Dawiso suggests one from the name and description, and you can change it.
- Match keywords by exact name only: when texts are linked to objects automatically, objects of this type match only their exact name. This matters when Keyword search of authored content is on, which is recommended and on by default.
Page layout
Available for the application editor.
It previews the generated object page based on what you set elsewhere. If the page would be empty, it names what to add: an attribute, a relation, ownership, labels, areas, documentation, synonyms, or related objects; child types alone don’t fill it. You can customize the layout later.
Review & create
New object type ends on Review & create; the application editor has no per-type summary, since its own last step already covers every object type. The summary shows one row per area:
- Application
- Object type
- Attributes
- Relations
- Position
- Governance
- Behavior
- Search, where you can also change the Domain type directly
A What will be created card names the object type, its placement, and where the result is stored: in the application’s configuration package, or an extension of it for a marketplace application.
Click Create object type to install it.
Installation status
This section applies to New object type. In the application editor, the object type is installed with the application. See Installation.
| Status | What you see | What you can do |
|---|---|---|
| Installing | ”Creating object type ‹name›… This can take a few minutes. Keep this page open until it finishes.” | Wait. |
| Installed | ”Object type ‹name› was created.” and “You can open it now or create another one.” | Click Open application or Create another object type. |
| Installed with warnings | Installed with warnings with the list of warnings. | Click Open application or Create another object type. |
| Failed | ”The object type could not be installed.” with the reported issues and the package name. | Click Run the installation again, Open Settings › Packages, or Start over. |
| Installed, but not found | ”The object type could not be installed.” with “The package was installed, but the new item could not be found in it.” and the package name. | Click Open Settings › Packages or Start over. |
| Taking too long | ”Installation is taking longer than expected. Check Settings › Packages for the package ‹package›.” | Click Open Settings › Packages or Start over. |
| Status unreachable | ”The installation status of the package ‹package› cannot be reached right now. Check your connection and try again.” | Click Check again, Open Settings › Packages, or Start over. |
When the installation fails, choose how to continue:
- Click Run the installation again when the failure was temporary. Dawiso validates and installs the same draft version again, and the screen shows the progress. If the installation can’t be started, the screen shows “The installation couldn’t be started again. Reload the page and try again.”
- Click Start over, define the object type again with the corrected input, and create it. Dawiso replaces the failed draft version and installs the new one.
A failed installation doesn’t block the package. A draft whose installation is still running, or a draft that was created in Settings > Packages and never installed, still blocks the package. See Troubleshooting.
Troubleshooting
Name and application
| Message | What to do |
|---|---|
| ”Enter a name for the object type.” | Enter a name on the Basics step. |
| ”Select an application.” | Select the application on the Basics step. |
| ”We couldn’t load the applications.” | Click Retry on the Basics step. The message appears instead of the Application list when the applications can’t be loaded. |
| ”An object type with this name already exists. Choose a different name.” | Rename the object type on the Basics step. |
Attribute values
| Message | What to do |
|---|---|
| ”An existing attribute can’t change its value type — the values objects already hold would no longer fit it.” | Keep the value type. To change it, remove the attribute and add a new one. |
Structure and governance
| Message | What to do |
|---|---|
| ”Select at least one role.” | Select a role under Ownership, or turn off Assign ownership. |
| ”Restricting where objects are created needs at least one parent type.” | Add a parent under Can be placed under, or set Where can new objects be created? to Anywhere. |
| ”Objects of this type can be created only under a parent, but its parent types can only be created in a loop through this type, so the first object could never be created. Allow this type, or one of its parent types, to be created anywhere.” | Set Where can new objects be created? to Anywhere for this type or one of its parents. |
Behavior and search
| Message | What to do |
|---|---|
| ”Select a domain type.” | Select a Domain type on the Behavior step. |
| ”Comments on drafts cannot be combined with publishing new objects immediately.” | Turn off Publish new objects immediately, or turn off Allow comments on drafts. |
| ”One of the selected features is not available in this wizard.” | Review the options on the Behavior step and try again. |
Layout preview
| Message | What to do |
|---|---|
| ”Objects of this type would get an empty page. Add an attribute or a relation, or turn on ownership, labels, areas, documentation, synonyms or related objects. Child types alone do not fill the page.” | Add an attribute or a relation, or turn on a connection such as ownership, labels, areas, documentation, synonyms, or related objects. |
| ”The layout preview could not be loaded.” | Click Reload preview. |
Creating the object type
| Message | What to do |
|---|---|
| ”The text ‹translation key› has no translation. Choose another value, or add the translation in Settings › Translations.” | Choose another value, or add the translation in Settings > Translations. New object type reports it after you click Create object type and creates nothing. The application editor lists it on the review screen. |
| ”A draft version of this configuration package is still being installed or is waiting in Settings › Packages. Wait for the installation to finish, or install or discard the draft there.” | Wait for the installation to finish. Otherwise install or discard the draft in Settings > Packages > Resources, then create the object type again. |