Invoke Service Action¶
Definition¶
<invoke_service_action name="alpha">
Calls for an action to be performed by a service.
| Attribute | Type | Description |
|---|---|---|
| name | string | Required. The name of the Action as defined in the Service Interface. |
| preconfirm | string | Optional. Can be set to "assertive" or "interrogative". If defined, causes system to ask for a confirmation from the user before performing the action. |
| postconfirm | boolean | Optional. If set to `True', causes the system to report on the status of the action |
| downdate_plan | boolean | Optional (deprecated). No longer triggers implicit downdating; use explicit downdate conditions instead. |
Parents¶
Children¶
None.
Behaviour¶
An
If defined, the `preconfirm' attribute causes system to give the user the opportunity to confirm (or abort) an action before it is performed. Can be set to "assertive" (e.g., "I will call John.") or "interrogative" (e.g. "Do you want to call John?"), depending on whether the preconfirmation should take the form of an assertion (which the user can respond, but if they do not, the system will go ahead and perform the action) or a question (requiring an answer from the user). The preconfirmation wording can include parameters of the action.
If set to True', thepostconfirm' attribute causes the system to report on the status of the action after calling on the device to carry out the action.
The downdate_plan attribute is deprecated and does not trigger implicit downdating. If a service action should end a plan, add an explicit <downdate_condition>, for example one that checks for a <service_action_terminated> proposition.
Examples¶
Invoke service action entry for calling a person, first confirming that the parameters are correct, and reporting again when the call has been made:¶
<invoke_service_action name="Call" preconfirm="interrogative" postconfirm="true"/>