Automation and scheduled processing
Keep authorised business and platform processes running even when users are not actively working in Velaxe.
Move from setup to connected operations
1
Background processing
Some work should continue without a user keeping an application open. Velaxe provides a scheduler, queue and worker environment for platform and application jobs.
2
Examples of scheduled work
3
Application context and boundaries
Application jobs run inside the authorised workspace and application context so the same storage and security boundaries apply in the background.
4
Connected operations
Automation can work with the event system and authorised application communication to support workflows that span more than one application.
Explore the platform from different angles
Some work should continue without a user keeping an application open. Velaxe provides a scheduler, queue and worker environment for platform and application jobs.
- Application-specific recurring jobs.
- Event delivery and retry.
- Subscription-cycle billing and entitlement checks.
- Workspace size scanning.
- Scheduled application publishing.
- Analytics rollups and retention.
Application jobs run inside the authorised workspace and application context so the same storage and security boundaries apply in the background.
Automation can work with the event system and authorised application communication to support workflows that span more than one application.
A closer look at how the platform works
Examples of scheduled work
- Application-specific recurring jobs.
- Event delivery and retry.
- Subscription-cycle billing and entitlement checks.
Application context and boundaries
Application jobs run inside the authorised workspace and application context so the same storage and security boundaries apply in the background.
Connected operations
Automation can work with the event system and authorised application communication to support workflows that span more than one application.