Control Users
Goal: Block and Unblock, Set presence Status of specific users
Complexity: Low
Preconditions:
- LUCS is installed
- API Setup and Preconditions are met
- At least one Service with Users has been defined, Service ID is known
- At least one User must be online (selectable) by the System so the blocking of created external tasks can be tested
Related DTOs:
Usage example steps
Used Functions | Action | Results | |
---|---|---|---|
1 | To find our target users, you may request the list of "isSelectable" users first if not already known. In this example we signed on with one test-user only, so we get details of only that user returned. Important parts to note are:
Return list of selectable users
CODE
| → Code 200 User ID of a selectable user is now known User is not yet blocked | |
2 | POST block user and POST Tasks to test | We now block the user, which changes the following parameters in it's returned DTO:
Return list of selectable users
CODE
Note that the presence state is not affected by this, so the user will not see the block in his messenger. You can use POST Tasks to get a testing task running. If no other user is selectable the task will remain pending. Test Task for Block-Checking
CODE
| Block → Code 200 (Returns changed user DTO parameters) Tasks → Code 200 (Returns TaskID) |
3 | POST unblock user | We now unblock the user to see if the task is immediately distributed as the system has no other alternatives (being online and selectable) Return list of selectable users
CODE
Note: The the block is removed = "IsBlockedByLuwareApi": false. However the user's presence is still unaffected = "online" , but now ""IsSelectable": false" is set. This is because the user immediately has received the pending task and chose to accept, making him unavailable for further task distribution selects. | Unblock → Code 200 (Returns changed user DTO parameters) |
4 | POST setpresence | Since the presence of the user remains unaffected by external task distribution (online), it could be preferable to set a user's presence to DND automatically upon accepting to handle a task. Via the API POST setpresence command you easily set the user to "DoNotDisturb" remotely. In the example below, the Client configuration combined with Agent Assistant makes your Agents automatically aware that they need to provide a not-ready reason (NRR) during the task handling. It also informs the Agent their task triggered automation in Skype for Business, which you might control individually based on a external tasks severity. | → 200 (No body) |
UCID | UC LUCS API 002 |