WORK MANAGEMENT SERVICE Using SharePoint 2013 as consolidated tasks platform across the company ADIS JUGO 1/13/2014 1 300
1/13/2014 2
Why It is 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 1/13/2014 3
Work Management Service Application New in SharePoint 2013 Provides functionality to aggregate tasks into central place Tasks are accessible through the personal site 1/13/2014 4
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
Tasks Aggregation Architecture
Features All tasks can be managed from one location (My Sites) Displayed on a dynamic time line can add tasks to the time line from the same screen. Sync to Outlook (with Exchange) Categorized/grouped by project sites or locations. Ability to mark tasks as important. Search your tasks.
WMA Prerequisites - Products Server products Cloud services SharePoint Server 2013 Standard or Enterprise SharePoint Online Plan P, Plan 1, or Plan 2 Project Server (for Project Server tasks) Project Online Project Portfolio Management (for Project Server tasks) Exchange Server 2013 Exchange Online Plan E*
Prerequisites My Tasks To aggregate Tasks the MySite Tasks Newsfeed requires: Work Management Service Application (WMA) User Profile Service Application SharePoint MySites Search Service Application Exchange 2013*
TASK AGGREGATION IN SP 2013 DEMO 1 1/13/2014 10
Configuration Steps 1. Setup the Search Service Application 2. Setup My Site Host 3. Setup the User Profile Service Application 4. Setup the Work Management Service Application (WMA) 5. Create the Project Server Service Application (optional) 6. Create sites in SharePoint and Project Server 7. Assign Tasks 8. Run a Search Crawl!
Special Considerations Tasks Appearing for the User A user s tasks won t be visible until the following are complete: 1. User creates their MySite 2. They refresh their Tasks 3. A Search Crawl has happened
Service application detailed architecture and process
Developing for WMA Service 1/13/2014 14
SSOM/CSOM 1/13/2014 15
Microsoft.Office.Server.WorkManagement KeywordFilter FieldFilter CustomAttributeFilter LastModifiedDateRangeFilter LocationFilter PinnedFilter UserSettingsManager UserOrderedSessionManager UserOrderedSession LocationOrientedUserOrderedSession TaskQuery Task Location RefreshResult 1/13/2014 16
TAMPERING WITH THE TASKS THROUGH SERVER OBJECT MODEL DEMO 2 1/13/2014 17
Special Considerations Refreshes 1. User Refresh from MySites Task 2. Provider Aggregator Refresh Triggers the WMA Refresh of MySites Task Checks the Site Collection Hints Listening for the new SharePoint events (hints) to be alerted when a new task is assigned to the user 3. Provider Query Refresh Checks the Search Index for New/Updated Task Locations and New/Updated User Assignments Tasks from legacy SharePoint task lists will not trigger hints
Special Considerations Relationship to Search Search Crawler locates tasks lists and loads them into the Search Index for Querying by the WMA Provider Once a task list is found to contain at least one task assigned to the user, any new task on this task list will be found during the next WMA Aggregator ( Provider ) refresh, since the task list location is in memory already Same for users If a user task is assigned but that user did not already have permission to the task list, the task won t show up until the next Search Crawl
Special Considerations General Cross farm 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.
Special Considerations WMA Admin Settings Cannot be set in Central Admin! Must be set with PowerShell with Set-SPWorkManagementServiceApplication
WMA Properties Property Default Value Description minimumtimebetweenproviderrefreshes minimumtimebetweenproviderrefreshes 0:05:00 MinimumTimeBetweenSearchQueries MinimumTimeBetweenSearchQueries 3:00: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. 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.
Supported Task Types Task Types 171 / Tasks from SP 2013 Feature ID 00bfea71-a83e-497e-9ba0-7a5c597d0107 107 / Tasks from SP 2010 Feature ID f9ce21f8-f437-4f7e-8bc6-946378c850f0
Working with refreshes DEMO3
Thus spoke Microsoft Implementation is based on provider model, so that additional systems maybe integrated to same architecture in future
no! <NotSupported /> 1/13/2014 26
Tampering with the Provider Model (18+) DEMO 4
Call for action! Consider work management needs Consider possible modifications and use cases Consider needed task providers
adis.jugo.ba @adisjugo 1/13/2014 29