The Get Presence task gets a user's current presence status on behalf of a watcher. This request is based on user's ACL rule, and both watcher and presentity should be a configured presence user. This task requires psconnector snap-in.
- This API is authorized if psconnector service attribute ‘force application authorization rule’ is disabled, or if the watcher has this calling app in its service profile. If authorization fails, an UnAuthorizedException is thrown.
This is an asynchronous task.
Both watcher and presentity URIs are mandatory. They have to be a presence services user, and the parameter should be the user's SMGR login name.
All mandatory fields should either be mapped using the Input Mapping window or entered in the Properties window for validation to succeed.
presentityUri (mandatory) – SMGR login name defined for the presentity.
watcherUri (mandatory) – SMGR login name defined for the watcher.
presentityUri – presentity.
personState – current status of presentity. It can be one of the following: "available", "busy", "away", "unavailable", "on-the-phone", "offline", "vacation", "unknown".
status – request status code. It can be one of the following: 200 - request was successful; 404 - invalid presentity or watcher; 403 - request failed due to ACL rule; 500 - other error, please check logs.
reason – detailed reason in case get presence request had failed. This field is empty if request was successful.
Not applicable.
Presence Services must be configured and running.
Presence Services Connector must be configured and running.
Not applicable.
Get the presence state of a user on behalf of a watcher, use the presence state to decide next action in chain.