You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This feature is part of an ongoing effort to separate the process engine from the Runtime. As this feature is still in active development, it's not ready for use in production scenarios. Behavior and interfaces are subject to change.

The case engine uses its own scheduler to schedule tasks of these types:

  • Timer nodes
  • Expiration tasks

It follows the design of the Advanced Scheduler, so there is a scheduler with persistent storage that has an administration of the tasks to execute and the moment at which the task should be executed. The scheduler adds a message to the queue which will trigger the Case Engine to execute a scheduled task at the moment the task was scheduled.

Configuration

The case engine scheduler is enabled automatically when the case-engine profile is enabled. For more information on configuring Quartz for the Case Engine Scheduler, please visit Case Engine Scheduler Quartz. For more information on configuring the Case Engine Scheduler Exchange, please visit Blueriq Case Engine.

  • No labels