Ontology Actions in Depth
Configure complex action types with validation rules, webhooks, notifications, and side effects.
1 · Complex Action Types
Beyond simple property edits, Action Types can:
- Create new objects (e.g., open a new ticket).
- Delete objects with confirmation gates.
- Modify multiple objects in a single atomic operation.
- Chain actions — one action's completion triggers another.
Each action type is configured with typed parameters, default values, and user-facing descriptions.
2 · Validation Rules and Submission Criteria
Validation rules run before the action executes:
- Field-level: "Salary must be between 30,000 and 500,000".
- Cross-field: "End date must be after start date".
- Ontology-aware: "Employee must not already be assigned to this project" (queries the Ontology live).
Submission criteria control who can execute the action based on roles, groups, or dynamic conditions.
3 · Side Effects and Webhooks
After an action completes, side effects can trigger:
- Send an email notification to the affected team.
- Fire a webhook to an external system (e.g., update a CRM).
- Create a follow-up object (e.g., generate an audit record).
- Enqueue another action for background processing.
Side effects make Actions a complete workflow engine, not just a data entry form.
✅ Key Takeaways
- Actions can create, edit, delete, and chain operations atomically.
- Validation rules and submission criteria enforce business logic before execution.
- Side effects trigger emails, webhooks, and follow-up actions automatically.
- Every execution is logged for full auditability.