Skip to main content

process-automation-beam


1.2.0 (2026-08-04)

  • Updated process-automation-component to version 1.14.1

Migration guide

  • net.democritus:Expanders::9.4.0 is required, if net.democritus:Expanders is used.
    -> Use minimal-jee-beam::2.2.0+ or remove net.democritus:Expanders from the dependencies completely
  • net.democritus:web-styles-expanders::2026.4.0 is required, if net.democritus:web-styles-expanders is used.
    -> Use minimal-jee-beam::2.2.0+, knockout-frontend-beam::1.0.0+ or remove net.democritus:web-styles-expanders from the dependencies completely
  • net.democritus.enumtypes:enum-type-expanders::2.5.0 is required, if net.democritus.enumtypes:enum-type-expanders is used
    -> Use net.democritus.bundles:enum-type-bundle::2.5.0+
  • When making use of the new TimerJobService (see below), a database migration is necessary. More info here.
  • Adapt custom code if compilation errors occur. This will only be necessary when the custom code uses one of the (re)moved methods from the internal process-automation classes.

New features

  • Added TimerJobService to schedule jobs at a specific point in time.
    • Enabled through the processAutomation.TimerJob.enable option or #processAutomation.timerJob tag.
  • Added FieldTimer trigger based on the timestamp of a field.
    • Added option trigger.timer.offset to add an offset to a FieldTimer trigger.

Stability and fixes

  • Fixed missing error handling issue when cancelling processing policy timers.
  • Fixed ApplicationPersistence queue crashing due to fetch timeout. Will now retry the fetch instead.
  • Fixed ApplicationPersistence claim query to make use of the status index if available.
  • Add semaphore to control the amount of jobs submitted to the ThreadPoolExecutor.
  • Improved /healthcheck stability by watching lastUpdatedAt and allowing more states to be considered active.
  • Moved various methods between internal classes to improve interfaces.

Known issue

  • The asynchronous executor sometimes fails to schedule tasks, essentially halting some workflows. A workaround for this is to use the ExecutorService processing instead of Asynchronous processing. See Processing Types.
    • This issue can occur in any of the process-automation-beam versions when used in combination with Jakarta

1.1.0 (2026-02-04)

Changed

  • Updated process-automation-component to version 1.12.2

Removed

  • Breaking change: findByIsLeaderEq, findByStatusSe and findByRequestSe finders of the WorkerNode data element have been removed from the view layer

1.0.0 (2025-08-14)

  • Created process-automation-beam project.

Added

  • process-automation-component:1.10.1