Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":2190,"date":"2014-06-29T12:03:14","date_gmt":"2014-06-29T10:03:14","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=2190"},"modified":"2014-06-29T12:03:14","modified_gmt":"2014-06-29T10:03:14","slug":"work-management-service-in-sharepoint-2013-6-creating-a-task","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2014\/06\/29\/work-management-service-in-sharepoint-2013-6-creating-a-task\/","title":{"rendered":"Work Management service in SharePoint 2013 (6): Creating a task"},"content":{"rendered":"

To create a task, we will use the session object created above. When we create a task through Work Management Application, it is initially always a personal task, stored only in the task cache list in user\u2019s My Site. Even if we are able to set a task location when creating a task, that task is still only a personal task.<\/p>\n

There are two overloads of the CreateTask() method, one with, and one without location. Setting the location to null, we can create the task without location even with the location-aware overload:<\/p>\n

TaskWriteResult taskWriteResult = uos.CreateTask(\"My task name\", \"My task description\", \"03\/24\/2014\", \"03\/27\/2014\", isCompleted, isPinned, \"\", locationId);<\/pre>\nTask myNewTask = taskWriteResult.Result;<\/pre>\nWith those two lines, we create a task with a name, description, start date (localized string), due date (localized string), booleans that define if the task is completed and pinned, task edit link (this would be interesting if we would have our own task providers), and the location id (nullable integer).<\/p>\n
As mentioned above, this task is still a personal task, even if there is a location info associated with it.<\/p>\n
To \u201cpromote\u201d this task to its location (basically, to push it to the associated SharePoint list, Project etc), we will use one of the two overloads of the Promote method. If location information has already been associated with the task, this will suffice:<\/p>\n
taskWriteResult = uos.PromotePersonalTaskToProviderTask(myNewTask.Id);<\/pre>\nIf there was no location information, we can set it during the task promotion:<\/p>\n
taskWriteResult = uos.PromotePersonalTaskToProviderTaskInLocation(myNewTask.Id, locationId);<\/pre>\nNow, this task can be found in its new location as well, and the location information cannot be changed anymore.<\/p>\n
\n\t\t\t  \n\t\t\t  <\/div><\/div>\n\t\t