Uploaded byAdis Jugo
SharePoint Conference Munich 2014: Work Management Service
The document discusses the Work Management Service Application introduced in SharePoint 2013, which allows for task aggregation from various sources like Exchange and Project Server into a centralized location. Key features include a unified tasks timeline, synchronization with Outlook, and the ability to categorize and search tasks. It also highlights prerequisites, limitations such as cross-farm aggregation not being supported, and the development model around this service.
More Related Content
Similar to SharePoint Conference Munich 2014: Work Management Service
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
SharePoint Conference Munich 2014: Work Management Service
- 1. Work Management Service Task Aggregation Platform Adis Jugo deroso Solutions GmbH Goldpartner: Veranstalter:
- 2. Who the…? •Born in Sarajevo, Bosnia and Herzegovina, 40 years ago • In SP world since 2002, doing nothing else since 2006 • Microsoft MVP for SharePoint Server • Head of Development at deroso Solutions • Blogger, speaker, author adis.jugo.ba Goldpartner: Veranstalter:
- 3. 9/22/2014 3 Goldpartner:Veranstalter:
- 4. Why • Itis challenging for information workers to get a comprehensive view of their tasks, or to have a central point for managing their work • Tasks are stored across applications and systems, and even in case where all tasks are stored within a single system, information can still be scattered 9/22/2014 4 Goldpartner: Veranstalter:
- 5. Work Management ServiceApplication • New in SharePoint 2013 • Provides functionality to aggregate tasks into central place • Tasks are accessible through the personal site (My Tasks) 9/22/2014 5 Goldpartner: Veranstalter:
- 6. Work Management Service Application • Tasks can be aggregated from Exchange, Project Server and SharePoint • Based on 'Provider model' so that other systems can be eventually integrated in the future • Tasks are cached to a users personal site • Work Management Service is exposed as part of each users My Site / Newsfeed experience Goldpartner: Veranstalter:
- 7. High level picture Goldpartner: Veranstalter:
- 8. Features • Tasksmanaged from one location (My Tasks in personal page) • Unified tasks timeline (view, add, close tasks) • Sync to Outlook (Exchange) • Categorized/grouped by “locations” • “Pinning” tasks (marking tasks as important) • Searching tasks Goldpartner: Veranstalter:
- 9. Prerequisites – WorkManagement Service Application (WMA) – User Profile Service Application • Import from AD – Search Service Application • necessary for SharePoint 2013 tasks – Exchange 2013* – Project Service Application * – Personal/Newsfeed site (MySites) Goldpartner: Veranstalter:
- 10. TASK AGGREGATION INSP 2013 DEMO 1 Goldpartner: Veranstalter:
- 11. Under the hood Goldpartner: Veranstalter:
- 12. Service application highlevel architecture Goldpartner: Veranstalter:
- 13. SharePoint 2013: SupportedTask Types • Task Types – 171 / New tasks from SP 2013 (“TasksWithTimelineAndHistory”) – 107 / Tasks from SP 2010 (Upgraded Lists) – 150 / GanttTasks (Upgraded Lists) • Any Tasks from any list that support Task content type – Task content type must be set as a default content type Goldpartner: Veranstalter:
- 14. Aggregator for SP2013 as a Task Provider Get from cached locations Look at the hint store Search for tasks (if search > 3h ago) Update cached locations Provider refresh minimum time between provider refreshes: 5 min Refreshing or accessing MyTasks page triggers aggregator code Goldpartner: Veranstalter:
- 15. WMA Properties PropertyDefault Value Description minimumTimeBetweenProviderRefreshes minimumTimeBetweenProviderRefreshes 0:05:00 This value specifies the minimum amount of time between refreshes for a provider for a given user. There cannot be a refresh of data if this value is not met, all refresh operations will be null before that. minimumTimeBetweenSearchQueries minimumTimeBetweenSearchQueries 3:00:00 This value specifies the minimum amount of time between calls to search for a given user. This is used to discover new providers not yet known to have tasks for this user. Goldpartner: Veranstalter:
- 16. WMA Admin Settings • Cannot be set in GUI • Must be set with PowerShell with – Set-SPWorkManagementServiceApplication Goldpartner: Veranstalter:
- 17. Relationship to Search • Search Crawler locates tasks lists and loads them into the cached locations for Querying by the WMA Provider • When a task list is added to the cached locations, new tasks from this task list will be found during the next Provider refresh • Most of the times, even new tasks from the list that are not cached will show up in MyTasks – Hints (rely on Event Receivers on Task lists) – Not triggered if user has no permissions on that list – Legacy SharePoint lists will not trigger receiver code (will not end up in hints) – Generally not guaranteed Goldpartner: Veranstalter:
- 18. Limitations • Crossfarm aggregation is not supported. – The My Tasks page will not report and aggregate tasks from another farm from the same domain or from a different domain, regardless of the existing trust between the domains and farms. Goldpartner: Veranstalter:
- 19. Development model Goldpartner:Veranstalter:
- 20. Developing for WMAService 9/22/2014 20 Goldpartner: Veranstalter:
- 21. SSOM/CSOM 9/22/2014 21 Goldpartner: Veranstalter:
- 22. Microsoft.Office.Server.WorkManagement UserSettingsManager UserOrderedSessionManager UserOrderedSession LocationOrientedUserOrderedSession TaskQuery Task Location RefreshResult KeywordFilter FieldFilter CustomAttributeFilter LastModifiedDateRangeFilter LocationFilter PinnedFilter 9/22/2014 22 Goldpartner: Veranstalter:
- 23. TAMPERING WITH THETASKS THROUGH SERVER OBJECT MODEL DEMO 2 Goldpartner: Veranstalter:
- 24. Working with refreshes DEMO3 Goldpartner: Veranstalter:
- 25. Client Object Model • CSOM: Full • REST: None Goldpartner: Veranstalter:
- 26. Building a metroapp DEMO4 Goldpartner: Veranstalter:
- 27. Thus spoke Microsoft… Implementation is based on provider model, so that additional systems maybe integrated to same architecture in future Goldpartner: Veranstalter:
- 28. …no! <NotSupported /> 9/22/2014 28 Goldpartner: Veranstalter:
- 29. Tampering with theProvider Model (18+) DEMO 5 Goldpartner: Veranstalter:
- 30. Further reading: Microsoftwhite paper My Tasks Aggregation in SharePoint Server and Exchange Task Integration http://www.microsoft.com/en-us/ download/details.aspx?id=38799 Goldpartner: Veranstalter:
- 31.
- 32. Ich freue michauf Ihr Feedback! Vielen Dank! Adis Jugo http://www.adisjugo.com @adisjugo Goldpartner: Veranstalter: