-
Notifications
You must be signed in to change notification settings - Fork 3
GUI Order Template
Show the order templates used to create orders automatically.

There are some possibilities to select a subset of order templates:
- 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'.
- Product: A multiple selection list to mark the output product types of the order templates to show.
The order template name has to be unique in the current mission.
One of these predefined slicing types:
- CALENDAR_DAY
- CALENDAR_MONTH
- CALENDAR_YEAR
- NONE
- ORBIT
- TIME_SLICE
The requested output product class(es) out of the list of defined product classes.
The output file class.
The processing mode.
is one of
- SYSTEMATIC, standard systematic productions applied.
- ON_DEMAND_DEFAULT, the production is the result of an on-demand processing request with default workflow options applied.
- ON_DEMAND_NON_DEFAULT, the production is the result of an on-demand processing request with non-default workflow options applied.
After passing of this period in days the product file(s) are deleted, the product metadata is kept. As default this time is not set.
The processing priority of a generated Order.
The template is usable if it is enabled.
The generated order will be released automatically.
The generated order is closed automatically after completion of all job steps.
The select ed set of configured processor(s) for processing the order (see Find The Applicable Configured Processor).
The wait period for input products. After this the action is: if Set state to FAILED after timeout is true, the job step state is set to FAILED. otherwise it is set to READY (to try if it possible to get a product without the missing input).
The URI used to notify the Processing Order originator of the order completion (allowed protocols are "http:", "https:", "mailto:", "http:" only if no authentication is required).
The username to authenticate with (using Basic Authentication).
The password to authenticate with (using Basic Authentication), mandatory if username is given.
The input filter is used to search for input products with particular parameter (attribute) values. The parameters are grouped by product classes. Each parameter is defined by a key, a data type and a value.

"inputFilters" : [ {
"productClass" : "PTM_L1B_P1",
"filterConditions" : [ {
"key" : "fileClass",
"parameterType" : "STRING",
"parameterValue" : "TEST"
}, {
"key" : "revision",
"parameterType" : "INTEGER",
"parameterValue" : "2"
} ]
}, {
"productClass" : "PTM_L0",
"filterConditions" : [ {
"key" : "fileClass",
"parameterType" : "STRING",
"parameterValue" : "OPER"
}, {
"key" : "revision",
"parameterType" : "INTEGER",
"parameterValue" : "1"
} ]
} ],
Like the Input Filter these parameters are grouped by product classes. Each parameter of a class is added to the created product of this product class.
"classOutputParameters" : [ {
"productClass" : "PTM_L1B_P1",
"outputParameters" : [ {
"key" : "copernicusCollection",
"parameterType" : "INTEGER",
"parameterValue" : "77"
}, {
"key" : "revision",
"parameterType" : "INTEGER",
"parameterValue" : "2"
} ]
} ],
These parameters are added to all created products.
"outputParameters" : [ {
"key" : "copernicusCollection",
"parameterType" : "INTEGER",
"parameterValue" : "77"
}, {
"key" : "revision",
"parameterType" : "INTEGER",
"parameterValue" : "99"
} ],
The dynamic processing parameters are forwarded to the processor via JOF (Job Order File) to control the processing.
"dynamicProcessingParameters" : [ {
"key" : "debug",
"parameterType" : "BOOLEAN",
"parameterValue" : "true"
} ],