Using Microsoft Share.Point 2. 01. 3 to build a robust support and training portal.This documentation is archived and is not being maintained.Technical Case Study.June 2. 01. 5The Microsoft IT team that.Microsoft Dynamics needed.CMS with a. solution that would better support a complex range of content and customer.Using Microsoft Share.Point 2. 01. 3 as a new CMS, the team created a support.The portal also makes.Situation. Solution.Benefits. Products Technologies.The Microsoft Dynamics support and training portal used an old publishing platform that was nearing the end of its life cycle.Publishing content on this platform was challenging, and customers and partners often struggled to find the information they needed.Microsoft IT used Share.Point 2. 01. 3 as a CMS to create a state of the art support and training portal that integrates product information and updates from a wide variety of sources, uses a consistent model to help customers and partners solve problems, and makes answers to product questions easy to find in searches.Improves discoverability Responds quickly to market demand.Provides a robust user experience.Consolidates diverse systems.Enables self support capability.Simplifies authoring.Microsoft Share. Point 2.Open source and standard web technologies.Situation. Microsoft Dynamics is one of the most complex product.Microsoft supports.Training and support content must cover a.Microsoft Dynamics Ax Erp Goes Mobile' title='Microsoft Dynamics Ax Erp Goes Mobile' />Almost all Microsoft.Dynamics products involve a partner who is certified to sell, implement, and.Partners are vital to the Microsoft Dynamics business.Microsoft. Dynamics products involve complex software and support highly sophisticated.Although partners provide some customer support, most customers.Microsoft for self help and training.In the old CMS, Microsoft.Microsoft Dynamics Ax Erp Goes Mobile' title='Microsoft Dynamics Ax Erp Goes Mobile' />Microsoft Dynamics.This portal isolation and several other limitations hindered the productivity.The following are some of the challenges and.CMS The user experience was unintuitive and required constant customization.Because of rigid page construction, every new user specific page design required a new custom template.This limitation resulted in an inconsistent and unattractive user interface.Content was hard to find and related content was disconnected, which led to excess support requests from users who were unable to resolve questions on their own.Search results were unproductive.Often, customers and partners found content only if they already knew where to look for it.To begin a search, a user had to first filter by category.Contents Q1 2015.Tweet It Whats your most important goal related to Microsoft Dynamics GP Share your thoughts on Twitter GPUG.In addition, keyword searches did not always produce accurate results, search results were not prioritized by relevance, and an unstable search index caused Search Center downtime. Crack Keygen Eset Smart Security 6 Registration . Authoring was painful.There was no standard process across all sites and subsites for authoring and approving content.Because authors had little control over the publishing process, they often needed support from the IT user support and operations teams.Localizing content was also a difficult manual process.Publishing tools were time consuming.The workflow for adding content forced authors to concentrate on formatting and positioning content and often on coding HTML and cascading style sheets CSS instead of on content quality.Authors also had to manually reinsert and reformat the same content on many pages, creating content inconsistencies over time that made reuse of content impractical or impossible.The platform was not scalable or extendable.The Microsoft Dynamics team was aggressively trying to increase the user base for the customer and partner portals while introducing new products and trying to gain market share.The CMS was an obstacle to these goals because it was hard to scale and did not offer a structured, streamlined method for onboarding new products.Integration with other portals was difficult.Microsoft business teams were creating separate infrastructure and web experiences.Because the old CMS lacked the capability to aggregate these experiences through cross site search, the user experience was broken and confusing.Solution. The primary business need was a platform that could scale.Microsoft Dynamics business.Another necessity.ERP solution and the customer relationship.CRM solution. Microsoft IT needed to create a holistic user.Integration would also expose important information from ERP and.CRM solutions to users in the portal in such a way that if an integrated system.The first step in creating a solution to meet the needs.Microsoft Dynamics business was to analyze the existing site.Microsoft IT identified the following requirements The ability to author partner and customer portal content separately, as well as the option to develop single source content content that is created once and can be used multiple times and in multiple locations to display in both portals.Better management of the variety of security, business, and resource needs of the multitude of Microsoft Dynamics products and users.Support for multilingual content management to allow publishing of content based on regional product availability.Ability for regional authors to review content before it goes live in their region.Designated Search Centers for each region, to provide content that is based on regional needs.Dynamic content display based on the type of page that a visitor is viewing.The ability to scale rapidly to support additional users while maintaining performance standards.Intuitive user content filtering based on metadata, and simple promotion of search results and management of relevance.Ability to integrate with other portals such as Microsoft Knowledge Base and the Microsoft Dynamics CRM Community.After analyzing its requirements and the available tools.Microsoft IT determined that using Microsoft Share.Point 2. 01. 3 as a CMS for the Microsoft.Dynamics portal would be an excellent solution.Share. Point 2. 01.A search driven architecture that decouples the presentation and rendering environment from the authoring environment.Integrated search that provides centralized search technology administration.Search analytics that better supports the ability to manage relevancy and boost content.Cross site publishing that lets authors create content once and use it anywhere and in any way.Managed navigation that provides a robust navigational framework tied to metadata that enables contextual content.Term driven pages that let developers render content dynamically.Support for current web standards such as HTML5 and CSS3, which enables improved accessibility.Client side rendering that simplifies customization of the presentation layer.Metadata mapping that lets developers converge metadata from external systems.Variations that support multilingual sites.A pluggable architecture that lets developers add site components based on demand without rebuilding architecture or implementing a complex deployment.Solution architecture.To take advantage of some of the new capabilities of Share.Point 2. 01. 3 and deliver a solution that separates.Microsoft IT built an architecture.Figure 1. Figure 1.Information architecture for the.Share. Point 2. 01.The solution uses one Share.Point 2. 01. 3 farm and includes.Authoring. To simplify and streamline the solution design, Microsoft.IT used the decoupled architecture functions of Share.Point 2. 01. 3. They created two.Microsoft Dynamics product that.The Share. Point 2.Authors create and maintain content once in the.This architecture also provides controlled security.In addition to meeting the requirements of single source.Share. Point 2. 01.Multilingual content management.Microsoft IT uses the Share.Point 2. 01. 3 variations feature to support multilingual requirements and publish content to different regions.Governance for regions is a standard component of the variations framework.When an author of the source region publishes content, Share.Point 2. 01. 3 publishes that content to all regions in a draft state and initiates a workflow.Approvers in different regions decide what content to publish and when.This gives the local market experts decentralized control over the content and allows them to localize it before it goes live.Some Microsoft Dynamics products are not sold in all regions, but multilingual variation allows each region to publish content based on regional product availability.Simplified content authoring solution.The old CMS was optimized for the end user experience authoring and modifying content required extra effort.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |