Skip to content

Latest commit

 

History

History
59 lines (40 loc) · 2.41 KB

sample-specify-queue-item-work-early-bound.md

File metadata and controls

59 lines (40 loc) · 2.41 KB
Raw
title description ms.custom ms.date ms.reviewer ms.suite ms.tgt_pltfrm ms.topic applies_to helpviewer_keywords ms.assetid caps.latest.revision author ms.author search.audienceType
Sample: Specify a queue item to work on (early bound) (Developer Guide for Dynamics 365 Customer Engagement) | MicrosoftDocs
The sample code demonstrates how to use PickFromQueueRequest to specify a user who will work on a queue item.
10/31/2017
pehecke
sample
Dynamics 365 Customer Engagement (on-premises)
sample for specifying queue items for users to work on (early bound)
specifying queue items for users to work on (early bound), sample
be171519-f8d0-43e6-b5a7-770802da47db
18
JimDaly
nabuthuk
developer

Sample: Specify a queue item to work on (early bound)

This sample shows how to use PickFromQueueRequest to specify a user who will work on a queue item. You can download the sample from here.

[!includecc-sample-note]

How to run this sample

[!includecc-how-to-run-samples]

What this sample does

The PickFromQueueRequest message is intended to be used in a scenario where it contains data that is needed to assign a queue item to a user and optionally remove the queue item from the queue.

How this sample works

In order to simulate the scenario described in What this sample does, the sample will do the following:

Setup

  1. Checks for the current version of the org.
  2. The Queue method creates a private queue instance and set its property values.
  3. The QueueItem method creates a new instance of queueitem and initialize its properties.

Demonstrate

  1. The WhoAmIRequest method retrieves the current user information.
  2. The PickFromQueueRequest method creates an instance of an existing queueitem in order to specify the user that will be working on it.

Clean up

Display an option to delete the sample data that is created in Setup. The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.

[!INCLUDEfooter-include]