Difference between revisions of "Actions"
From AMTech WikiDocs
(→Send command) |
(→Send command) |
||
| Line 25: | Line 25: | ||
== Send command == | == Send command == | ||
| − | * This action can be configured to send a command. | + | * This action can be configured to send a command. |
* Command objects are no different from observation objects. In fact, you will be asked to provide an observation type as if you were sending a regular observation. | * Command objects are no different from observation objects. In fact, you will be asked to provide an observation type as if you were sending a regular observation. | ||
| − | + | Same as asynchronous consumption of observations. The command received, which is also an observation instance, will have the target type and target uri into the targetthings property. | |
== Send notification == | == Send notification == | ||
Revision as of 20:19, 22 April 2016
Contents
Create thing
- This action is configured to create a new thing.
- The name property will be used to generate a uniq ID for this thing.
- Things aren't immediately created. The creation action is queued as a promise. See CRUD promises.
Update thing
- This is only available in a for-each reasoner.
- This action is configured to update an existing thing: the thing that is currently being visited by the for-each reasoner.
- Things aren't immediately updated. The update action is queued as a promise. See CRUD promises.
- In the configuration context (and also at execution time) the object referencing "the thing" doesn't change after the action update. It means that any further action using "the current thing" object will work with the same object that the observer retrieved from the DAP.
Delete thing
- This action is only available in a for-each reasoner.
- This action is configured to delete the thing that is currently being visited by the for-each reasoner.
- The thing is not immediately delete. The deletion action is queued as a promise instead. See CRUD promises.
Send observation
- This action can be configured to send an observation to the Sensor's network.
- Most mandatory data must be configured in this action. See Observations and observation types in the Sensor's network page.
Send command
- This action can be configured to send a command.
- Command objects are no different from observation objects. In fact, you will be asked to provide an observation type as if you were sending a regular observation.
Same as asynchronous consumption of observations. The command received, which is also an observation instance, will have the target type and target uri into the targetthings property.
Send notification
- This action can be configured to send a notification. Notifications are configured as global objects under the activity's scope.
- You will need to provide string bindings for all the configured placeholders.
- You will decide if the security for the execution of this action will be taken from the observation that triggered this reasoner or from thing being visited, in case of for-each reasoners. Based on that the notification will be either be received by the users in the tenant of observation or by the users in the tenant of the thing.
Send scheduled observation
- Very similar to send observations action.
- You will be required to specify the following:
- An identifier for this scheduled observation.
- Start date: a starting point in the future where the send observation action will actually be executed.
- Occurrence: a number of repetitions: 0 for unlimmited repetitions
- A frequency of repetitions specified as a combination of years, months, days, hours, minutes, seconds. For instance, 3 days, 4 hours, 30 minutes will specify that the observation will be sent each time a period of 3 days 4 hours and 30 minutes is elapsed.
