Skip to content

Common process elements in Pantarey

When modeling processes in Pantarey, you work with various BPMN elements. They let you present workflows clearly and define them technically. Every activity stands for a concrete step – such as sending an email, executing an approval, or retrieving data.

Start events

Every process begins with a start event. Pantarey supports three types:

  • User start: The process is started manually by a user action – often together with a form.
  • Timer start: The process runs automatically at specific times or on a recurring schedule (e.g., every day at 8:00 a.m.).
  • Standard start event: Used when another process triggers this one – for example as a subprocess.

User task

This task provides a form to users. They can enter or review data.

  • Assign to specific people or groups.
  • Automatically generated form based on the linked data schema.
  • Optional: custom forms for advanced requirements.

Service task

A service task runs a predefined action automatically – without user interaction.

Typical uses:

  • Send an email.
  • Generate a document.
  • Write to FTP or SharePoint.

💡 The actions are available without coding and provided by Pantarey. The catalog is continuously expanded.

Script task

Script tasks contain custom code (JavaScript) that runs directly within Pantarey.

Examples:

  • Dynamic calculations.
  • Validations or data transformations.
  • Calling external APIs.

Database actions

Pantarey offers two activities for working with data:

  • Save data: Store information from previous tasks as a record.
  • Load data: Retrieve existing records (e.g., via filters).

Both activities work with defined data structures.

Gateways (conditions)

Gateways steer the flow.

  • Exclusive gateway (XOR): Only one path is chosen depending on the configured condition.
  • Multiple outgoing paths are possible.
  • A default path can be defined if no condition applies.

Subprocesses

Subprocesses encapsulate partial workflows in a dedicated area.

  • Reusability.
  • Structure complex flows.
  • Build large processes in a modular way.

End events

The end event marks the logical end of a path in the process.

  • Optionally include an outcome.
  • Relevant for the overview in the process monitor.

Error handling

Pantarey supports targeted error handling with error throw events.

  • Attach errors to service or script tasks.
  • Define error paths that describe what should happen if something goes wrong.
  • Every case can be traced in the process monitor.

Activity properties

Every activity in a process model has properties that determine its behavior. The available settings depend on the activity type:

  • User task: Responsible person or group, associated form, visibility conditions.
  • Service task: Selected service and its input parameters.
  • Script task: JavaScript code to run.

Configure the properties by selecting the element in the Process Designer. The properties panel appears on the right so you can adjust everything.

💡 Many properties include a help icon with detailed explanations. Proper configuration is essential. Only then do processes work as expected, tasks are assigned correctly, and data is processed reliably.