Properties & Actions
Module Summary
Understand how Properties describe objects and how Actions allow users to write back — editing, creating, or deleting objects safely.
Properties in Depth
Each Property on an Object Type has a name, a type, and an optional description. Properties can be marked as searchable, filterable, or orderable — controlling how they appear in Object Explorer and Workshop filters.
Derived Properties go a step further: they compute values on the fly using Functions (e.g., "Days Since Last Order" calculated from the order date).
Introduction to Actions
Actions allow users to write back to the Ontology. Instead of giving people direct database access, you define an Action Type that says exactly what can be changed, by whom, and under what validation rules.
For example, an "Update Employee Department" action might require a reason, validate against a list of allowed departments, and trigger a notification to HR — all configured without code.
Action Validation and Side Effects
Every Action can include validation rules (e.g., salary must be positive), submission criteria (e.g., must be a manager), and side effects like sending emails, triggering webhooks, or creating follow-up objects.
Because every action execution is logged, you get a complete audit trail of who changed what and when — critical for regulated industries.
Key Takeaways
- Properties describe objects with typed, searchable fields.
- Actions let users write back to the Ontology through controlled forms.
- Validation rules and permissions make Actions safe for production use.
- Every action execution is logged for full auditability.