Skip to content

Triggers

Triggers hold custom logic that runs at points in a process: before or after a task, on derivation, or from a web entry. They are written once and attached wherever they are needed.

Start here

Page What it answers
This page Creating a trigger, attaching it, copying it
PHP in triggers What the code receives, how it reads and writes case data, why it failed
Lurana functions Every function you can call, with its arguments

The list

Column Shows
Title The trigger name
Description What it does
Type Custom or template-based

Click a header to sort by title or type. Show ID shows the trigger's identifier in a small dialog with a single OK: the ID is what references the trigger from code and from other processes, so it is worth noting before you copy a process.

Create a trigger

  1. Open Process objects → Triggers and choose + New.
  2. Choose a custom trigger or start from the wizard.
  3. Fill in Title and Description:
Field Limit
Title 100 characters
Description 500 characters

Both fields stop at the limit and show Character limit reached; there is no n / max counter, so the message is the only signal.

  1. Write the code, or adjust what the wizard generated.
  2. Save.

Copy a trigger

Select a trigger and choose Copy. The copy keeps the code, gets its own ID, and the confirmation says Trigger copied successfully — not the message for a new trigger, which is a common mix-up when two tabs are open.

Where triggers are used

  • Task properties — before and after a task.
  • Web entry — before the public form is submitted.
  • Report tables and database connections — a trigger can query them and store the result in a process variable.

Functions you can call

The code runs against the platform's function library: dates, text, case and task lookups, email, documents, users and groups. The function reference lists all of them with their arguments and return values.

Permissions

Editing triggers requires design permission for the process. See Permission reference.