Webinar “Work Management Service” materials and answers
I would like to thank everyone for attending my webinar “Work Management Service – Using SharePoint as a consolidated task platform across the company”. I am really pleased by such a large number of...
View ArticleWork Management service in SharePoint 2013 (1): a short overview for developers
We all know the dilemma of having our tasks scattered all over the place: some are in Exchange (Outlook), some are in SharePoint tasks lists, and some are in Project Server. Taking care of all those...
View ArticleWork Management service in SharePoint 2013 (2): Providers and refreshes
Under the hood, the whole system is based on the model of “Task providers”. Task providers are systems from which the WMA can aggregate tasks: At the moment, three tasks providers are supported:...
View ArticleWork Management service in SharePoint 2013 (3): Locations
Providers look in so called “Locations” to get the updates for existing tasks, and to discover new tasks. Locations are different and specific for each provider. For SharePoint 2013 as task provider,...
View ArticleWork Management service in SharePoint 2013 (4): What is in it for developers?
Even if there isn’t much developer documentation out there, WMA has one of the best and cleanest APIs in the SharePoint world, with equally good SSOM and CSOM implementations. Now, this is something...
View ArticleWork Management service in SharePoint 2013 (5): Querying Tasks
When you have a session manager object, you can retrieve all the tasks for a user, or filter the tasks to get only those that you need. There are seven possible filters that you can apply when querying...
View ArticleWork Management service in SharePoint 2013 (6): Creating a task
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...
View ArticleWork Management service in SharePoint 2013 (7): More task operations
Once we have a task, there are numerous task related methods within the Session object. We can, for example, pin and unpin tasks to the timeline (equals to the “important” tasks in Outlook, or high...
View ArticleWork Management service in SharePoint 2013 (8): Working with provider refreshes
As mentioned earlier, a provider refresh is a process of retrieving and caching tasks for a user. It is done on demand, with no background job processing the tasks. Refresh will be started at that...
View ArticleWork Management service in SharePoint 2013 (9): And on the client side?
I have mentioned already in the previous articles of this series, that the CSOM side have been implemented with almost the same methods as the server side. To finish this blog post with a goodie, I...
View ArticleClik here to view.
Webinar “Work Management Service” materials and answers
I would like to thank everyone for attending my webinar “Work Management Service – Using SharePoint as a consolidated task platform across the company”. I am really pleased by such a large number of...
View ArticleClik here to view.
Work Management service in SharePoint 2013 (1): a short overview for developers
We all know the dilemma of having our tasks scattered all over the place: some are in Exchange (Outlook), some are in SharePoint tasks lists, and some are in Project Server. Taking care of all those...
View ArticleClik here to view.
Work Management service in SharePoint 2013 (2): Providers and refreshes
Under the hood, the whole system is based on the model of “Task providers”. Task providers are systems from which the WMA can aggregate tasks: At the moment, three tasks providers are supported:...
View ArticleWork Management service in SharePoint 2013 (3): Locations
Providers look in so called “Locations” to get the updates for existing tasks, and to discover new tasks. Locations are different and specific for each provider. For SharePoint 2013 as task provider,...
View ArticleWork Management service in SharePoint 2013 (4): What is in it for developers?
Even if there isn’t much developer documentation out there, WMA has one of the best and cleanest APIs in the SharePoint world, with equally good SSOM and CSOM implementations. Now, this is something...
View ArticleWork Management service in SharePoint 2013 (5): Querying Tasks
When you have a session manager object, you can retrieve all the tasks for a user, or filter the tasks to get only those that you need. There are seven possible filters that you can apply when querying...
View ArticleWork Management service in SharePoint 2013 (6): Creating a task
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...
View ArticleWork Management service in SharePoint 2013 (7): More task operations
Once we have a task, there are numerous task related methods within the Session object. We can, for example, pin and unpin tasks to the timeline (equals to the “important” tasks in Outlook, or high...
View ArticleClik here to view.
Work Management service in SharePoint 2013 (8): Working with provider refreshes
As mentioned earlier, a provider refresh is a process of retrieving and caching tasks for a user. It is done on demand, with no background job processing the tasks. Refresh will be started at that...
View ArticleWork Management service in SharePoint 2013 (9): And on the client side?
I have mentioned already in the previous articles of this series, that the CSOM side have been implemented with almost the same methods as the server side. To finish this blog post with a goodie, I...
View Article
