Connect Learn Share Microsoft Dynamics CRM 2013 Sanaullah

Connect Learn Share Microsoft Dynamics CRM 2013 Sanaullah Khan

Application – New Features § § § § § Reimagined User Interface Site Flattening Navigation Bar and Command Bar Form Controls Composite Controls Auto Save People Pictures Access Teams Business Process Flow @CRMU

Concepts Introduced § December 2012 Service Update – Reimagined User Interface • In-page Experience • Navigation Model – Bing Maps – Auto Save – Business Process Flows @CRMU

Reimagined User Interface Simple • Focus on the essential functions with a clear, consistent purpose that matches user intention Usable • Measure usability, incorporate feedback into designs Modern • Use appropriate web interpretation of Windows 8 UI to create delightful, engaging people and process centric experiences Fast • Design and deliver great perceived performance Loved • Design for Love. Create software that people not only want to use, but simply can’t live without. @CRMU

Reimagined User Interface § December 2012 Service Update – 3 form modes – Classic – Read Optimized (inline controls to enable editing) – Process Flow based UI for • • • Contact Opportunity Lead Account Case @CRMU

Reimagined User Interface § December 2012 Service Update – Form Events/Client SDK was not supported in • Read Optimized form • Process Flow UI form – Fallback to Classic mode § Dynamics CRM 2013 – No Extensibility Gaps – No fallback to Classic mode @CRMU

Ribbonized entities CRM 2011 Dec 12 Service Update CRM 2013 Other Ne • COLAC = Contact, Opportunity, Lead, Account and Case w • RO - Read Optimized Classic UX New • COLAC = Contact, Opportunity, Lead, Account and Case UX/ Classic • RO - Read Optimized. Classic/RO classic New UX Classic/ RO Classic @CRMU

Reimagined User Interface § New Form Experience – Most of the end user facing system entities (30 entities) – All Custom entities § Classic Forms – Classic forms are restricted to System Settings area @CRMU

Refreshed Entities Legend @CRMU

@CRMU

Site Flattening § An attempt to eliminate – Continuous window contextual switches – Excessive window opening which is • Difficult to manage and • Impacts performance § Site Flattening has been implemented to – Reduce the number of clicks – Optimize the use of pop-up windows @CRMU

Site Flattening § In-Page Experience – New Navigation Model – In-page experience rather than pop-up window @CRMU

Navigation Model § Optimized Information display § Quick Access to CRM data @CRMU

Navigation Model @CRMU

Navigation Model § Navigation Levels – Module or Area Selector – Entity Name or Sub Area – Title of the entity record @CRMU

Navigation Bar § Modules or Areas @CRMU

Navigation Bar § Entity Names or Sub Areas @CRMU

Navigation Bar § Entity Records @CRMU

Navigation Bar § Related Records @CRMU

Command Bar § Problem with CRM 2011 Ribbon Model – Provides a lot of information in a very dense format. @CRMU

Command Bar § Why Command Bar ? – Quick and easy access to small set of actions – Less commands with overflow menu – Supports Ribbon migration to new Command bar @CRMU

Command Bar @CRMU

Command Bar Types § § Dashboard Command Bar Form Command Bar Grid Command Bar Associated Grid Command Bar @CRMU

Command Bar § Customise using Ribbon XML § Same schema as CRM 2011 Ribbon XML § Architecture has been optimized to boost performance of – Command Bar rendering experience @CRMU

Form Controls § Inline Lookup Control – Introduced in December 2012 Service Update – Supports in-page experience @CRMU

Form Controls § Three Modes – Read Mode – Edit Hint Mode – Edit Mode @CRMU

Form Controls § Edit Hint Mode @CRMU

Form Controls § Edit Mode @CRMU

Form Controls § Inline Sub-grid Control – Introduced in December 2012 Service Update – Supports in-page experience @CRMU

Sub-grid Types § Form Sub-grids – Unlike CRM 2011, sub-grids do not update form’s contextual command bar/ribbon. § Associated Grids – Based on relationships – Customizable Command Bar § Dashboard Grids § Homepage Grid – Landing page of an entity – Customizable Command Bar @CRMU

Inline editable Sub-grids § Not available for all entities § Products Sub-grid on – – Opportunity Quote Order Invoice § “Role” column of Stakeholder Sub-grid on – Opportunity @CRMU

Inline editable Sub-grids @CRMU

Composite Controls § Name and Address fields in CRM 2013 § Bing Map Control @CRMU

@CRMU

Bing Map Control § Address composite control updates a Bing Map § Multiple Bing Map on a single form are NOT supported @CRMU

Auto Save • Triggers every 30 seconds • Plug-ins on save will run @CRMU

People Pictures § § CRM 2013 supports “Image” data type Only one image per entity is supported Display an image in the form header on any entity Some out of the box entities will be image enabled by default – – Contact Account Lead User @CRMU

Image Upload @CRMU

Image Upload @CRMU

Image Upload @CRMU

Access Teams § § § Collaboration Teams No Security Role Any entity can now be Access Team enabled Only one Access Team per record (CRM Online) More than one Access Teams can be associated per record (On-Premise) @CRMU

Access Teams § Auto-Created Access Teams § User Created Access Teams § Grants Access to – Record – Related child records @CRMU

Access Teams • - Account Team • Full team that works together on an account. May also include an executive sponsor, dedicated support representative and a project manager. - Opportunity Team Sales people that normally work together on sales opportunities. A typical opportunity team might include the account manager, the sales representative and a pre-sales consultant. @CRMU

Access Rights @CRMU

Access Teams @CRMU

Business Process Flow § Streamlined user experience to lead people through the processes § Step-by-Step guide to enter data § Guided stage progression § Available for all entities § Process centric approach @CRMU

Business Process Flow @CRMU

Capabilities § Configuration – – Multiple processes per entity Multi-entity processes Stage-gating Role based processes § End User Business Process Flow UI – Process centric experience § Extensibility – Define process for any entity – Solution Awareness @CRMU

Components § Configure Business Process Flow – Define Stages – Define Steps § Each stage contains a group of steps § Each step represents a field § Stage-gating – Step can be marked as “Required” @CRMU

@CRMU

Add New Stage @CRMU

Add New Step @CRMU

Business Rules § Build client-side Business Logic without writing Java. Script § Not a complete replacement of – Client-side scripting – Plug-ins § UI for Business Rules designer @CRMU

Business Rules § Capability – – – Validate and show errors Set Values Set Required/recommended fields Enable/Disable fields Hide/Show fields @CRMU

Business Rules § Generates Java. Script § Reuses WF Object Model … @CRMU

Questions § Source of Information – Microsoft’s • Website • MSDN Blogs • Documentation – Product experience @CRMU