Skip to main content

Document Start Event

Introduction​

A document start event begins a new process instance when a document lifecycle event matches the configured filter. The event creates one engine subscription per selected lifecycle and starts a fresh process instance on every matching dispatch.

Process-level start variants have a few restrictions compared to the activity-bound variants:

  • The instance and scope location rows are not allowed, because no running scope exists yet at deploy time.
  • The filename filter is not allowed, because the instance would already have been spawned before the filter could reject the match.
  • The list variable name is not allowed, because appending requires a running scope.

A document start event placed inside an event sub-process does not have these restrictions: it is activity-bound to the parent process instance and supports filename filters, instance / scope locations, and the list variable. Interrupting and non-interrupting flavours behave like any other event sub-process start.

For the full configuration model (events, locations, filename matcher, variables) see Document Events.