GUI Trigger

Show the defined triggers used to create orders automatically.

There are some possibilities to select a subset of triggers:

• Type: A selection list to mark the trigger type to show.
• Name: Enter the name or a simple name pattern for selection. The search is not case sensitive. In the pattern a '*' is accepted for any character list, e.g. '*orbit*' matches 'L2_orbits_3000-3002'.

Type

There are 5 trigger types defined:

• Calendar: A cron-style trigger, which is tied to specific times of day/week/month.
• DataDriven: A trigger that fires upon ingestion of a product fulfilling certain criteria (match of product class, file class (if set) and/or processing mode (if set); trigger events may be sent by the Ingestor or by Monitors for non-prosEO pickup points (local or remote);
• Datatake: Trigger to create a processing order for an expected datatake (not completely implemented yet).
• Orbit: Trigger for the generation of processing orders per spacecraft orbit
• TimeInterval: A trigger that fires in certain time intervals.

For each trigger type are common properties defined:

Name

The name of the trigger (unique for a type).

Priority

The processing priority of a generated Order.

Order Template

The name of an order template used to generate an order.

Execution Delay

Delay between order generation time (= trigger firing time) and earliest order execution (release) time; default 0.

Enabled

Flag indicating whether this trigger is available for use (disabled triggers cannot be used for order generation).

Trigger Type Details

Calendar Trigger

Cron Expression: A cron-style expression to schedule trigger firing.
JSON example:

{   
  "missionCode" : "PTM",
  "name" : "CAL-L1",
  "type" : "Calendar",
  "orderTemplateName" : "L1-L2-Slice",
  "executionDelay" : 0,
  "priority" : 50,
  "cronExpression" : "0/0 0/30 * * * ?",
  "enabled" : false
}

DataDriven Trigger

Input Product: The product type of the input product.
Input File Class: The file class of the of the input product.
Input Processing Mode: The processing mode of the input product.
Parameters to copy: The selection of product parameters to copy the the output product(s). This is a list of parameter names or '*' for all.

{
  "missionCode" : "PTM",
  "name" : "DD-L0",
  "type" : "DataDriven",
  "orderTemplateName" : "L0-L1",
  "inputProductType" : "PTM_L0",
  "inputFileClass" : "OPER",
  "inputProcessingMode" : "OPER",
  "executionDelay" : 0,
  "priority" : 50,
  "enabled" : false
}

Datatake Trigger

Datatake Type: Not defined yet.
Delta Time: Time offset for the trigger to fire, relative to the mission planning object's start time (may be negative, which means that the event fires before the start time of the object).
Last Start Time: Start time of the last datatake, for which a processing order was generated.
Parameters to copy: The selection of product parameters to copy the the output product(s). This is a list of parameter names or '*' for all.
JSON example:

{
  "missionCode" : "PTM",
  "name" : "DT-L0",
  "type" : "Datatake",
  "orderTemplateName" : "L0-L1",
  "executionDelay" : 0,
  "priority" : 50,
  "datatakeType" : "tbd",
  "lastDatatakeStartTime" : null,
  "deltaTime" : 10,
  "parametersToCopy" : [ "Second", "First" ],
  "enabled" : false
}

Orbit Trigger

Spacecraft Code: The spacecraft whose orbit start times determine the trigger times.
Last Orbit: The last orbit for which a trigger was generated.
Delta Time: Time offset for the trigger to fire, relative to the mission planning object's start time (may be negative, which means that the event fires before the start time of the object).
JSON example:

{
  "missionCode" : "PTM",
  "name" : "O-L0",
  "type" : "Orbit",
  "orderTemplateName" : "L0-L1-Orbit",
  "executionDelay" : 0,
  "priority" : 50,
  "spacecraftCode" : "PTS",
  "lastOrbitNumber" : 3242,
  "deltaTime" : 0,
  "enabled" : false
}

TimeInterval Trigger

Next Trigger Time: The next date and time, at which the trigger is expected to fire (default setting is trigger creation time + trigger interval).
Trigger Interval: The interval between two firings of the trigger.
JSON example:

{
  "missionCode" : "PTM",
  "name" : "TI-L0",
  "type" : "TimeInterval",
  "orderTemplateName" : "L0-L1",
  "executionDelay" : 0,
  "priority" : 50,
  "nextTriggerTime" : "2026-02-26T08:01:00.722000",
  "triggerInterval" : 600,
  "enabled" : false
}