Task Properties
Property | UI Field Name | Description | Specifications | Required |
---|---|---|---|---|
| Universal Event Template | Universal Event Template name. XML <eventTemplate label="Test Event A">test_event_a</eventTemplate> "eventTemplate": { "label": "Test Event A", "value": "test_event_a" } | The | Y |
| Event Type | Type of Universal Event to monitor. | Valid values: one of the following (not case sensitive):
| Y |
| Expiration Action | If | Valid values:
Default is Failed (1). | N |
| n/a | Universal Event criteria to monitor. | N | |
| From | If Together with If the criteria is satisfied already, the Universal Monitor task goes immediately to SUCCESS status. Otherwise, the Controller continues monitoring until the criteria is met or until the | Format: [+/-]hh:mm. Default is 00:00. | N |
| To | If Together with | Format: [+/-]hh:mm. | N |
| Universal Task Publisher | Universal Extension-based Universal Task that will be:
| N | |
| Universal Template | Universal Template name. | Y | |
| Universal Template Event Template | Universal Template Event Template name. XML <templateEventTemplate label="Test Event B">test_event_b</templateEventTemplate> "templateEventTemplate": { "label": "Test Event B", "value": "test_event_b" }
| The | Y |
| Time Scope | For Universal Monitor tasks not associated with a trigger; Used to create a window during which the Universal Monitor conditions must be met in order for the Universal Monitor to be satisfied. The For example, if you specify -01:00 in | Valid values:
Default is – None – (0). | N |
Filter Properties
Property | UI Field Name | Description | Specifications | Required |
---|---|---|---|---|
| Match All Match Any | Valid values:
Default is And (1). | N | |
| Criteria list. An element in the list is of type criterion or criteria. | The following example represent a criteria list consisted of two elements:
Note In JSON, the two elements are wrapped in the “criteria“:[] property. However, in XML, there is no additional <criteria></criteria> tag to wrap the two elements. XML <criterion> <name>int</name> <operator>EQUALS</operator> <value>5</value> </criterion> <criteria> <criterion> <name>ifield</name> <operator>IS_NULL</operator> </criterion> <criterion> <name>bool</name> <operator>EQUALS</operator> <value>true</value> </criterion> <logicalOperator>And</logicalOperator> </criteria> JSON "criteria": [ { "type": "criterion", "name": "int", "operator": "EQUALS", "value": "5" }, { "type": "criteria", "criteria": [ { "type": "criterion", "name": "ifield", "operator": "IS_NULL" }, { "type": "criterion", "name": "bool", "operator": "EQUALS", "value": "true" } ], "logicalOperator": "And" } ] | N |
Criteria Properties
Property | UI Field Name | Description | Specifications | Required |
---|---|---|---|---|
| For JSON only. Valid values:
Default is criterion. | N | ||
| A single condition composed of name, operator, value(s). For example: “attribute1 EQUALS value1“ where attribute1 is a attribute of the selected Universal Event Template. | XML <criterion> <name>int</name> <operator>EQUALS</operator> <value>value1</value> </criterion> JSON { "type": "criterion", "name": "attribute1", "operator": "EQUALS", "value": "value1" }, | N | |
| Composed of multiple elements and a logical operator And or Or. An element can be a criterion or a inner criteria. | XML <criteria> <criterion> <name>ifield</name> <operator>IS_NULL</operator> </criterion> <criterion> <name>bool</name> <operator>EQUALS</operator> <value>true</value> </criterion> <logicalOperator>And</logicalOperator> </criteria> JSON { "type": "criteria", "criteria": [ { "type": "criterion", "name": "ifield", "operator": "IS_NULL" }, { "type": "criterion", "name": "bool", "operator": "EQUALS", "value": "true" } ], "logicalOperator": "And" } |
Criterion Properties
Property | UI Field Name | Description | Specifications | Required |
---|---|---|---|---|
| Name of the attribute | Input data will be converted to lowercase. | Y | |
| Valid values (case insensitive) :
| Y | ||
| Y - if operator is either:
| |||
| Y - if operator is either:
| |||
| start should be less than or equal to end. XML <start> <value>5</value> </start> JSON "start": { "value": "5" } | Y - if operator is:
| ||
| start should be less than or equal to end. XML <end> <value>6</value> </end> JSON "end": { "value": "6" } | Y - if operator is:
|