Articles2018-09-05T13:04:32.0000000Z/articles/Optimizely WorldAbout XML External Entity vulnerability in EPiServer CMS 5, 6 and 7/articles/Items/about-xml-external-entity-vulnerability-in-episerver-cms-5-6-and-7/2018-09-05T13:04:32.0000000Z<p>The vulnerability was found in the external blog interface of EPiServer CMS versions 5, 6, and 7. The issue was handled for versions 5, 6, and 7, and patches were created for it. The functionality exposing the vulnerability was discontinued after version 7.0.</p>
<p>If you are running EPiServer CMS version 5, 6, or 7, and cannot upgrade to a version higher than 7, you have the following options depending on the scenario:</p>
<ol>
<li>If you do not use the external blog interface functionality, you can simply <strong>remove the endpoint (/util/xmlrpc/Handler.ashx)</strong>.</li>
<li>If you use the functionality and are on <strong>v7.0.x</strong>, there is an <strong>upgrade (Episerver 7 Patch 5)</strong> that contains a fix for this (as well as other bug fixes).</li>
<li>If you use the functionality and are on <strong>v7.0.x </strong> <strong>but cannot to upgrade</strong>, there is a <strong>patch of Episerver.XmlRpc.dll</strong> that can be applied to the application.</li>
<li>If you use the functionality, and are on <strong>older versions (5, 6)</strong>, you apply a <strong>patch of handler.ashx</strong>.</li>
</ol>
<p>Please contact <a title="Episerver Developer Support" href="mailto:support@episerver.com">Episerver Developer Support</a>, to request the patches referred to above.</p>Ektron Spring 2017 Updates/articles/Items/ektron-spring-2017-updates/2017-06-19T21:54:29.0000000Z<p>While many clients are making or considering the <a href="http://www.episerver.com/products/platform/ektron/converge/">move to the Digital Experience Cloud</a>, Episerver consistently delivers updates for the Ektron platform. If you actively log into the <a href="https://portal.ektron.com/">Support Portal</a>, you already knew this. <a href="http://www.episerver.com/products/platform/ektron/protect/">Protecting your investment? We have you covered!</a></p>
<p>After several great conversations with Ektron customers, I thought it would be helpful to explain our Ektron release process regarding updates, releases, and how requests are handled behind the scenes. There is no magic to this and should look familiar to most.</p>
<p>Ektron releases cumulative updates on a continuing basis. Each update typically contains 1-3 items and includes all previous updates for the service pack that it supports. For example, the 9.20 cumulative update .3 includes updates .2 and .1. Cumulative updates are eventually “rolled-up” into a service pack or major release for our spring and fall product launches. Enhancements and bigger changes are released in service packs or major releases because there is a greater amount of regression testing applied to ensure proper validation coverage and reduction in risk for potential update issues.</p>
<p> <img title="ektron release schedule" alt="ektron release schedule" src="/link/e37ae7910d114406a22ec6905db6f2bd.aspx" height="189" width="600" /></p>
<p><b>How do we prioritize and managed these requests, and what goes into each release? </b></p>
<p>Working closely with our services teams, we review requests from them and from customers to address issues and other requests. As we review requests, we may identify some that are more fitting for our major release; they are put into a backlog and prioritized. Some may end up in service packs or major releases like 9.20.</p>
<p>Have a request for something that you need that might help you out with your current Ektron system? Consult with your <a href="http://www.episerver.com/actions/ektron-customer-contact/">account manager</a>.</p>
<p><img title="Ektron release cycle" alt="Ektron release cycle" src="/link/6e67ecdaa36c4e3ca7a38e3e096d0722.aspx" height="223" width="450" /></p>
<p><b>What’s in Ektron 9.20 Service Pack 1?</b></p>
<p>The Episerver Ektron spring 9.20 service pack 1 release includes all the cumulative updates that were created for version 9.20. There also were additions that are worth mentioning:</p>
<ul>
<li><a href="http://www.episerver.com/products/platform/episerver-social/"><b>Episerver Social</b></a> – an option to use <a href="http://www.episerver.com/products/platform/episerver-social/">Episerver Social</a> allows for expanding your marketing solutions using an easy-to-use service for user-generated content.</li>
<li><b>Workarea performance enhancements</b> – updates were made to improve the overall experience for common activities, such as viewing and navigating folders, viewing and editing content, and general navigation of the folder trees and general user interface.</li>
<li><b>Framework and library updates</b> - component frameworks and libraries were updated to the latest available versions. These include: <i>Microsoft System.Web, Microsoft System.Net.Http.Formatting, Newtonsoft.Json, Microsoft Enterprise Library, and the Microsoft Unity Framework.</i></li>
</ul>
<p>Review the <a href="/link/1dcb866695824550b9d5548357b3f219.aspx">Ektron 9.20 Service Pack 1 Release Notes</a> for details.</p>
<p>For information about the Episerver Digital Experience Cloud or your Ektron platform, <a href="http://www.episerver.com/actions/ektron-customer-contact/">consult with your account manager</a>.</p>Episerver releases/articles/Items/episerver-releases/2017-04-04T10:08:14.6700000Z<h1>Episerver releases</h1>
<h2>―Or why you don’t have to ask “When is the next Episerver version coming?”</h2>
<p>Many software companies release new versions of their software once a year, and maybe some smaller bug fix releases in between. Each time they release, they hit the big drum and make a lot of advertising for the new release. Customers have gotten used to this and wait eagerly for the next big release and hope for a bunch of new features. They might even wait with buying the software because they want the latest-latest.</p>
<h2>Weekly releases</h2>
<p>At Episerver, we are taking another approach. In technical mumbo jumbo, it is called <b><i>continuous releases</i></b> (but never mind that, the term itself isn’t important) and that means we are releasing new features and bug fixes as soon as they are done. And tested, of course! This also means that we release almost every week of the year (okay, we may slack a bit around Christmas and New Year but generally, we release e v e r y w e e k!).</p>
<p>The main idea is that by releasing smaller upgrades every week, there is less risk of introducing major bugs, and the system is always thoroughly tested. Less work for us, less work for you.</p>
<h3>Advantages for us</h3>
<p>Working this way is a great advantage for us. As the cycle is short between starting with a feature, testing, releasing and getting feedback, we have a good overview of each step in the process, and we can quickly fix issues not working so well. Creating the big bang release every year also has a huge cost, both in effort for the company and in dollars and cents.</p>
<h3>Advantages for you</h3>
<p>It is also a great advantage for you, as users of the Episerver platform. Episerver developers can upgrade whenever they want to but generally, the more often they upgrade, the less hassle it is. And Episerver editors don’t have to wait another year for the next great feature in the user interface.</p>
<h2>Versioning</h2>
<p>Another term we use is <b><i>semantic versioning</i></b>. The term itself is not important, but it is important to understand the concept, and how we think of our releases and how they are named.</p>
<p>When we speak of releases, we tend to use one, two, or three digits, as in Episerver 10, Episerver 10.2, or Episerver 10.4.3.</p>
<p>First of all, we call the single-digit releases (such as 8, 9, and 10) for “a major version”. Major versions are releases that have some breaking changes. And by breaking changes, we mean that a developer may have to change something in their code before they can upgrade. But if you are an editor, there may not be a single change between the previous version and the new major version.</p>
<p>A release with two digits (also called "a minor version"), such as Episerver 10.2, is a release that has some new features. The new features can be either inside the software (what we call CMS Core) or in the user interface (CMS UI). (I’m mentioning just Episerver CMS here, but all parts of the Episerver platform are released and versioned the same way.)</p>
<p>A three-digit release, such as Episerver 10.4.3, is a release which contains only bug fixes. It does not contain any new functionality.</p>
<p style="margin-left: 300px;"><img alt="" src="/link/05ebd8d65fe542e0922fc228d71b1697.aspx" height="209" width="533" /></p>
<p>So between versions 10.1 and 10.4.3, there are new features and bug fixes, but upgrading should be very smooth since there are no breaking changes.</p>
<p>Our releases are also <b><i>cumulative</i></b>, which means that release 10.8 contains all the features and bug fixes that were released in 10.7.9 and 10.5 and all other previous releases.</p>
<p>So, if you are a developer, this means you are most interested in the major releases, as these <i>may</i> give you more work than simply just pressing the Upgrade button. But note the word *may*, your specific site may not be affected by the breaking changes at all.</p>
<p>As an editor, you may be more interested in the minor versions, because that’s where most of the goodies are released. If we take the Episerver 10 release as an example again, the 10 release didn’t include anything fun for the editor at all. But the 10.1 release did, as did the 10.7 release. In release 10.1, you got the first sneak peek of the <a href="http://webhelp.episerver.com/latest/cms-edit/content-approvals.htm">content approvals feature</a>, and in release 10.7, content approvals were implemented for assets such as blocks and media.</p>
<h2>Add-ons</h2>
<p>The Episerver platform is built up by Episerver CMS, Episerver Commerce, and Episerver Find. In addition to that, there are a number of add-ons, which contain functionality not included by default in a standard installation but can be added to enhance the product. Some of them are built by Episerver and some by third-parties. Some of them can be used for free, while others require an additional licence.</p>
<p>When we release a new major version of Episerver CMS, we know people are eager to get it and start working with it. So we prioritize releasing it as soon as it is ready, which means that some add-ons have not been tested against the new CMS version at the release. After a major release of Episerver CMS, we update the add-ons to support the latest CMS version, but this is a process which takes some time. If you are using add-ons, you can check the <a href="/link/be3403ff721f405b99014cf0f33793dc.aspx">Add-ons compatibility</a> page to see which CMS versions support the add-ons you are using.</p>
<h2>Where to find what has been released and when?</h2>
<p>We try to keep you informed of what we have in the pipeline, and the different teams generally blog about major releases before they are released as a heads-up. New features are also released as Beta features while still under development, to give you a chance to try them out and give us feedback. Beta features are tested but should not be used on production sites as they may be changed without prior notification.</p>
<p>When we release each week, we publish what we call “a weekly update” on <a href="/link/6c9478a8761c41d88dfc32e9ef56e714.aspx">Episerver World</a>. The <a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx?page=1">weekly update</a> includes information on what is being released and it also links to a release feed. The weekly update also includes links to relevant updated documentation.</p>
<p>Example of weekly update:</p>
<p><img alt="" src="/link/24212c8e9abb49cda1344d3a552f0260.aspx" height="471" width="637" /></p>
<p>The <a href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">release feed</a> displays all new features and public bug fixes and you can easily use this to sort out information for a specific release:</p>
<p><img alt="" src="/link/bd111999ef614ec5b88562121f78e9ce.aspx" height="467" width="636" /></p>
<p>With the short test and release cycles we have, it just isn’t possible to say when the next major or minor release will be released. We release major versions when we have enough breaking changes to warrant a new major version. Minor versions are released as soon as new features are thoroughly tested. We never release anything unless all tests are green.</p>
<p>The best recommendation we can give you is that you try to be as up-to-date as you can be. The more up-to-date you are, the easier it is to upgrade each time.</p>
<h2>Other useful information</h2>
<p><b>Editor?</b></p>
<p>The weekly update is often full of technical details and aimed at the developers who are responsible for doing the upgrade at customer websites. Four times a year, we summarize all new features that were released since the last time in what we call <a href="/link/91de3b08d0bf43178aed75c54a5dca35.aspx?page=1">feature lists</a>. They are found on <a title="Episerver World" href="/link/6c9478a8761c41d88dfc32e9ef56e714.aspx">Episerver World</a> (our community site) and are intended for editors, or other people interested in new functionality.</p>
<p>You find shortcuts to the weekly updates, release feed and feature lists under Releases and features on the Episerver World start page:</p>
<p><img alt="" src="/link/bf480faf7cd940f991dc9916ed471f2c.aspx" height="430" width="635" /></p>
<p>From <a href="/link/10fe06c8c54c412aaf5564aeb1159de9.aspx">Documentation</a> in the top menu of World, you can find developer documentation but also a link to <a href="http://webhelp.episerver.com/latest/">the Episerver User Guide</a>, which is aimed towards editors and descibes how to work with the Episerver platform.</p>
<p><img alt="" src="/link/9464bf63712c457283c8db3f89fc88bf.aspx" height="365" width="634" /></p>
<p>The user guide isn’t released every week but we try to release it every month, if necessary. There is a section called <a href="http://webhelp.episerver.com/latest/getting-started/whats-new.htm">What’s new</a> which shows the last weekly update that it covers. Many new features are also <a href="http://webhelp.episerver.com/latest/_online-only-topics/videos.htm">demoed in short videos</a>.</p>
<p>If you prefer to rather print the user guide and read on paper, you find PDFs on the <a href="http://webhelp.episerver.com/latest/_online-only-topics/pdfs.htm">User guides for print</a> page.</p>
<p><b>Developer?</b></p>
<p>As you probably already know, <a href="/link/6c9478a8761c41d88dfc32e9ef56e714.aspx">Episerver World</a> is full of information for you. Regarding releases, the most useful information is:</p>
<ul>
<li>The <a href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">release feed</a></li>
<li>The <a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx?page=1">weekly update</a> information</li>
<li><a href="/link/1933ba72787346df9003b7a4c7d1cff8.aspx">Bug list</a></li>
</ul>
<p>Note that if you want to try out features still in Beta, you need to enable these features by defining a EPiBetaUsers role in your system. See <a href="/link/8b4432703e44486ea1af6ddec232a8c5.aspx">Fredrik Tjärnberg’s blog post</a>.</p>
<p><b>System manager? IT boss?</b></p>
<p>If you are more interested in the future than the past, we plan on keeping our roadmap available on World. This is still work-in-progress, but keep your eyes open.</p>Ektron - time to tackle competitive FUD/articles/Items/ektron---time-to-tackle-competitive-fud/2017-02-22T15:59:43.0800000Z<p>Like many of us, toward the end of 2016, I was very excited that the U.S. election would soon be over. What a crazy year it was. Like many, I enjoy a good debate over real data and when both sides are civil. However, I’m not a fan of mudslinging, name calling, and language that lowers the level of the debate.</p>
<p>It’s no secret that we live in a highly competitive world, and last year’s election proves just that, where challenging statements are made to distract us from reality. This seems to be the case in the business world too, where competitors routinely highlight a customer’s “only” options, entice them with unrealistic financial incentives, or occasionally communicate misinformation about their competition.</p>
<p>Whether this approach is coming from a political party, politician, or a competitive organization or their associates, I’m quick to acknowledge that someone is attempting to take advantage of me. In this case, the approach is the continuing fear, uncertainty, and doubt (FUD) directed against my company, Episerver and our product, the Ektron CMS.</p>
<p><b>So, let it be very clear (again) - Episerver has no plans to discontinue the Ektron CMS.</b> There are still many hundreds of Ektron clients using the platform every day who are an important part of the Episerver family, just as there are hundreds of customers using the Episerver CMS platform, which is also an important part of our family. Episerver was clear about this back in January 2015 when Ektron and Episerver merged and laid out a <a href="http://www.episerver.com/cms/ektron/converge/">roadmap for the convergence</a> of the best of both products into the next-generation <a href="http://www.episerver.com/services/cloud-service/">Digital Experience Cloud platform</a>. Customers who have chosen to make the move up to the Digital Experience Cloud, regardless of product heritage, have been fully supported through every step of the process by Episerver and our partners with great success. Episerver continues to offer this support for all customers, just as we continue to support customers who chose to remain on their current investment for now. </p>
<p>While we know that we are genuine with our position (after all, it’s now over two years since we outlined it), and stand behind all customers through their digital experience journeys, we also encourage your own validation with <a href="http://www.episerver.com/customers/">our many customer references</a>, from those that have made the move as well as those that are planning to do so but are <a href="http://www.episerver.com/cms/ektron/protect/">still on the Ektron CMS</a> or older versions of the Episerver CMS platform.</p>
<p>Please <a href="http://www.episerver.com/actions/ektron-customer-contact/">consult with your account manager</a> today who can connect you with many reference accounts who have moved up to the Digital Experience Cloud. If you are still not ready, that’s OK too, because when the time is right, we’re ready for you. Until then, <a href="http://www.episerver.com/cms/ektron/protect/">we have you covered</a>.</p>Ektron Fall Updates/articles/Items/ektron-fall-updates/2016-12-09T17:32:32.0000000Z<p><b><span style="text-decoration: underline;">Ektron Fall 2016 Updates</span></b></p>
<p>Episerver interacts with customers at many stages of their digital marketing journey, and we are very proud to be considered great listeners. Beyond listening, we gain an equal amount of pride delivering solutions to solve problems, which makes this journey together successful!</p>
<p>The Episerver Digital Experience Cloud™ represents the convergence of the Ektron and Episerver product lines, as well as substantial new features and functions previously unavailable with either. While the strongest value for clients is the Episerver Digital Experience Cloud™, we understand there are reasons for continuing to use the Ektron CMS.</p>
<p>As part of the Episerver fall product release, we are excited to announce Ektron 9.20. This release includes useful enhancements, product updates, and platform updates. Ektron 9.20 is available for download and use. </p>
<p><b>Enhancements</b></p>
<p>The Ektron CMS features and enhancements added in version 9.20 include:</p>
<ul>
<li><a href="http://documentation.ektron.com/cms400/v9.20/Reference/Web/EktronReferenceWeb.html#Content/Content.htm?Highlight="Change Auditing"">Change Auditing</a> - Ektron 9.20 now has change auditing functionality to help with your authoring needs where compliance may be important. You can configure content, folders, menus, and taxonomies to protect or log the activities.</li>
<li><a href="http://documentation.ektron.com/cms400/v9.20/Reference/Web/EktronReferenceWeb.html#Content/Content.htm?Highlight="recycle bin"" target="_blank">Recycle-bin</a> - The Recycle-bin like functionality makes use of the change auditing feature. This provides a more visual way for content authors to delete items while maintaining the ability to restore them, preventing accidental deletion or simply as an added safeguard to a workflow.</li>
<li><a href="http://documentation.ektron.com/cms400/EDR/Web/EDR.htm#Strategies/Strategies.htm?Highlight="Wizard to Generate"" target="_blank">Strategies Wizard</a> - You can now easily create Ektron Strategies using a point and click wizard. This new interface helps speed up the creation by presenting a list along with automating some configuration details.</li>
<li><a href="http://documentation.ektron.com/cms400/EDR/Web/EDR.htm#IQueryable Data Sources/IQ data sources.htm">IQueryable Data Sources for Ektron Data Types</a> - For developers that prefer to use Linq queries, an IQueryable interface is now available to interact with most core Ektron data types.</li>
</ul>
<p><b>Product Updates</b></p>
<p>As part of our release scheduling, all updates from Ektron 9.10 were added to this release, including 3 service packs, over 100 cumulative updates, general performance enhancements, and all applicable security patches. Full regression and acceptance testing were performed to ensure proper test coverage for all core functionality with the common configurations. All relevant documentation was also updated to coincide with the product changes. </p>
<p><b>Platform Updates</b></p>
<p>In addition to the mentioned updates, we also extended support for the latest platforms and technologies used with the Ektron CMS. Support for Microsoft SQL Server 2016 and .NET 4.62 are included and validated to ensure compatibility with the latest versions from Microsoft. We are also happy to announce support for the latest Solr Manifold version. As many have been requesting the ability to update to the latest Java Runtime, you can now upgrade to the current version of JRE. Ektron Digital Experience Hub users that have or would like to integrate with Microsoft SharePoint 2016 can now upgrade and use Microsoft SharePoint 2016.</p>
<p>For complete details on what’s included in Ektron 9.20, please visit the <a title="Release notes" href="http://documentation.ektron.com/current/ReleaseNotes/ReleaseNotes_WebHelp.htm#Release9/9.20.htm" target="_blank">release notes</a>.</p>
<p><b>How do I move to the Episerver Digital Experience Cloud?</b></p>
<p>Our next-generation platform features many capabilities that Ektron CMS users enjoyed but re-envisaged in an improved manner. The Digital Experience Cloud brings together the best of the Ektron and Episerver products and is easy to adopt for users on current versions. That said, it is a major new release and, as users of Ektron who moved from version 4 to 6 to 9 know, major version moves need planning and some services. Episerver partners and customers who have made the move will tell you it’s one worth making. To start, it is best to speak with your account manager, as there are many options and resources they can provide, including:</p>
<ul>
<li>Licensing and current Ektron contract information</li>
<li>Upgrade options and product offerings specific to your needs and interests</li>
<li>Episerver Expert Services site assessment - If you are planning a site redesign or have other goals, this may be an ideal time for an assessment, which will reduce the risk of a move</li>
<li>Connecting you to one of our partners willing to help with your implementation and/or re-design needs</li>
</ul>
<p><b>Not quite ready to switch to the Episerver Digital Experience Cloud?</b></p>
<p>Episerver continues to support the Ektron platform with updates to address issues and add enhancements based on customer feedback. Your M&S subscription includes access to the <a href="https://portal.ektron.com/">Episerver Support Portal</a>, which also provides:</p>
<ul>
<li>Episerver developer support</li>
<li>Software downloads and updates for all products, including past versions</li>
<li>Helpful articles and news about the Ektron platform for developers, administrators, and end users</li>
<li>Updates through RSS feeds</li>
<li>Ability to view and submit support tickets</li>
<li>Links to product documentation</li>
<li>Access to Ektron developer resources including:
<ul>
<li>Developer reference library</li>
<li>Community resources (forums, blogs, etc.)</li>
<li>Archived articles and other information</li>
</ul>
</li>
</ul>
<p>If you have suggestions for what you would like to see in future releases of Ektron CMS, <a href="http://www.episerver.com/about-us/our-offices/">please contact us today</a>!</p>
<p> </p>Episerver World updates/articles/Items/world-updates/2016-08-09T15:38:55.0000000Z<p>Anything going on with Episerver World? Our Episerver community site has been around for some time, supporting more than 30,000 developers worldwide working with the Episerver platform. Our web development team continuously work to improve the functionality on World, based on feedback from our community. This article summarizes the latest enhancements, and what is in the backlog for the future.</p>
<h2>About World</h2>
<p>First some background. Like many other websites, World is a complex site which has been added to and built on by multiple developers during the years. It contains both legacy code, as well as newer parts based on recent functionality. A large part of World is the community sections with <a href="/link/bccc323fc15e45259d7a934d1efb5d52.aspx">blogs </a>and <a href="/link/641b1512405b405ca9ffd515aebb08ae.aspx">forum </a>posts. World is also the home of most of the technical <a href="/link/10fe06c8c54c412aaf5564aeb1159de9.aspx">documentation</a> for the Episerver platform, as well as other product-related information.</p>
<p>World is based on the latest Episerver CMS and Find, and is regularly updated to include recent features and fixes as part of the <a href="/link/d0fb45fcfe7e4d2e875444b6ca2cce2b.aspx">continuous release process</a>. This way, World also acts as a "guinea pig" for instant testing of new features, and is an important channel for collecting feedback about the Episerver platform. </p>
<p>The site runs in a load balanced staging environment with multiple web servers both in the stage and in the production environment. World also has integrations with other systems, for example our CRM system, and the issue and project tracking system we use in software development. This integration also provides the source for auto-generated <a href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">release notes</a> for our <a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx">weekly updates</a>, and for the <a href="/link/1933ba72787346df9003b7a4c7d1cff8.aspx">bug list</a> where you can monitor status for bug fixes.</p>
<h3>Working with World</h3>
<p>Our community members create much of the content on World, and some of our <a href="/link/0e4c738fd29f4c0ebe73a97178bc995a.aspx">great EMVPs</a> help us monitor and answer forum questions. We also have quite a few editors working with content. So who are they? Well, you might be surprised to know that most editors are actually Episervers' own developers, working with developer guides. And of course they get to use as much as possible of the functionality they built themselves. Eating your own dog food, that is...</p>
<h4>Projects</h4>
<p>Whenever we have releases with associated documentation changes, we use the <a title="Episerver Projects (Episerver user guide)" href="http://webhelp.episerver.com/latest/cms-edit/projects-feature.htm" target="_blank">Project feature</a>. This lets teams collaborate on content items using notifications, and at release time, instantly publish everything related to the release.</p>
<p class="imageborder"><img alt="" src="/link/834902a223c042979a080ac0a93f66c6.aspx" height="485" width="800" /></p>
<h4>Filtering</h4>
<p>Some of the content filtering you see on World is based on the good old <a title="Episerver categories (Episerver user guide)" href="http://webhelp.episerver.com/latest/cms-admin/editing-categories.htm" target="_blank">built-in category functionality</a> in CMS, but we also use Find to filter out information, like in the filtering of <a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx">release notes</a> by product, packages and versions.</p>
<h4>Search optimization</h4>
<p>We also use the built-in <a title="Search optimization (Episerver user guide)" href="http://webhelp.episerver.com/latest/find/editor-optimize-search.htm" target="_blank">search optimization possibilities</a> in Find, to ensure that certain popular content we know visitors are frequently looking for, is properly displayed when searching using different keywords. </p>
<p><img alt="" src="/link/0c99fdb1e6aa4fa9a79f8aba871477ea.aspx" height="456" width="800" /></p>
<h4><span style="font-size: 16px; line-height: 22px;">Personalization</span></h4>
<p>We also use <a title="Personalization (Episerver user guide)" href="http://webhelp.episerver.com/latest/cms-edit/personalizing-content.htm" target="_blank">personalization </a>on some sections on World to present selected content to a targeted group of visitors, for example specific content that is only for Episerver partners.</p>
<h4>Add-ons</h4>
<p>In addition to add-ons like the <a href="/link/4266adf461a547d79ca5bbbb4db37a49.aspx">Spellchecker</a> and <a href="/link/e1f955cf1a3d45a2882f9f9b32d9cfc3.aspx">Google Analytics for Episerver</a> that we use on the site, we recently added the new <a href="/link/1c63c14e3ef148fb8080b50b09dfeabd.aspx">block-based Episerver Forms</a> add-on, to take advantage of the more advanced possibilities provided with that.</p>
<h2>Recent enhancements</h2>
<ul>
<li>In case you haven't already noticed, the <a href="/link/bccc323fc15e45259d7a934d1efb5d52.aspx">Manage your blogs</a> feature is now publicly available. This lets you conveniently manage your blog posts, if you are blogging directly on World. See <a href="/link/1883e72de62e4947b1e9f57a841b088c.aspx">blogging on World for available blogging options</a>.<br /> </li>
<li>There is now a <em>Recent documentation updates</em> block, which lists new updates to for example system requirements and developer guides. The block can be seen on the <a href="/link/10fe06c8c54c412aaf5564aeb1159de9.aspx">Documentation</a> and Start pages.<br /> </li>
<li>Other recent fixes based on your feedback:
<ul>
<li>Subject titles on new forum postings are now mandatory, so no more empty posts without titles...</li>
<li style="width: 1130px;">All forums are checked by default (may need to click Go to populate the list).</li>
<li style="width: 1130px;">Clearer indication of forum posts with solutions to questions (marked as answered).</li>
<li>Not possible anymore to add a post with a heading that is too long.</li>
<li>Hidden views and ratings for syndicated blogs.</li>
<li>Fixed issue where you cannot edit the first forum post.</li>
<li>Improved search with added product and version numbers for hits.</li>
<li>Improved print output for pages (useful if you're studying for a certification).</li>
<li>Fixed issues with ordered lists in forum posts.</li>
<li>Improved password resetting procedure.</li>
</ul>
</li>
</ul>
<h2>In the backlog</h2>
<p>Work continues to make World even better. We have a list of improvements within areas like search capabilities, content tagging, layout and design, and documentation presentation. Please continue to send us your feedback, to ensure that we are doing the right things!</p>
<h2>Useful hints</h2>
<p>How do I find...</p>
<ul>
<li>Status for a bug - see the <a href="/link/1933ba72787346df9003b7a4c7d1cff8.aspx">bug list under Support (requires login)</a></li>
<li>Most recent <em>features</em> - check the <a href="/link/91de3b08d0bf43178aed75c54a5dca35.aspx">feature list</a>, or go to <em>world.episerver.com/features</em></li>
<li>Most recent <em>updates</em> - see the <a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx">weekly updates</a> list, or go to <em>world.episerver.com/releases</em></li>
<li>Release notes - see <a title="Episerver release notes" href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">release notes</a>, or go to <em>world.episerver.com/releasenotes</em></li>
</ul>Ektron Spring Updates/articles/Items/ektron-june-updates/2016-06-30T21:16:37.0000000Z<h2>Episerver Ektron CMS 9.10 SP3</h2>
<p>As Episerver continues to help clients succeed by providing world class content management, commerce, and digital marketing solutions, the Ektron content management system is still a core platform for many of our customers. While an increasing number of customers are taking advantage of the move to the Episerver Digital Experience Cloud, many clients are still successfully using the Ektron CMS with a strategic plan to make the move at a conservative pace. The good news is that you have options, and Episerver is here to help you achieve the greatest value from your investment.</p>
<p>As part of our spring seasonal launch, Episerver recently introduced a new service pack for Ektron 9.10. This release represents a consolidation of cumulative updates completed since Service Pack 2 (released in the fall of 2015). Ektron 9.10 SP3 includes additional minor fixes as well as customer-requested enhancements and platform and web browser validation, some of which were originally intended for Ektron 9.2.</p>
<ul>
<li><strong>Boosting for Solr</strong> – Boosting is a Solr feature that allows for query time reordering of search results. More information, including a code sample, can be found <a href="https://portal.ektron.com/KB/10746/" target="_blank">here on the Support Portal</a>.</li>
<li><strong>Microsoft Edge browser support</strong> - Updates were made to support use of the Microsoft Edge browser with the Ektron system. Further, validation testing was performed to confirm compatibility for key areas of the user interface.</li>
<li><strong>TLS 1.2 encryption support</strong> – To better assist clients prepare for PCI 3.0 requirements, Episerver added support for TLS 1.2. This will allow the Ektron Windows Services to support the new TLS protocol.</li>
<li><strong>Over 100 issues resolved</strong> from cumulative updates and several updates requested by clients. For details, please see the <a href="http://documentation.ektron.com/current/ReleaseNotes/ReleaseNotes_WebHelp.htm#Release9/9.10SP3.htm" target="_blank">release notes</a>.</li>
</ul>
<h2>Not quite ready to make the switch to the Episerver Digital Experience Cloud?</h2>
<p>Episerver continues to support the Ektron platform with updates to address issues and add enhancements based on customer feedback. Your M&S subscription includes access to the <a href="https://portal.ektron.com/" target="_blank">Episerver Support Portal</a>, which also provides:</p>
<ul>
<li>Access to Episerver developer support</li>
<li>Software downloads and updates for all products, including past versions</li>
<li>Helpful articles and news about the Ektron platform for developers, administrators, and end users</li>
<li>Updates through RSS feeds</li>
<li>Ability to view and submit support tickets</li>
<li>Links to product documentation</li>
<li>Access to Ektron developer resources including:</li>
<ul>
<li>Developer reference library</li>
<li>Community resources (forums, blogs, etc.)</li>
<li>Archived articles and other information</li>
</ul>
</ul>
<h2>Considerations for users on the Ektron CMS</h2>
<ul>
<li>As with most platforms, it is strongly recommended to update to the latest version. Once on the latest version, updates are much easier, and you benefit from all future updates.</li>
<li>On our support portal, subscribe to RSS feeds to get up-to-date information on the latest updates and other helpful information.</li>
<li>Speak with your account manager for any questions or feedback regarding the Ektron product.</li>
<li>Follow key Ektron experts on Twitter to keep up with the latest webinars, articles, and developer updates from the <a href="https://twitter.com/hashtag/ektron" target="_blank">#Ektron</a> community.</li>
<li>From Episerver</li>
<ul>
<li>James Stout (<a href="https://twitter.com/egandalf" target="_blank">@egandalf</a>)</li>
<li>James Donato (<a href="https://twitter.com/james_donato" target="_blank">@james_donato</a>)</li>
</ul>
<li>From the developer community:</li>
<ul>
<li>Daved Artemik (<a href="https://twitter.com/beendaved" target="_blank">@beendaved</a>)</li>
<li>Dustin Sier (<a href="https://twitter.com/miraclemans" target="_blank">@miraclemans</a>)</li>
<li>Brad McDavid (<a href="https://twitter.com/bsm44" target="_blank">@bsm44</a>)</li>
</ul>
</ul>
<h2>How do I move to the Episerver Digital Experience Cloud?</h2>
<p>Our next-generation platform features many of the capabilities that users of the Ektron CMS enjoyed but re-envisaged in an improved manner. The Digital Experience Cloud brought together the best of the Ektron and Episerver products and is fairly easy to adopt for users on current versions. That said, it is a major new release and as users of Ektron who have moved from version 4 to 6 to 9 know, such major version moves need to come with planning and some services – but Episerver partners and customers who have already made that move will tell you it’s one worth making. To start, it is best to speak with your account manager, as there are many options and resources they can provide, including:</p>
<ul>
<li>Licensing and current Ektron contract information</li>
<li>Upgrade options and product offering specific to your needs and interests</li>
<li>Episerver Expert Services site assessment - If planning a site redesign or have other goals, this may be an ideal time and will reduce the risk of a move</li>
<li>Connecting you to one of our many partners willing to help with your implementation and/or re-design needs</li>
</ul>
<h2>What’s coming in the Ektron 9.20 release?</h2>
<p>Ektron 9.2 has been planned for some time but, while we continue to work on the final scope, we instead released enhancements, fixes and platform support sooner (like in 9.10 SP3). Stay tuned! We will share more information this summer and provide insight into some neat things on the way for Ektron CMS 9.2. However, there’s still time. If you have suggestions for what you would like to see in 9.20 then <a href="http://www.episerver.com/about-us/our-offices/" target="_blank">please contact us today</a>!</p>Continuous deployment of Episerver solutions/articles/Items/continuous-deployment-of-episerver-solutions/2016-06-15T13:58:22.0000000Z<p><a id="TOP"></a>This article provides an example of how to manage continuous deployment for Episerver solutions. In this scenario we are using <a title="Octopus Deploy" href="https://octopus.com/" target="_blank">Octopus Deploy</a>, to deploy code changes to the Integration environment in <a href="/link/5d17930c8cda4653b6d50a78c589a51e.aspx">Episerver Digital Experience Cloud (DXC) Service</a>, the cloud-based service offer from Episerver using Microsoft cloud technology.</p>
<h2>Continuous deployment with Octopus Deploy</h2>
<p>You can use <a href="/link/53582b4023114b0a94b2bdf423b2cc23.aspx">any deployment tool that supports Azure Resource Manager (ARM)</a>, for continuous deployment. In this scenario we use Octopus Deploy, describing the steps needed to set up and execute continuous deployment of code changes.</p>
<h3>Prerequisites</h3>
<ul>
<li>An existing website running in the <a href="/link/96ba09b044d04d1bab059afb1c8dcfac.aspx">Integration environment</a>, with a URL to which you will publish your code changes.</li>
<li>A deploy server running Octopus Deploy.</li>
<li>Information from Episerver required for publishing in DXC Service:
<ul>
<li>Client application ID</li>
<li>Password key</li>
<li>Subscription ID</li>
<li>Tenant ID</li>
</ul>
</li>
</ul>
<h3>Procedure overview</h3>
<p>This scenario assumes a <strong>first-time setup</strong> <strong>and deployment</strong> of code changes for a customer project to an Octopus server and the Integration environment. There are different options for configuring your Octopus server, depending on how you prefer to manage continuous deployments. In the steps below, we will configure Octopus to automatically create a release and deploy to the DXC Integration environment, each time the project is built.</p>
<ul>
<li><a href="#STEP1">STEP 1: Creating a project account</a> - done for each new customer project.</li>
<li><a href="#STEP2">STEP 2: Configuring Octopus</a> - done once if you use the same deployment process.</li>
<li><a href="#STEP3">STEP 3: Configuring Visual Studio</a> - done for each new customer project.</li>
<li><a href="#STEP4">STEP 4: Setting up the deployment process</a> - done once if you use the same process. </li>
</ul>
<h2>Setting up continuous deployment</h2>
<h3><a id="STEP1"></a>STEP 1. Create a project account</h3>
<ol>
<li>In <strong>Octopus</strong>, go to <strong>Environments</strong> <strong>></strong> <strong>Accounts</strong>, and create a Service Principal account for the project.</li>
<li>Add a project name and description, and the <strong>Client\Application ID</strong>, <strong>Subscription ID</strong>, <strong>Tenant ID</strong>, and <strong>Password\Key</strong> values received from Episerver.<br /> <br /><img alt="" src="/link/ecd39bf9b9d94722bb82ac2545a65453.aspx" height="602" width="802" /><br /> </li>
<li>Click <strong>Save</strong>.</li>
</ol>
<h3><a id="STEP2"></a>STEP 2. Configure Octopus</h3>
<p>As this is a first-time deployment setup, you need to create an environment, modify the lifecycle, create a project group, a customer project, and an Octopus user. If you already have these items in place, you can skip these steps.</p>
<ol>
<li>In <strong>Octopus</strong>, go to <strong>Environments > Create new</strong>.</li>
<li>Add a name and description of the environment, and click <strong>Save</strong>.<br /><br /><img alt="" src="/link/0a807773aa294c06906be57184a8efe5.aspx" height="592" width="802" /><br /> </li>
<li>Go to <strong>Library > Lifecycles</strong> and add a lifecycle: Add a name and description, and add a <strong>phase</strong> with the environment previously created. Click <strong>Save</strong>.<br /><br /><img alt="" src="/link/2a7c790a9f924fc2af4937f03f88b4c8.aspx" height="641" width="800" /><br /> </li>
<li>Under <strong>Projects</strong>, create a <strong>project group</strong> for the customer (if applicable), add a name and description. Click <strong>Save</strong>.<br /><br /><img alt="" src="/link/deb1c2545aa04f1b9059acfc95cc688e.aspx" height="513" width="800" /><br /> </li>
<li>Under <strong>Projects</strong>, create a <strong>project</strong>, add a name and description, and associate it with the <strong>project group</strong> and <strong>lifecycle</strong> created in previous steps. Click <strong>Save</strong>.<br /><br /><img alt="" src="/link/31fabf3948634ec2b8bff05469213172.aspx" height="490" width="802" /><br /><br /></li>
<li>Go to <strong>Configuration > Users</strong>, and create a deployment user for your Octopus server. Add user information and click <strong>New API key</strong> to generate a deployment key. The user can be used for multiple projects, and you might already have an existing deployment user if you have worked with Octopus before.<br /> <br /><img alt="" src="/link/2c3abe7e2ae143e7939f923a5ef142dd.aspx" height="458" width="802" /></li>
</ol>
<h3><a id="STEP3"></a>STEP 3. Configure project in Visual Studio</h3>
<p>In this step you will configure Visual Studio to create Octopus-compatible NuGet packages, and push them to your Octopus deploy server. This step needs to be done for each new project.</p>
<ol>
<li>In Visual Studio, right-click on <strong>References</strong>, locate the <em>OctoPack</em> package and click <strong>Install</strong> to add it to the project.<br /> <br /><img alt="" src="/link/5b563522c10f4f35838c8a954cb5a387.aspx" height="537" width="800" /><br /> </li>
<li>Ensure that you are applying proper versioning settings when building components for your project, as Octopus will use these in the deployment process. Check <strong>AssemblyInfo</strong> to verify these settings.<br /><br /><img alt="" src="/link/d1c8ec137c984d879f6d0ec10ede7e83.aspx" height="525" width="800" /><br /><br /></li>
<li>Right-click on project and select <strong>Unload Project</strong>.</li>
<li>Right-click on project and select <strong>Edit...</strong> to edit the csproj.file for the project.</li>
<li>Edit the csproj file to add the <strong>URL</strong> and <strong>API key</strong> for your Octopus server. The URL can be retrieved in <strong>Octopus</strong> under <strong>Packages</strong>, and the API key can be found in <strong>Configuration > Users</strong> (see STEP 2 above). <br /> <br /><img alt="" src="/link/448ac3bfdd6342349f0e7aa780f3c941.aspx" height="337" width="802" /><br /> </li>
<li>Add the following code to the <strong><PropertyGroup></strong> section in the csproj.file:<br /><br />
<div>
<pre class="language-csharp"><code><!--RUN OCTOPACK START-->
<RunOctoPack>true</RunOctoPack>
<OctoPackPublishPackageToHttp>http://YOUR-OCTOPUS-SERVER-ADDRESS</OctoPackPublishPackageToHttp>
<OctoPackPublishApiKey>YOUR-USER-API-KEY</OctoPackPublishApiKey>
<!--RUN OCTOPACK STOP--></code></pre>
</div>
<br /><br /> <br /><img alt="" src="/link/d08014c54e7f4569ad73ea71be79016a.aspx" height="651" width="780" /><br /><br /></li>
<li>Reload and build the project. A an OctoPack package is created, and pushed to the Octopus server on the URL you specified.<br />A succesful console build message will look something like this:<br /> <code> OctoPack: Packaging an ASP.NET web application (Web.config detected) <br />OctoPack: Attempting to build package from 'dxcdeploy.nuspec'. <br />OctoPack: Successfully created package 'c:\users\name\documents\visual studio 2015\Projects\dxcdeploy\dxcdeploy\obj\octopacked\dxcdeploy.1.0.6010.25791.nupkg'. <br />OctoPack: OctoPack successful <br />Pushing octotest 1.0.6010.25791 to 'http://your-octopus-server-address/nuget/packages'... <br />Your package was pushed. ========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ========== </code></li>
</ol>
<h3><a id="STEP4"></a>STEP 4. Set up the deployment process</h3>
<p>In this step you will set up the <strong>deployment process</strong>, using the components created in previous steps. In step 3 you created a NuGet package and pushed it to your Octopus deploy server. Here you will configure Octopus to create a release, and deploy the package to the Integration environment in DXC Service.</p>
<ol>
<li>In <strong>Octopus</strong>, go to <strong>Library > Packages.</strong> Search for the project under <strong>Available packages,</strong> and ensure that the package you created in the previous step, is available.<br /><br /><img alt="" src="/link/f22e7c81c5d940d6a8317faf289c041c.aspx" height="458" width="802" /><br /> </li>
<li>Go to <strong>Project > Process</strong>, click <strong>Add step</strong>, and select <strong>Deploy Azure Web App</strong>.<br /><br /><img alt="" src="/link/20f4c600265644e1b46b9368d58b330a.aspx" height="522" width="802" /><br /><br /><img alt="" src="/link/9a92a148b5314c7998cb57ce5bb41935.aspx" height="640" width="500" /><br /> </li>
<li><span lang="EN-US">Enter values for<span class="apple-converted-space"> </span><strong>Step name</strong>,<span class="apple-converted-space"> </span><strong>Package ID</strong><span class="apple-converted-space"> </span>(project name), name of your<span class="apple-converted-space"> </span><strong>Web App</strong><span class="apple-converted-space"> </span>(suggested by default) and the <b>Environments</b> condition</span>. Note that under Web Apps, you have the option to use<em> slots</em>, if slots are part of the provisioning of your Integration environment.<br /><br /><img alt="" src="/link/1a26e390931442c8ad2c6be8b12ffe6a.aspx" height="835" width="802" /><br /> </li>
<li>Click <strong>Save</strong>, and verify the deployment process.<br /><br /><img alt="" src="/link/1d90fcf644e84c7dba06f336ffddaf13.aspx" height="522" width="802" /><br /> </li>
<li>Go to <strong>Settings</strong> for the project, add values as below and click <strong>Save</strong> when done:<br /><ol>
<li>Name, description and project group.</li>
<li>Release versioning - select <em>Use the version number from an included package</em>. </li>
<li>Versioning package step - select <em>INTEGRATION</em>.</li>
<li>Package re-deployment - select <em>Always deploy all packages</em>.<br /><br /><img alt="" src="/link/9652b37215c64386b09e23f7cfec9177.aspx" height="522" width="802" /></li>
</ol></li>
<li>You can configure the process to <strong>automatically</strong> push a release to the Integration environment, every time you build your project and a package is pushed to your Octopus server. <span lang="EN-US">Select this in the<span class="apple-converted-space"> </span><strong>Automatic Release Creation</strong><span class="apple-converted-space"> </span>section on the Process page of your project</span>.<br /><br /><img alt="" src="/link/534d3d1ee1d34a5eb5fc8af9a0d35d25.aspx" height="522" width="802" /><br /> </li>
<li>When you have built your first project and created a release following the steps above, go the URL provided in DXC Services for the Integration environment, to verify that the website is working.</li>
</ol>
<h2>Deploying changes</h2>
<p>If you have set up your deployment tool as described above, code changes and <a href="/link/e40ccef4cf424571945bbd382d89ac0c.aspx">Episerver updates</a> done by your team will be pushed to your build and deploy servers, whenever you build. From there, a release will be automatically created (if you selected that option), and pushed to the Integration environment in the Azure cloud. </p>
<p><img alt="" src="/link/7c26f24fcde74f55b96f1c70d31b1a93.aspx" height="364" width="702" /></p>
<p>You can use the Integration environment to regularly test and verify your changes, before deploying to production. Note that in DXC Service, deployment from Integration to the Production environment is managed by Episerver. See <a title="Deploying" href="/link/ce2a173c294d41c3a95e81b40f814e54.aspx">Deploying</a> for more information.</p>
<h2>Related topics</h2>
<ul>
<li><a href="/link/d0fb45fcfe7e4d2e875444b6ca2cce2b.aspx">Episerver continuous release process</a></li>
<li><a href="/link/bac2c19b2b2b4a6fb3eba23049cdc3d1.aspx">Episerver weekly updates</a></li>
<li><a href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">Episerver release notes</a></li>
<li><a href="/link/5d17930c8cda4653b6d50a78c589a51e.aspx">Episerver DXC Service</a></li>
<li><a href="http://docs.octopusdeploy.com/display/OD/Home" target="_blank">Octopus Deploy</a></li>
</ul>
<p><a href="#TOP">Go to top of page</a></p>Ektron and WURFL device detection library/articles/Items/ektron-and-wurfl-device-detection-library/2016-04-04T14:51:29.0000000Z<p>Episerver (and the former Ektron) has recently ceased including WURFL - a device detection library - with the Ektron product line, which was previously included as a complimentary add-on. See the article <a href="/link/22663370ce7a4b06a2af91c155ae3363.aspx">Episerver and WURFL</a> by Episerver's <a href="/link/5341f632537c4b0ab6b8fb651bd310f8.aspx?userid=26a20235-9fa8-e411-9afb-0050568d2da8" target="_blank">James Stout (Technology Evangelist)</a>, for more information and guidelines for how to proceed, if your websites are using WURFL.</p>Cloud development considerations/articles/Items/cloud-development-considerations/2016-04-01T10:31:14.0000000Z<h2>Common questions about Cloud development</h2>
<p><a href="/link/5d17930c8cda4653b6d50a78c589a51e.aspx">Episerver Digital Experience Cloud Service (DXC Service)</a> enables customers to improve the efficiency and scalability of their operations. Developing in the cloud, however, requires some additional considerations when compared to previous approaches.</p>
<p>With that in mind, we have collected answers to frequently asked questions about the DXC Service. Episerver's Viktor Sahlström is lead developer on the cloud solution, and Fredrik Tjärnberg, Development Manager, is responsible for the R&D department in Sweden.</p>
<p><img alt="" src="/link/12a82218aee84f309df238fb1886e9dd.aspx" height="527" width="539" /><br /><em>Fredrik Tjärnberg (left) and Viktor Sahlström</em></p>
<p><strong>How has the launch of the DXC Service gone so far?</strong></p>
<p><strong>Fredrik:</strong> We successfully launched the DXC Service seven months ago, and it's already live with a number of customers and under development with many others.</p>
<p><strong>Viktor:</strong> Many developers think that the DXC Service is great. We're also working to continuously improve the solution and are actively listening to feedback from developers.</p>
<p><strong>How many code bases does the DXC Service support?</strong></p>
<p><strong>Viktor:</strong> You can have as many code bases as you like. The important thing is that they come out as a single application, because the DXC Service by default only supports one application.</p>
<p><strong>Fredrik:</strong> Right, that's an important distinction to make, between code bases and applications. Of course, the solution is flexible, and provides an option for customers to add additional applications to their DXC Service when needed.</p>
<p><strong>Can I run as many websites as I like on one DXC Service license?</strong></p>
<p><strong>Fredrik:</strong> Yes, unlimited websites is a very popular feature because previously you had to pay for this. With the DXC Service, customers can launch campaign or other related sites with extreme simplicity, not having to think about extra licenses or associated costs. The business side tends to like this a lot! Keep in mind, though, that with the DXC Service you have to use the functions a little differently, since some changes you make will affect all the sites and not just one.</p>
<p><strong>Viktor:</strong> Also note that all entities are shared, and some can't be hidden, such as Visitor Groups and crawled data. If the sites are administered by different editors, be sure to set the rights so that they don't have access to confidential information or publish on each other's websites by mistake.</p>
<p><strong>Can I configure different environments for different purposes? For example, if I have a live connection to a payment system in production, but don't want it to be live in integration?</strong></p>
<p><strong>Fredrik:</strong> All environments are configured the same way, but there is a solution for this. Using a setting in the DXC Service, you can compile code that knows which environment it's in. The solution for payments may take a little more planning, especially if you have a third-party connector that's not adapted for the DXC Service.</p>
<p><strong>Viktor:</strong> The DXC Service will definitely support configuration transformation in the future. In the meantime, we recommend sending the different configurations to our Managed Services department, who will make sure they end up in the right environment.</p>
<p><strong>Can I use another search solution than Episerver Find?</strong></p>
<p><strong>Fredrik:</strong> The answer is yes. But why? The developer feedback on Find is great, and it is included in the DXC Service. Considering it's nicely integrated into the platform and we drive the roadmap alongside our other product development efforts it's a win win scenario.</p>
<p><strong>Can I use Search, the built-in search function in Episerver CMS, instead of Find?</strong></p>
<p><strong>Viktor:</strong> I wouldn't recommend it. A key value of the DXC Service is its automatic-scalability. Search is file-based, and gets corrupted when the DXC Service scales and the index file is copied to a new machine.</p>
<p><strong>How do I deploy new code in the DXC Service, and how long does it take?</strong></p>
<p><strong>Fredrik:</strong> Developers can deploy directly to the Integration environment via industry standard tools that work with Azure WebApps. When you're ready to deploy to Production or Pre-production, you send a deployment ticket to our Managed Services department who makes sure the code works. We have people who only do deployment, and they usually get to work on it within an hour. How long it takes to check the code depends on the solution. An upgrade that involves data migration might take another hour.<br />As a side note, another cool thing not everyone might realize is that we can also deploy production data back to the other environments. This makes it really easy for developers or QA to work with real data in those environments without adding much work to their day.</p>
<p><strong>Viktor:</strong> You can also specify a time window for deployment, for example, if you have an online store and don't want to deploy when you have a lot of visitors.</p>
<p><strong>What Azure services can I use with the DXC Service?</strong></p>
<p><strong>Fredrik:</strong> The DXC Service runs on Azure, so some of its services are already included in the solution. These include WebApps as its foundation, SendGrid for outbound mail, Storage for persisting different types of data and Service Bus for distributed queue and message handling. However, some Azure services are not included in the standard packing.</p>
<p><strong>Viktor:</strong> If there are certain Azure features you need, be sure to discuss this with Episerver before you start development so that we can arrange a special solution.</p>
<p><strong>Where can I find the Episerver logs?</strong></p>
<p><strong>Fredrik:</strong> You need a special login to the Azure portal to see them. Ask Managed Services for access credentials.</p>
<p><strong>How do I make a hot fix? I need to quickly fix something in production and don't want to throw away everything in the other environments.</strong></p>
<p><strong>Viktor:</strong> Contact Managed Services and tell them you want to make a hot fix. We have a sneak path you can use.</p>
<p><strong>Have more questions about the DXC Service? </strong></p>
<ul>
<li><a title="Episerver Managed Services" href="http://www.episerver.com/services/support/" target="_blank">Contact Managed Services</a></li>
<li><a href="/link/5d17930c8cda4653b6d50a78c589a51e.aspx">DXC Service section on Episerver World</a></li>
</ul>EMVP Q&A on Cloud deployment/articles/Items/emvp-qa-on-cloud-deployment/2016-03-13T20:46:23.0000000Z<h2>Everything you want to ask about Cloud</h2>
<p>What are the main differences between running <a href="/link/5d17930c8cda4653b6d50a78c589a51e.aspx">Episerver Digital Experience Cloud Service</a> and hosting your own solution? We spoke with two <a href="/link/0e4c738fd29f4c0ebe73a97178bc995a.aspx">EMVPs (Episerver Most Valuable Professionals)</a> to learn about their experiences. Ted Nyberg is CEO of <a title="Ted & Gustaf" href="http://tedgustaf.com/" target="_blank">Ted & Gustaf</a>, and Johan Kronberg is a software architect at <a title="NetRelations" href="https://www.netrelations.com/en/" target="_blank">NetRelations</a>.</p>
<p><img alt="" src="/link/98e696e368664d6083980b6a66a97f92.aspx" height="535" width="802" /><br /><em>Johan Kronberg (left) and Ted Nyberg</em></p>
<p><strong>What's the main difference between running Episerver Digital Experience Cloud Service and hosting a solution yourself?</strong></p>
<p><strong>Johan:</strong> That Episerver hosts the entire platform for you, and makes sure it's always up and running. It's basically platform as a service.</p>
<p><strong>Ted:</strong> Exactly, you don't have to think about servers per se, scaling and deployment are part of the service.</p>
<p><strong>For what projects have you used Digital Experience Cloud?</strong></p>
<p><strong>Johan:</strong> We've used it for the city of Nacka's upcoming website and intranet, and another client as well.</p>
<p><strong>Ted:</strong> We're currently working on a new online platform for a multinational customer. It's not launched yet, but the environment for development and testing is up and running.</p>
<p><strong>What are the benefits of the Cloud for customers?</strong></p>
<p><strong>Johan:</strong> The biggest benefits we've seen have been better response time and uptime, compared to traditional hosting. I'd say the included CDN service and deployment process are the main reasons for this.</p>
<p><strong>Ted:</strong> With traditional hosting our client had to pay for high-capacity servers that can handle peaks in sales, even though that capacity isn't needed for most parts of the year. In Digital Experience Cloud Service, capacity can scale with demand.</p>
<p><strong>What's your experience of running several websites on the same license?</strong></p>
<p><strong>Ted:</strong> Digital Experience Cloud Service is great if your websites use the same application and database. Such as our client's websites in our current project, which will technically be the same in all countries.</p>
<p><strong>Johan:</strong> Yes, but if your websites use different applications you might be better off buying a license for each. Not just to make it easier for developers – sharing a license can also be confusing for editors, who will see content and information from other websites.</p>
<p><strong>Some developers wonder why they can't access the servers. Why is that?</strong></p>
<p><strong>Ted:</strong> I know some people think it's strange, but if Episerver is to uphold their SLAs, they must also be in control of what happens behind the scenes.</p>
<p><strong>Johan:</strong> Episerver has staff that makes sure that your website is always up and running. I think that outweighs the possible disadvantages of not having direct access to the server.</p>
<p><strong>Since developers can't access the servers, they have to ask Episerver to deploy new code. How does this affect development?</strong></p>
<p><strong>Johan:</strong> One thing to keep in mind is that it takes longer to deploy new code. First you must contact Episerver, who creates a backup of the existing environment, moves the code to preproduction, and run tests to make sure your code works. So, things you want to be able to change quickly, for example certain JavaScript, CSS and things like texts on buttons, should not be part of the deployment package, but placed in the edit interface.</p>
<p><strong>Ted:</strong> Some people might find this process annoying, but I think it's a good thing. It guarantees that deployments are always done in a consistent, and rather sophisticated, manner. Since Episerver reviews deployments before go-live, and takes responsibility for the SLA, deployments can be a less dramatic experience for both customers and developers.</p>
<p><strong>Johan:</strong> Yes, and if you've done something really stupid, it's almost guaranteed to be discovered.</p>
<p><strong>Digital Experience Cloud Service runs on Azure. Does that mean I can combine Digital Experience Cloud Sevice with all other Azure services?</strong></p>
<p><strong>Ted:</strong> Some Azure services are integrated into Digital Experience Cloud Service, but not all. If you want to use other services than those already available, you can ask Episerver to create a special packaging of Digital Experience Cloud Service for you. Or, you could pair the standard packaging of Digital Experience Cloud Service with Azure services of your own.</p>
<p><strong>Johan:</strong> Whichever option you choose, I recommend discussing it with Episerver first.</p>
<p><strong>Do you plan the architecture differently when using Digital Experience Cloud Service, as opposed to h<strong>osting a solution yourself</strong>?</strong></p>
<p><strong>Johan:</strong> Yes, given that Episerver takes responsibility for everything we put into Digital Experience Cloud Service, we try to put as much as possible there instead of hosting parts separately.</p>
<p><strong>Ted:</strong> I agree, projects we host ourselves generally have a more decentralized structure.</p>
<h2>Want more information on Cloud?</h2>
<p><a title="Dev chat on cloud and Azure" href="https://plus.google.com/b/115633273288707301955/events/cqaue2hvfi287mc9s1aj26fhpj0" target="_blank">Join the DevChat on March 30</a> to learn the benefits of running Episerver on Azure and using Episerver Digital Experience Cloud Service.</p>The new Projects feature/articles/Items/the-projects-feature/2015-11-09T14:33:11.0000000Z<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]-->
<p class="MsoNormal">Last year, EPiServer released the <a href="/link/18c5228d9fcb4922976c83db606c4ab0.aspx">project gadget</a> allowing editors to work on multiple content items and publish them at the same time. Now, a new and extended version of this feature, called Projects, has been released. This blog post provides an overview to this feature, check out the <a href="/link/3aa770bc7f0044fb9175c18048c0d2e7.aspx">user guide</a> for a detailed description and instructions on how to work with projects.</p>
<p class="MsoNormal">Just like the project gadget, the purpose of the projects feature is to let editors work on and publish a number of items at the same time. This is especially useful when you are working with related items, such as a Christmas campaign or new product launch, and want to publish a set of new or updated content at a specific time.</p>
<p class="MsoNormal">One of the major additions is the possibility for editors to collaborate in preparing a project for publishing. While you work on items in a project, you and your coworkers can comment on the project or on individual items in the project, and users can be notified of comments through e-mails.</p>
<h2 class="MsoNormal">New user interface</h2>
<p><img alt="" src="/link/759f505b8da8485fa0c2e727b4d23e72.aspx" height="613" width="1060" /></p>
<p class="MsoNormal">You enable the project feature from the admin view (<strong>Config </strong>><strong> System Settings </strong>><strong> Editing</strong> ><strong> Enable Projects</strong>). The project feature is visualized with a project bar at the bottom of the EPiServer CMS window.</p>
<p class="MsoNormal"><img alt="" src="/link/052ff80f44bf4fed929b5ecf195c6e33.aspx" height="121" width="369" /></p>
<p>When you create a project and it is active in the project bar, editing actions (such as creating and updating items) automatically associate the items with the project. You need to manually deactivate the project in the project bar to stop EPiServer from associating items with the project.</p>
<p>Another new feature is a project overview and a project items navigation pane which display content items associated with the active project. From the overview, you can set multiple project items as <b>Ready to publish</b> and then publish them by the click of a button. You can also schedule items for later publishing.</p>
<h2>Project collaboration</h2>
<p>In the project overview, you can also add comments to projects or project items. This is a great way to let your coworkers know what you have done, ask them to review or just to keep track of what remains to be done.</p>
<p><img alt="" src="/link/3f15905afafc4e1081d0b96f762903e4.aspx" height="667" width="974" /></p>
<p>You can tag a coworker in a comment and the coworker is notified of the comment in an e-mail. If someone comments on something you have done in a project, such as setting a page to Ready to publish, or replies to one of your comments, you receive an e-mail notification.</p>
<p><img alt="" src="/link/d6ffce9a060a41609406fc06342d6e5a.aspx" height="1529" width="1024" /></p>
<h2>Project preview</h2>
<p>When you are working with a project, you can preview the website as it would appear if all content items in the active project were published.</p>
<h2>Setting up the project feature</h2>
<p>To use the project feature, an administrator must enable it from the admin view. An administrator must also configure the e-mail server for EPiServer to send e-mails to users.</p>
<h2>What is happening to the project gadget?</h2>
<p>The project gadget is still there, with an updated user interface, and works as before when the project feature is disabled.</p>
<h2>So, what's next?</h2>
<p>Are we happy with this and are now leaning back drinking coffee? Yes and no. We are very happy with Projects and hope that a lot of editors will use it as we feel that it will make their lives easier. We also hope to get feedback to be able to continuously improve EPiServer. But there is no rest for the wicked so we have already started on the next big things to make the lives of EPiServer users even easier. We are currently working to make notifications a part of the user interface, to be used with both commenting and workflow collaboration.</p>
<p>Speaking of workflows, we are also working on implementing workflows to let you control at what stage and by whom content can be published.</p>
<p> </p>
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="371">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0cm;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->Forum is open again reCAPTCHA is in/articles/Items/changed-access-rights-for-the-forum/2015-05-19T09:27:34.0000000Z<p><strong>Update May 26</strong></p>
<p>The forum has been reopened - you no longer need partner access to post.</p>
<p>The access to the forum was restricted for about a week. I did not receive much feedback during that time, but the feedback I did get was mostly negative. That was expected though since the only affected people were those who lost access. I have now decided to reopen the forum and try other approaches to combat spam. Mainly for two reasons:</p>
<ul>
<li>The users that benefit the most from the forum are those who are not employed at a partner company. Since they don't have access to the support system the forum is place they go to seek help. Shutting them out from the forum will drive them away from the community, we'd much rather have them stay. This is kind of obvious in retrospect but I apparently needed someone to point that out for me - thank you, Luc and others.<br /><br /></li>
<li>I was not particularly happy with the lockdown solution either and I felt bad linking this article and replying "this is why you can't post anymore". It felt wrong.</li>
</ul>
<p>Instead of the access restriction I have added Google's reCAPTCHA to the new thread and reply forms. This is a relatively simple CAPTCHA that most often only requires you to check a box but sometimes you need to select images based on certain critera. As i mentioned in the original message (below) I believe that most of the spam is not posted by bots - we'll see what effect the CAPTCHA has. Either way we now have robust bot protection.</p>
<p>As before, please comment below.</p>
<p><strong>Original message from May 19</strong></p>
<p>Around the same time as this article is published the access rights for the forum will be changed. After the changes have been made only accounts that have been associated with a partner company are allowed to post in the forum. Read access will still be granted to everyone.</p>
<p>The reason for this decision is the large amount of spam that has been posted during the last few months. The traps I've laid to try to catch and discard posts by bots have had no effect, this means that either that bots don't fall for the traps or the spam is not posted by bots. My belief is that the latter is true.</p>
<p>We have discussed other solutions to the problem, mainly two that are still on the table:</p>
<ul>
<li>Use CAPTCHA. An annoyance for everyone that definitely will shut out bots but will not stop a determined spammer.</li>
<li>A wait period and/or a posting limit for new accounts. Annoying for new members but, again, will not stop determined spammers.</li>
</ul>
<p>Please post any feedback in the comments below, I want to have a solution in place that we're all happy with.</p>New release of EPiServer CMS with enhanced preview and improved SEO/articles/Items/new-release-of-episerver-cms-with-enhanced-preview-and-improved-seo/2015-02-23T09:18:00.0000000Z<p>Today we're releasing EPiServer CMS version 8.0.0. I want to highlight this release since it contains a number of important updates, as well as some small breaking technology changes.</p>
<h2>Multi-publish and preview</h2>
<p>The beta stamp from projects is now removed. Projects make it possible to group content that you're working with, such as a campaign that contains several landing pages, teasers, products and videos. You can then preview all the content as if it was published, making it easy to see exactly what the experience will be like. When you're all set you can decide to go live immediately or schedule it for publish at a later date.</p>
<h2>Support for canonical URLs</h2>
<p>EPiServer has always supported the use of canonical URLs, but now it is easier than ever to setup multiple domains and ensure that there is only one canonical URL. This works for both pages and products and is essential to avoid a penalty from search engines for duplicated content. The feature includes adding canonical link elements to the HTML head of your pages and redirecting requests to your primary domain. In a later release we'll be adding alternate language versions as well.</p>
<h2>Better ways to organize content types and properties</h2>
<p>You can now control grouping, including access rights, of content types and properties using a typed model. This feature will make it easier to organize the edit interface for your customer's specific needs.</p>
<h2>Improved control to ensure design consistency</h2>
<p>One of the most common requests when it comes to block management is the possibility to restrict which blocks can be used where. I'm happy to say that you now can do exactly that! We've also added other functionality to take care of more advanced needs around content control.</p>
<h2>Performance improvements</h2>
<p>We're always working on improving performance. In this release we've made optimizations to the core APIs as well as improved the testability.</p>
<h2>Updated UX guidelines</h2>
<p>Our UX guidelines, available at ux.episerver.com, is the place to go if you want to make sure that your EPiServer add-ons and customizations have the same look and feel as the platform itself. The UX guidelines are now updated and simplified using new refactored CSS that is available in this release.</p>
<h2>Updated browser support</h2>
<p>Our policy for Internet Explorer is to support the two last versions, but before removing support for a specific version we want to make sure that few customers are affected. For quite some time we have supported the three latest versions (9, 10 and 11), but with this release we're removing support for Internet Explorer 9.</p>
<h2>Updated major version number</h2>
<p>The technology changes made to support this causes an increment in the major version number to 8 to follow semantic versioning. Read Linus Ekström's blog post, linked below, to get all the details and to see if this affects your solution. If the customer has an active subscription the license that has been used for 7.x will continue to work. When it comes to how certifications are handled for new major versions we will soon give you an update on that. But, rest assured, your EPiServer 7 certification will continue to be valid.</p>
<h2>Related information</h2>
<ul>
<li><a title="EPiServer - update 55" href="/link/47427e695841460ab6787e0c67f22742.aspx">Release information</a></li>
<li><a title="Add-ons support for CMS 8" href="/link/78da612d1dd24b428d3e8cd8d322fb24.aspx">Add-ons support for CMS 8</a></li>
<li><a title="EPiServer User Guide" href="http://webhelp.episerver.com/15-1/EN/Default.htm" target="_blank">User guide (15-1)</a></li>
<li><a href="http://thisisnothing.nystrom.co.nz/2015/02/12/improved-support-for-canonical-urls/" target="_blank">Improved support for canonical URLs</a> - blog post by Henrik Nyström</li>
<li><a title="Performance improvements in the PropertyDataCollection" href="http://thisisnothing.nystrom.co.nz/2015/02/12/performance-improvements-in-the-propertydatacollection/" target="_blank">Performance improvements in the PropertyDataCollection</a> - blog post by Henrik Nyström</li>
<li><a title="The new and improved allowed types" href="/link/3bd193af4f804116b80ceab5b3589de5.aspx">The new and improved allowed types</a> - blog post by Ben McKernan</li>
<li><a title="Changes regarding language handling during content loading" href="/link/bdc9bd9a39d44b7ba819f52f887c69b3.aspx">Changes regarding language handling during content loading</a> - blog post by Johan Björnfot</li>
<li><a title="Upgrading your site and add-ons to EPiServer CMS 8 pre-release" href="/link/3aa4fff923ff40838a2060f9397c7c16.aspx">Upgrading your site and add-ons to EPiServer CMS 8 pre-release</a> - blog post by Linus Ekström</li>
<li><a title="Typed tabs/groups" href="/link/9f3313138f054433828e803bf9fce166.aspx">Typed tabs/groups</a> - blog post by Per Bjurström</li>
<li><a title="Projects" href="/link/18c5228d9fcb4922976c83db606c4ab0.aspx">Projects</a> - blog post by Magnus Baneryd</li>
</ul>EPiServer World: Updates for improved user experience/articles/Items/episerver-world-updates-for-improved-user-experience/2015-02-13T09:28:31.0000000Z<p>There are a lot of things happening right now. We’re processing our backlog at a steady pace. Some updates are done in back-end, but the things you may have already noticed are the ones we have released concerning front-end.</p>
<h2>New add-ons page</h2>
<p>With a larger amount of add-ons, the need for a more structured section page for add-ons was increasing. The solution was grouping the add-ons according to <b>function</b>.</p>
<p>Our hope is that you’ll get a <b>better overview</b> of what we have to offer, and that you’ll find the <a href="/link/5988d1f85539420dbb1323b306c12f93.aspx">new add-ons page</a> more easy to use.</p>
<h2>Documentation, developer guide – added navigation</h2>
<p>The update documentation pages for <a href="/link/48dc9b4302234cb18ff58aefa4613106.aspx">CMS</a>, <a href="/link/6c210e1c1e6543b999a79ac32456e8d3.aspx">Commerce</a> (and <a href="/link/199046299d934811aad7f2d5730ccdb3.aspx">Find</a>) were a first step to improve the developer guide. We have now taken the next step and added the page structure on all documentation pages as well. This way, it’s easier for you to navigate between different the different items. </p>
<p><img alt="" src="/link/9ea5767ebf0a47638761048a78639a59.aspx" height="623" width="1218" /></p>
<p> </p>
<p>If you want to read the page in full width, click on “<b>Hide menu</b>” – and the content will use the entire page width. As it was prior to the change.</p>
<p>Stay tuned for next update!<br /> <i>EPiServer Web Team</i></p>Moving forward – added features on EPiServer World/articles/Items/moving-forward--added-features-on-episerver-world/2015-02-05T16:19:15.0000000Z<p>We have – of course – launched some new features since December. Features like:</p>
<p><b>- Site search</b>: Added a “People”- filter. Makes it easier to find your fellow members on World.</p>
<p><img alt="" src="/link/6ec86317915a4415a7512a90993fc459.aspx" height="147" width="789" /></p>
<p><b>- Release notes</b>: Added product groups, listing all packages for a specific product. <a title="Release notes for EPiServer updates" href="/link/76974ad8d2a84c1b989ad0ac453ab663.aspx">Try it out</a>! </p>
<p><b>- Start page</b>: Added team blog listings. Our development teams each have a blog, to better gather all blog posts regarding EPiServer CMS and Commerce (to start with).</p>
<p><b>- Start page</b>: Longer blog introductions to enable a better understanding of the blog post.</p>
<p>Besides from the above list, we’re continuously working on smaller updates and backend improvements.</p>
<p>Together with the requests posted on “<a href="/link/773b33f40b5f42288bce1987fa6827d1.aspx?productFilter=EPiServer+World">Help us improve EPiServer World</a>”, we have a long back-log with a mix of front- and backend changes.</p>
<p>Stay tuned for next update!<br /><i>EPiServer Web Team</i></p>Re-introducing PowerSlice for Episerver CMS/articles/Items/re-introducing-powerslice-for-episerver-cms/2015-01-14T14:42:52.0000000Z<p>Some time ago <a title="Joel Abrahamsson" href="/link/5341f632537c4b0ab6b8fb651bd310f8.aspx?userid=8aa55d22-e145-dd11-93be-0018717a8c82">Joel Abrahamsson</a> created PowerSlice for Episerver. A lot has happened with the Episerver platform since then, and now we are re-introducing PowerSlice to match the latest and greatest version Episerver. Expanding the page tree to locate a page can be time consuming on large websites with hierarchical navigation structures. PowerSlice provides a different way of listing and managing content, suitable for sites with large numbers of pages and blocks. PowerSlice is also useful for content that does not naturally fit into a hierarchical structure, for example news and articles on media sites, and blog postings.</p>
<p>A special thanks goes to <a title="Viktor Sahlström" href="/link/5341f632537c4b0ab6b8fb651bd310f8.aspx?userid=5a195b24-6628-e411-9f63-0050568d2da8">Viktor Sahlström</a> for code samples and the awesome demo video!</p>
<h2>PowerSlice for editors</h2>
<p><iframe style="border: 0;" src="//www.youtube.com/embed/vaGZGpQB394?VQ=HD720&fs=1" height="663" width="1180"></iframe></p>
<p>How does it work? PowerSlice lets developers divide website content into slices based on its properties. This is then used for creating customized super fast content filtering. PowerSlice is made available to editors as a gadget that can be added to the panes in CMS edit view. </p>
<p>The slices you see are filtered on the logged in user and content type. In the example below "slices" are applied for pages, blocks and articles, but more filters can be added. Content within a selected slice can be searched, as well as sorted based on name and publish date.</p>
<p><img alt="" src="/link/718f1cbfa1df4f77a69a6d92370d7934.aspx" height="420" width="800" /></p>
<p>Content can be created directly from the PowerSlice gadget, and you can use the slices in the gadget to add for instance blocks to a page that you are creating. </p>
<h2>PowerSlice for developers</h2>
<p>Installing and using PowerSlice for Episerver CMS is easy, follow the steps below to get started.</p>
<p class="informationBox"><strong>Note</strong>: PowerSlice requires an <a href="/link/ec69a0960ee04e42b6be33efcc90c756.aspx">Episerver Find</a> license because <a href="/link/55fe410f4f65482cab72fb59d47c7561.aspx?documentId=find/8/42FC6CC4">EPiServer.Find</a> is a dependency.</p>
<h3>Installation</h3>
<p>Ensure that you have the <a href="/link/e40ccef4cf424571945bbd382d89ac0c.aspx">Episerver NuGet feed</a> added as a package source in Visual Studio, and then install the <strong>PowerSlice</strong> package.</p>
<h3>Creating a slice</h3>
<ol>
<li>Create a class inheriting from <strong>ContentSliceBase<T></strong> (T is the type you want to list, can be <strong>IContentData</strong>, <strong>PageData</strong>, <strong>MyFunkyPage</strong> etc).</li>
<li>Implement the <strong>Name</strong> property.</li>
<li>Annotate the class with<br />[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]</li>
<li>Done!<br /> </li>
</ol>
<h3>Customizing slices</h3>
<ul>
<li>Override the <strong>HideSortOptions</strong> property and return true to hide the sort links.</li>
<li>Override the <strong>Order</strong> property to control in which order the tabs for slices appear
<div>
<pre class="language-csharp"><code>[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]
public class CategoriesSlice : ContentSliceBase<CategoryPage>
{
public override string Name
{
get { return "Categories"; }
}
public override int Order
{
get { return 5; }
}
public override bool HideSortOptions
{
get
{
return true;
}
}
}</code></pre>
</div>
</li>
</ul>
<h3>Enable content creation</h3>
<ul>
<li>Override the <strong>CreateOptions</strong> property and return one or more CreateOptions.</li>
<li>Each option requires a name/label, a content type and a parent for the new content.
<div>
<pre class="language-csharp"><code>public override IEnumerable<CreateOption> CreateOptions
{
get
{
var contentType = ContentTypeRepository.Load(typeof (TagPage));
var startpage = ContentLoader.Get<StartPage>(ContentReference.StartPage);
yield return new CreateOption(contentType.LocalizedName, startpage.TagsRoot, contentType.ID);
}
}</code></pre>
</div>
<br /><br /></li>
</ul>
<h3>Filter content</h3>
<p>The type argument to the base class is just the first filter, you can add more.</p>
<div>
<pre class="language-csharp"><code>protected override ITypeSearch<EditorialPageBase> Filter(
ITypeSearch<EditorialPageBase> searchRequest,
ContentQueryParameters parameters)
{
return searchRequest.Filter(x => x.Created.MatchYear(DateTime.Now.Year));
}</code></pre>
</div>
<h3>Example slices</h3>
<p>The examples below are used in the PowerSlice demo video [LINK]</p>
<h4>My pages</h4>
<div>
<pre class="language-csharp"><code>[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]
public class MyPagesSlice : ContentSliceBase<SitePageData>
{
public override string Name
{
get { return "My Pages"; }
}
protected override ITypeSearch<SitePageData> Filter(ITypeSearch<SitePageData> searchRequest, ContentQueryParameters parameters)
{
var userName = HttpContext.Current.User.Identity.Name;
return searchRequest.Filter(x => x.MatchTypeHierarchy(typeof(IChangeTrackable)) & ((IChangeTrackable)x).CreatedBy.Match(userName));
}
}</code></pre>
</div>
<h4>Blocks</h4>
<div>
<pre class="language-csharp"><code>[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]
public class BlocksSlice : ContentSliceBase<SiteBlockData>
{
public override string Name
{
get { return "Blocks"; }
}
}</code></pre>
</div>
<h4>Articles</h4>
<div>
<pre class="language-csharp"><code>[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]
public class ArticleSlice : ContentSliceBase<ArticlePage>
{
public override string Name
{
get { return "Articles"; }
}
public override IEnumerable<CreateOption> CreateOptions
{
get
{
var contentType = ContentTypeRepository.Load(typeof(ArticlePage));
yield return new CreateOption(contentType.LocalizedName, ContentReference.StartPage, contentType.ID);
}
}
}</code></pre>
</div>
<h4>Pages</h4>
<div>
<pre class="language-csharp"><code>[ServiceConfiguration(typeof(IContentQuery)), ServiceConfiguration(typeof(IContentSlice))]
public class PagesSlice : ContentSliceBase<StandardPage>
{
public override string Name
{
get { return "Pages"; }
}
} </code></pre>
</div>
<h2>Related information</h2>
<ul>
<li><a title="PowerSlice for latest EPiServer" href="https://github.com/episerver/PowerSlice" target="_blank">PowerSlice source code on GitHub</a></li>
<li><a title="PowerSlice demo video" href="https://www.youtube.com/watch?v=vaGZGpQB394" target="_blank">PowerSlice demo video on YouTube</a></li>
</ul>Installing Commerce using Visual Studio extensions/articles/Items/installing-commerce-using-visual-studio-extensions/2014-12-21T07:50:00.0000000Z<p>We have received a lot of feedback from developers requesting an easier way of creating an empty EPiServer Commerce project without using Deployment Center. <a href="/link/9bf4467c4d2b4963b3bf9f9d6550ab30.aspx">Update 48 of EPiServer</a> with Commerce 8.6 includes the possibility to install a new EPiServer Commerce site from Visual Studio, using an extension package for Commerce.</p>
<h2>About the features</h2>
<p>Key points about the new features:</p>
<ul>
<li>The EPiServer.Commerce NuGetpackage is responsible for adding the correct Commerce configuration and installing the Commerce database. It does not install any CMS configuration or database.<br /> </li>
<li>The installed database is in the form of a <strong>local mdf file</strong>. Please make sure the parent folder where you are installing has <strong>write permissions </strong>since Local Database does not respect the Administrators group. If you want to move the database, just attach the file to an SQL server instance.<br /> </li>
<li>There is an SQL file in the tools folder of the EPiServer.Commerce.Core package that contains the install file for the current version of Commerce. This can be used to create a new database for automation tasks.</li>
</ul>
<p class="Note"><strong>Note</strong> that installed website will not have any templates. Furthermore, the installation does not include Commerce Manager (the Commerce administration interface), however most parts of Commerce can be accessed from code.</p>
<h3>Creating a project</h3>
<p>Follow the steps below to create an empty Commerce project:</p>
<ol>
<li>In Visual Studio, <a href="/link/258b438f622b46818823d5fd9b99ebb1.aspx">create an empty website with CMS</a>.</li>
<li>Right-click on <strong>References</strong> in your project, and select "Manage NuGet Packages".</li>
<li>Select "EPiServer" under <strong>Online </strong>and click "Install" for the <strong>EPiServer.Commerce </strong>package. This will add all the latest Commerce components to your project.</li>
<li>In the Package Manager Console in Visual Studio, run the command "update-epidatabase".</li>
<li>Build your solution and open the website in a browser.</li>
<li>Verify that the site is working and that you can log in to the user interface (default path is http://yoursite/episerver).</li>
</ol>EPiServer CMS certification update/articles/Items/certification-updates/2014-12-19T15:19:25.0000000Z<p>It's now been a little over 2 years since we released EPiServer 7 CMS. With EPiServer 7 we made some big changes to both the platform and the UI, which led to a new certification for developers to ensure that partners and customers could use the CMS to its full potential. Earlier this year we also introduced certification for EPiServer Commerce to cover the whole platform.</p>
<p>Even though we released EPiServer 7 we of course still had several customers using EPiServer CMS 6. That's why we decided to keep the certification for version 6 for a transition period. This period has now come to an end. Starting in January we will remove the cerfication for EPiServer CMS 6 and the certification will from now on be based on a specified version of the platform and updated regularly. More details around this will be covered in an article early next year.</p>
<p>If you're interested in taking a certification or want to know more about what they cover, you should head over to the EPiServer Certification page linked below.</p>
<h2>Read more</h2>
<ul>
<li><a href="http://www.episerver.com/Training/EPiServer-Certification/">EPiServer Certification</a></li>
</ul>Google Analytics for EPiServer with support for Universal Analytics/articles/Items/google-analytics-for-episerver-with-support-for-universal-analytics/2014-12-09T11:21:00.0000000Z<p>Google Analytics for EPiServer makes it easy to enable tracking and let editors, marketers and merchandisers access analytics data directly inside EPiServer. </p>
<p>Today we’re releasing a new updated version of Google Analytics for EPiServer with several changes that let business users better understand how content performs to increase engagement and conversions. There are four major areas that have been improved, each described below.</p>
<h2>More configuration alternatives and support for Universal Analytics</h2>
<p>When configuring the add-on you can now choose if you want to use Classic Analytics, Universal Analytics or a custom script tag. Classic Analytics are for customers who have not yet upgraded their Google Analytics account. The Universal Analytics alternative lets you take advantage of the latest functionality in the Google Analytics platform, including better cross channel tracking, improved report capabilities, enhanced e-commerce, as well as extended tracking. The custom script tag is something that is recommended if you want to use Google TagManager and insert all your scripts and custom tracking that way, or if you want to manage everything from your own code.</p>
<h2>Simplified developer setup and custom tracking</h2>
<p>Google Analytics for EPiServer can be installed as a solution add-on inside Visual Studio. This means that you can safely add custom tracking through code and use it as a dependency in your projects. The new version has a simplified API and with the Universal Analytics support you have better tracking capabilities. We have also made sure to improve our documentation around how to add custom tracking to get you started faster.</p>
<h2>Enhanced e-commerce analytics</h2>
<p>The Universal Analytics supports enables something Google calls “Enhanced Ecommerce tracking” which is a must if you want to get an overview on how your different products and product categories performs. Since this tracking involves both interactions with the shopping cart as well as the whole checkout process it’s something that you will need to add as custom tracking. When the tracking is added, you can also expose some of this information to merchandisers inside EPiServer so they don’t need to login to Google Analytics to get important insights. See link to Steve Celius’ blog post below to get a great introduction on how to enable this on an e-commerce site.</p>
<h2>Improved on page analytics</h2>
<p>We’ve also made small but important improvements to the page analytics gadget that lets editors, marketers and merchandisers see analytics next to the content that they are working on. Any segment can now be used to filter the data charts and we have highlighted the data that marketers have pointed out as most important. Related to this there is also a new acquisition section to immediately see how much traffic pages drive and from where. All figures are now compared with site average, which makes it easy to understand how specific content performs. As an example you can now see the bounce rate on a landing page for customers that are part of the winter sales campaign and compare that with site average.</p>
<h2>Next steps</h2>
<p>The new version is currently in beta and can only be installed as a solution add-on inside Visual Studio. We’re expecting to remove the beta label beginning 2015 and at the same time we will make the add-on available as a one-click installation as well.</p>
<h2>Further reading</h2>
<ul>
<li><a href="/link/8b1a294e8d8542d893227e83de1f1ef2.aspx">Google Analytics Tracking and Customization - blog post by Steve Celius</a></li>
<li><a href="/link/e1f955cf1a3d45a2882f9f9b32d9cfc3.aspx">Documentation for installation, configuration and customization</a></li>
<li><a href="/link/311b866679fa4911897a9b8078071cc6.aspx">User guide</a> (added PDF document)</li>
<li><a href="/link/27219dba83654f7d8201b4efa62d575b.aspx">2 important improvements for managing add-ons in EPiServer</a></li>
</ul>