Components
Components are the building blocks of custom logic in Hantera. They contain code written in Filtrera that can be executed in different contexts to automate workflows, expose APIs, enforce business rules, and calculate dynamic pricing.
Use Cases
Jobs
Components are wrapped in job definitions to enable scheduling:
- Process orders at night
- Generate reports
- Clean up old data
- Sync with external systems
Learn more about Job Definitions → | Learn more about Jobs →
Ingresses
Expose components as APIs:
- Custom HTTP endpoints
- Webhook handlers
- Message queue processors
- Integration APIs
Rules
React to system events and actor lifecycle hooks:
- Execute logic when orders are created, updated, or deleted
- Trigger actions on payment captures or refunds
- Automate workflows based on entity state changes
Discounts
Calculate dynamic discounts on orders:
- ComputedDiscounts re-evaluate whenever an order changes
- Pure calculation components (no side effects)
- Persist throughout order lifecycle, even after promotion ends
Learn more about Order Discounts →
Access Control
The ACE for components looks like this:
components[/<id>]:read|write