Creating and using augmented attributes

Standardization of business logic: You can encode business rules once (e.g., “On-Time Delivery,” “High-Value Customer,” “Late Payment”) directly in the Data Model. Every View and user in your team then uses the same consistent logic, preventing discrepancies.

Re-usability across Studio assets: Once you define augmented attributes in a View, all analyses built on that View can reuse them.

Improved performance: Augmented attributes are pre-computed when the View is processed. This means dashboards and analyses using the View load faster than if the same logic were implemented as calculated fields.

Encapsulation of business context: Augmented attributes let you embed business meaning directly into the View. Instead of exposing only raw data (like timestamps, IDs, or codes), you can expose interpreted attributes (like “Late Delivery,” “Payment Delay Category,” etc.).

Governance and version control: Since Views are versioned and managed separately from the base data model, augmented attributes defined in Views support controlled evolution of business logic. You can safely test or adjust logic in a View without impacting other models or analyses.

With the augmented attribute appearing under the Data Model table to which it has been added, you can use it as a reference in your components. When using the augmented attribute in this way, the autogenerated PQL will be consistently correct even if the configuration of the attribute changes.

Each augmented attribute has it's own table in the Data Model. With this table, more advanced information can be extracted (such as the time of the last update or the user who performed it).

This table uses the following naming convention:

<data model table>_AUG_<Augmented Attribute Name>

When configuring a table component within a View, you can assign augmented attributes and enable inline editing of the data displayed per column.

To enable inline editing for a table column, click the column configuration icon and then select Cell Interactions - Inline Editing:

For example, the invoice status column in this table is based on an augmented attribute. When inline editing is enabled, the app user can edit this table column to update the current status of the invoice from Open to In Progress.

Updates to augmented attributes are kept regardless of the user's team or Celonis Platform status. As such, if a user is removed from a team, any augmented attributes they have updated will remain in their updated state.

The table in the data model you assign the augmented attribute can have a maximum of 150 million rows.

The maximum number of augmentation tables per data model is 200.

The maximum number of values per augmented attribute is 200k (however rows containing the default value are not included).

Table names and column names in your data model can't contain spaces. For example, you should use "VENDOR_INFO" instead of "VENDOR INFO" as a table name.

Any tables you want to use must have a primary key (also known as an identifier) set in the data model. For more about identifiers, see: Setting identifiers.