Content element
Contains the items that have to be executed consecutively when the group is executed.
Parent
Attributes
| Name | Type | Required | Description |
|---|---|---|---|
| multipleGet | EnumTrueFalse | If "true", all parameters will be read in one SNMP Get operation. |
Children
| Name | Occurrences | Description |
|---|---|---|
| choice | ||
| Action | [0, *] | Specifies the ID of an action to include in the group. |
| Pair | [0, *] | Specifies the ID of a command/response pair to be included in the |
| Param | [0, *] | Specifies the ID of a parameter to be included in the group. |
| Session | [0, *] | Specifies the ID of an HTTP session to be included in the group. |
| Trigger | [0, *] | Specifies the ID of a trigger to be included in the group. |
Remarks
The content of a group has to consist of items the same type.
- action items only
- pair items only
- parameter items only
- session items only
- trigger items only
Tip
Do not include more than 10 parameters, pairs, actions or triggers in one Protocol.Groups.Group.Content tag.
Important
Depending on the content type, the behavior regarding when the polling request/command is built might differ:
- For serial, see makeCommandByProtocol.
- For HTTP, the requests will be built and buffered when the group is added to the SLProtocol queue. This means that if some request parameters are updated by the time the group gets executed, the sent request will still contain the values from when the group was added to the queue, avoiding race condition issues.