Easy Design Structure • to find information • to find my personal work areas • to find information on Sites and tasks • to find information about the organisation • to reach end users with corporate information • to find social features for personal interaction • must follow the brand guidelines • intuitive • on page editing • an integrated working tool • old intranet shall be migrated into new nodes, approx. 6000 pages • improved prestanda • Intranet pages, Sites and My Site shall have aligned design and the feeling of being “one system” European SharePoint Community Awards 2014 Award submission: Most Innovative Cloud Solution Title of Submission: Volvo Car Group (Volvo Cars) Intranet 3.0 Description of the SharePoint Challenge The Intranet 3.0 should be built on the SharePoint 2013 Office365 dedicated platform with support for: • 30.000 Users • Intranet • 1800 Team Sites for Internal Access • 350 Partner Team Sites with External Access • My Site Move all content and page layouts into a new Intranet Architecture and Upgrade all of the system from SharePoint 2010 to SharePoint 2013. Develop the new Intranet 3.0 using the (CSOM and JSOM) for 95% of its features. The remaining 5% for a framework enabling the JSOM app web parts. -We believe Microsoft will enable this code in the future thus making it possible for a 100% CSOM implementation. Project Objectives: 1. Go back to SharePoint out of the box as much as possible for future maintainability and enable effective support. –There should be minimal need for support personnel to learn what has been customized; everything should be as normal SharePoint out of the box 2. Use CSOM client scripting as much as possible and the new SharePoint API in order to avoid server deployed farm code, also for migration of content into new site architecture. 3. Facelift, to align the 3 (Intranet, Sites, My Site) applications which make up the Intranet with the Volvo Car Group Digital Brand Guidelines 4. Implement Direct Access certificate on all employee laptops so they can access the Intranet from home or on the road 5. Automatic new Site Collection Provisioning through list workflow and Azure web services 6. Implemented own Translation module for Multilanguage articles. 7. Personalized Content by Metadata (reading from each user profile, Language, Location and Organization) 8. Metadata Navigation is used for Volvo Car Group Section which structure is frequently changed 9. Adaptive Video Streaming from Azure Media Services, SharePoint Image Renditions 10. Seamless Integration of Intranet, Sites and My Site. 11. Statistical analytics implementation in order to track the majority of application events for future improvements. 12. Improved Search functionality with vertical Search scopes, Promoted Results and Cross-domain Query Results. Business Requirements
Transcript
Easy
Design
Structure
• to find information
• to find my personal work areas
• to find information on Sites and tasks
• to find information about the organisation
• to reach end users with corporate information
• to find social features for personal interaction
• must follow the brand guidelines
• intuitive
• on page editing
• an integrated working tool
• old intranet shall be migrated into new nodes, approx. 6000 pages
• improved prestanda
• Intranet pages, Sites and My Site shall have aligned design and the feeling of being “one system”
EuropeanSharePointCommunityAwards2014
Award submission: Most Innovative Cloud Solution
Title of Submission: Volvo Car Group (Volvo Cars) Intranet 3.0
Description of the SharePoint Challenge
The Intranet 3.0 should be built on the SharePoint
2013 Office365 dedicated platform with support
for:
• 30.000 Users
• Intranet
• 1800 Team Sites for Internal Access
• 350 Partner Team Sites with External
Access
• My Site
Move all content and page layouts into a new
Intranet Architecture and Upgrade all of the system from
SharePoint 2010 to SharePoint 2013.
Develop the new Intranet 3.0 using the (CSOM and JSOM) for 95% of its features. The remaining 5% for a framework
enabling the JSOM app web parts. -We believe Microsoft will enable this code in the future thus making it possible for a
100% CSOM implementation.
Project Objectives:
1. Go back to SharePoint out of the box as much as possible for future maintainability and enable effective
support. –There should be minimal need for support personnel to learn what has been customized; everything
should be as normal SharePoint out of the box
2. Use CSOM client scripting as much as possible and the new SharePoint API in order to avoid server deployed
farm code, also for migration of content into new site architecture.
3. Facelift, to align the 3 (Intranet, Sites, My Site) applications which make up the Intranet with the Volvo Car Group
Digital Brand Guidelines
4. Implement Direct Access certificate on all employee laptops so they can access the Intranet from home or on the
road
5. Automatic new Site Collection Provisioning through list workflow and Azure web services
6. Implemented own Translation module for Multilanguage articles.
7. Personalized Content by Metadata (reading from each user profile, Language, Location and Organization)
8. Metadata Navigation is used for Volvo Car Group Section which structure is frequently changed
9. Adaptive Video Streaming from Azure Media Services, SharePoint Image Renditions
10. Seamless Integration of Intranet, Sites and My Site.
11. Statistical analytics implementation in order to track the majority of application events for future improvements.
12. Improved Search functionality with vertical Search scopes, Promoted Results and Cross-domain Query Results.
Business Requirements
Evidence to Support the Solution
Start
Figure 1 start page
My Work – Accordion section for all day-to-day work and notifications
Figure 2 My Work, not expanded
Figure 3 My Work –Sites I Follow
expanded
News
Figure 4 news section with the amazing anything slider, content types, search engine
News – news article, multi-language
Figure 5 news article, multi-language
Volvo Car Group
Figure 6 KPI values from a list into a web part, Major links web part for on page edit and drag and drop the order of links.
Knowledge Sharing
Figure 7 top horizontal web part zone, web parts for links and request a site
Drag and drop
Knowledge Sharing – Sites
Figure 8: using the search engine, cross-domain query into a site registry, icon displaying internal or external access
Knowledge Sharing – Tools
Figure 9 tools, find a tool, add it to My tools section as a quick link to an external application
Help –Main section
Figure 10 help main page
Help –Use the Intranet section with streaming videos
Figure 11 showing one adaptive video streaming from Azure Media Services
Branded Team Site
Figure 12 branded Team Site, custom Web part for easy editing of Ownership,
My site
Figure 13 my site, news feed
Developer’s notes and comments:
As the previous versions of our intranet portal was very heavily based on traditional Full Trust Code solutions, the
complex and time-consuming process of deploying updates and bug fixes had been an issue for us ever since the
beginning of project for the first version of the portal built on the Office 365 dedicated platform, over two years ago.
The new improvements to the Client Side Object Model in SharePoint 2013 allowed us to develop version 3.0 of the
intranet almost completely without Full Trust Code. This gives us flexibility and speed when it comes to solution updates
on par with (and in some areas exceeding that of) an on-premise environment.
We only used Full Trust Code for two features in the Intranet project. The first is a server control for referencing
JavaScript files in a cache-safe manner and with the ability to switch between minimized and debug versions of scripts,
making it possible for us to debug and step through any part of the intranet live on our production environment without
affecting other users.
The second feature is a generic JavaScript web part that can be configured to become any number of web parts
depending on which user configurable parameters it is set to display and which scripts it is set to load.
This way, we can develop and deploy new web parts without writing a single line of additional Full Trust Code, which
made this “chameleon” web part the foundation for nearly all other custom features developed for the intranet.
While this switch from traditional server-side code to relying completely on client side code made it necessary for us
developers to rethink our approach to SharePoint development, it also brought an unexpected side effect. By focusing
completely on client-side code running in the browser, it made it more natural for us to develop interactive and
responsive features, which in my opinion is definitely a contributing factor to the level of usability we achieved in this
![[MS-CSOMREST]: SharePoint Client Query OData ProtocolM… · web technologies when the protocol server implements SharePoint Client Query Protocol, [MS-CSOM]. This protocol defines](https://static.documents.pub/doc/80x56/5e9cccfa397fd134be6a9307/ms-csomrest-sharepoint-client-query-odata-protocol-m-web-technologies-when.jpg)
![[MS-CSOM]: SharePoint Client Query Protocol](https://static.documents.pub/doc/80x56/61e95242c271ab70e60098ea/ms-csom-sharepoint-client-query-protocol.jpg)
