Announcing the Yammer network for survivors of disasters

I’m very excited that last week on Tuesday 29th July 2014 we announced the availability of the Yammer network for survivors of disasters at the White House Disaster Response Innovation and Recovery Day. I was honoured to be asked to talk at the White House for the announcement and I will remember the day for a very long time! This has been a pet project of mine for some time and to see it come to life in such a big way was amazing. I will share some pictures and more information from the day later on this page. This is a major milestone in my dream for a turnkey rapidly deployable community for survivors of all disasters (natural, political, criminal etc) but there is more to do. If you are an expert in Cloud regulations, Hipaa or Criminal law in relation to cloud data and you want to help please let me know, I may just have a project for you!

If you want to find out more please contact the Microsoft Disaster Response team directly here: www.microsoft.com/disasterresponse. Their twitter page is here: @msftresponse

  You can see the full announcement here (We are on first, about a minute into it): http://www.youtube.com/watch?v=X8eiXjbhfOc   I would like to take this opportunity to thank the team that made this announcement possible : Steve CromptonNoah Chandler from the Yammer team at Microsoft – absolute legends, well beyond the call of duty and your dedication is amazing! Jeremy Bersin & Donna Ruscavage & the team from the Boston Public Health Commission for your relentless drive in making it happen. Dave Fourtier – for being #bostonstrong and dedicating you own time and sharing during extremely difficult times in order to help others. Rich Serino – I have only just met you but you made an immediate impression and your an inspiration to many. Thank you for survivor centricity. Tony Surma &  John Farmer from the Microsoft Disaster Response team and Microsoft Civil Engagement for all the great work you do. Jo Dover from the Foundation for piece charity – Thank you for the administration of the 7/7 survivor network and all the good work your organisation does. Tony Moore from the Metropolitan Police – A very special person and a hero to us all. I will never know how we will ever thank you enough for the work that you do. Finally I would like to thank the Microsoft Leadership team and in particularly my manager for giving me everything I ever needed to turn this idea into reality.   Here are some about the day: I arrived at the White House nice and early with my US passport (I am a dual citizen) and unfortunately security had a different spelling for my middle name so I had to wait 45 minutes to get in, for a while there I thought it was over before it began! I’m not sure how much more I am supposed to share about the security so I’ll play it safe! But I will say a highlight for me was using Skype (with video) from inside to call my wife which was pretty cool! The talk itself was actually in the building adjacent to the main White House but you are allowed some scope to walk around the grounds.There were two parts of the day, the first was a number of workshops to discuss/brainstorm possible uses of technology for disaster response where I got to meet some amazing people and here great ideas and then the second was the announcements themselves.   Whitehouse

 Just getting into the announcement, I have never been so nervous! There where 250 people in the auditorium and another 1,200 watching live online.

markanddave

 Dave and I just outside the West Wing and the White House

  selfiewhitehouse

 My first ever selfie, had to really…

BostonPic

If ever a picture told a thousand words this is it. Watch the announcement to find out more. Photo courtesy of http://projects.dearworld.me and is not to be used under any circumstances without mine or Dear World written permission

Project Overview

What is the Yammer network for survivors?

The aim is to provide the capability to provision a secure and private Social Enterprise network for Survivors such that they are able to find information quickly and talk to people who share the same experience and trauma.

Why?

Many governments work with devolved organisations and under a multi-agency framework (emergency services, local government departments, survivors, family members and other organisations) in order to prepare, respond and recover from an emergency. During a large scale event that might occur in multiple locations at different times it is pivotal that these organisations are able to quickly and efficiently communicate with each other. A centralised communication system is needed to facilitate the communication and collaboration between these parties at a time when key information is scarce and confusing.

Benefits

  • Speed up the recovery time of survivors
  • Reduce information overload on survivors
  • Increased the speed of which information is shared amongst the group
  • Increased the likelihood and speed of people returning to work
  • Provides a forum for survivors to self help and support each other
  • Reduce the severity of PTSD
  • Reduce the cost of healthcare for the survivors
  • Provide real-time access to information on all devices

How:

  • People helping each other
  • People receiving help much earlier in the process
  • The various officials have a centralised place to publish information (real-time)
  • Survivors have a single place to access information (as a survivor it is often difficult to know where to seek help from the various agencies)
  • Survivors can collaborate with one another to self-serve for support
  • Information can be obtained immediately

What is Yammer?

Yammer is a secure, private Enterprise Social Network that enables online collaboration and communication with multiple parties and stakeholders. People can ask questions, provide answers, upload documents and participate in real time online conversations. For officials Yammer becomes a centralised environment to disseminate information to affected people and is easily accessible on any web enabled device (smartphone, tablet, etc).

Who would / could use Yammer?

  • Survivors
  • Family Members
  • Central Government
  • Local Government Departments
  • First Responders
  • Emergency Response Teams (Police, Ambulance, Fire, Army)
  • Local, national and global charities
  • Local business offering support and help
  • Local, national and internal media

When would you use Yammer?

A Social Enterprise Crisis Management System could be used in the event of any disaster natural or man main such as:

  • Floods, earthquakes or other natural disasters
  • Famines
  • Nuclear Disasters
  • Disease Outbreaks (flu pandemics)
  • Acts of Terrorism
  • Serious incidents related to organised crime
  • Mass shootings

How would it be Deployed?

Yammer is a cloud service and as such does not require any “installation” time. However there are best practises and guidelines that should be followed. The diagram below is a visual representation of a typical deployment flow.   CommunityProcessFlow   Identify Owner Organisation In the event of a disaster an owner organisation needs to be identified. An organisation such as local government or health service, charity etc. Owner Organisation Assigned Once an organisation has been assigned it is necessary to determine if they already have Yammer. If they do not an alternative organisation may be preferable, otherwise the organisation can quickly register an account. Create External Network An external network is created this is where the various parties related to the disaster will work together. Create Usage Policy Before invites can be sent a usage policy or terms and conditions need to be created to set the terms and expectations of the members in terms of what is allowed and what isn’t. Create Network Structure A series ig groups can/should be created to support the privacy of the members. However in principal you should try to have as few groups as possible and groups should be open (not private) to other members if possible. A obvious exception to this might be police or legal matters or perhaps a family room for family member to discuss things privately. Send Invite Invites should be sent out to individuals to register and agree to the usage policy. The individuals on the invite should be vetted by a police service or similar

Example Case Studies:

London 7/7 Bombings Within days after the London 7.7 bombings an online community was used for survivors to support each other and to help them deal the trauma they were going through. The London 7/7 community site was used by survivors, family members, tube drivers, police and other people effected by the bombings. The London 7/7 site is still in use today. Boston Marathon Bombings The Boston marathon survivors have used Yammer network in much the same ways as the survivors of London 7/7.  Some of the injured recently used the group to organise running the marathon during the 1st anniversary. I will post further examples as soon as I have received permission to do so –  there are many. There are many other examples related to natural disasters, nuclear disasters and other cases. Please contact me if you have an urgent need for further information.   This post was originally published on https://markmargolis.wordpress.com. This posting is provided “AS IS” with no warranties, and confers no rights.

Now Available On Premises: FinDemo A Core Financial Services Demo Pack

WPC starts this week and to start the week on a high I have decided to publish my core financial services demo pack as a standalone install for on premises scenarios. I strongly advise that you continue to use DemoBuilder to provision the template as this comes preconfigured and will save you some time. For those times that you need it on premises enjoy. My only ask is constructive feedback on how this can be improved and any stories you have on how these have been used to help your clients would be much appreciated. Either via the comments on here on DM me via my twitter account.  BranchMarketingAnalytics The demo toolkit includes:

  • My core Financial services data model (Corporate, Investment, Retail Banking, Asset Management and more), forms, reports, dashboards, business process etc (with thanks to the team for their collaboration)
  • Paul Mare’s amazing Client 360 component configures for Financial Services scenarios
  • XRM Consultancy’s Timeline Component
  • North 52’s Formula Manager / Process Genie

To download the solution files, instructions and demo data visit the  solutions page here. This is a demonstration tool kit and is not recommended for production purposes. This post was originally published on https://markmargolis.wordpress.com. This posting is provided “AS IS” with no warranties, and confers no rights.

Client 360 – Single View Component for Microsoft CRM

I have written about the Client 360 component before. This solution was built by one of my colleagues Paul Mare so all credit goes to him!

Those of you familiar with the existing Financial Services templates will recognise this component already as I embeded it into FinDemo.

We are now making these solutions available as separate install files files. This solution comes pre configures on the Financial Services templates on demobuilder. http://demobuilder.cloudapp.net/

Introduction

The Client360 Single View Configurator is a demo asset that allows pre-sales people to establish a rich user experience inside a standard CRM Form, without requiring any JavaScript, HTML 5 or CSS coding. This is made available to be freely used or modified by anybody, at their own risk. Specifically note that this is a demo asset and not suited for production.
It is typically used to add the following items to a CRM Account or Contact Form:

  • • A tile-based display of related records like Opportunities or Cases
  • • A tile-based display of the customer’s portfolio of business, like Fund Holdings, Product Holdings, Bank Accounts, Installed Base or Projects
  • • Guidance / Best Next Actions – a list of recommended Best Next Actions and contextual guidance for the user
  • • Quick Buttons – touch friendly buttons that can be quickly configured to perform related actions

An example of such a customized form could be:

sv1

Note the following elements on this sample:
1. Three horizontal tabs, each indicated by a heading followed by a record count. A quick glance shows that apart from the 5 Opportunities, there are 6 Cases logged and Contoso Inc has 3 Subsidiaries.
2. The Guidance: Best Next Actions area shows up to 7 messages for the User.
3. The Quick Buttons area with up to 4 buttons that will perform related actions from this Company record.
Note that each tile has the following information components:

  • • An Icon, in this case based on the Probability of the Opportunity.
  • • A Color, in this case determined by the Status Reason of the Opportunity.
  • • Three Zones with information next to the icon (referred to as Zone 1, Zone 2 and Zone 3), in this case showing the Opportunity Estimated Value, Estimated Close Date and Status Reason.
  • • A Title area, in this case showing the Name of the Opportunity.

To accomplish this, do the following, assuming that the Client360 Single View solutions have been installed already:

  • • Edit the Form for the Account or Contact record where the rich user experience is needed.
  • • Add the ms_SingleViewDisplay.html web resource to the form. Save and publish your customisations.
  • • Edit the Single View Settings record for the Account or Contact form. Configure the Tile-based display, Quick Buttons and Guidance / Best Next Actions settings. Save and test by opening the Form for an Account or Contact entity.

An example of the settings used to define the tile layout for Opportunities (as shown on the previous page):

sv2

Installing Client360 Solutions

Import the latest versions of the managed solutions for:
Client360 Single View Configurator –
Client360 Single View Icon Library –

** Update** For the latest Client360 files please download the 4 Client360 files from the primary FinDemo page.

If it is the very first time you are installing the solution, also do the following:

• Visit the Configuration page for the Client360 Single View Icon Library to see the available Icons.
• Visit the Configuration Page for the Client360 Single View Configurator to see breaking documentation, and more importantly, to create default Single View Settings records to get you started easily.

Adding Client360 to a Form

  1. Create or edit a form (via Solutions or Customisations)
  2. Insert Web Resource: ms_SingleViewDisplay.html
    1. Custom Parameter: name of the Singleview Setting (under General, see above)
    2. Formatting: One column
    3. Number of rows 18
    4. Scrolling: Never
    5. Display border: no

Tab Definition

Complete the relevant fields below for each of the 4 horizontal tabs to define the tab content and layout:

  • Name: The heading to be displayed for this tab.
  • Content: Select Tiles for a tile-based user experience, CRM Web Resource to display a custom web resource like an image or html file, or Not Used if the tab should not be rendered. The current version does not yet support CRM Charts.
  • Name: The heading to be displayed for this tab.
  • Content: Select Tiles for a tile-based user experience, CRM Web Resource to display a custom web resource like an image or html file, or Not Used if the tab should not be rendered. The current version does not yet support CRM Charts
  • Tile Layout: Select Small or Medium to determine the Tile size. The values Large, Case Process and Opportunity Process are not yet implemented.
  • URL: The relative URL of the web resource to display (only relevant if Content set to Web Resource.
  • Entity: The name for the Entity to be rendered in the tab, using the ODATA format, e.g. OpportunitySet or new_customentitySet, case-sensitive!

Tile Definition

To define the records that will be rendered on the tiles, enter the following information:

  • Primary Key: The field containing the Guid for the Entity above, listed in the CRM field list with the data type Primary Key, e.g. OpportunityId.
  • Foreign Key: The field on this Entity containing the relationship back to the entity on which the Single View will be rendered (typically the Account or Contact record), e.g. ParentContactId.
  • Filter: Select whether to include all Child Records or Active Child Records; for advanced scenarios select Child Records + Custom Filter, Active Child Records + Custom Filter or Custom Filter Only. Use in conjunction with the Custom Filter field below.
  • Custom Filter: ODATA filter expression for this entity, e.g. StateCode/Value eq 0 or startswith(Name,”W”)
  • Zone1-3,Title: The name for the field on the Entity to be rendered on the Tile, using the ODATA format, e.g. CloseProbability or new_MyField, case sensitive! The correct spelling is displayed in the second column (Schema Name) when looking at the field list for the Entity in a solution.
  • Zone1-3,Title Formatters: Specifies how the raw data returned from the ODATA service should be processed before display on the Tiles. Use None for simple text fields. Match Currency,Date and Option Set field types. Use Custom Javascript Function to format the fields using your own Javascript handler.
  • Additional Fields: Fields to be retrieved and made available to Custom Javascript handlers.

Guidance / Bext Next Actions

Enter the text to display on the Single View form. Use replacement values
for dynamic content, e.g.:

» &Cnt1: Count of the number of records in horizontal tab 1

» &Cnt2: Count of the number of records in horizontal tab 2

» &Cnt3: Count of the number of records in horizontal tab 3

» &Cnt4: Count of the number of records in horizontal tab 4

» &RandomWord1: Random phrase from Random List 1

» &RandomWord2: Random phrase from Random List 2

Quick Buttons

For each Quick Button, enter the following information:

»Name: The name to be displayed on the form

»Action: What should happen when the button is clicked or touched

»Entity: The entity on which the button action will be performed

»Foreign Key: The Odata name for the field pointing to the current entity

»Primary Key: The Odata field name for the field containg the primary key (record Guid)

Setting Color With A Custom Function

When selecting Custom JavaScript Function as the Color source, you need to implement a Javascript function on the form that returns the CSS color name or color value. It must have the name and calling interface as per the example below:

function determineCustomColor(record, entityLogicalName) {        // Return green for Open opportunities, gray for Won or Lost        if (entityLogicalName == “opportunity”) {            return (record.StatusCode.Value == 0) ? “DarkGreen” : “#777777”;        }    }

The input parameter record is a Javascript object. Each of the fields retrieved according to the tab’s tile definition is a property of this object, e.g. record.Name, record.CloseProbability or records.StatusCode. Option Sets, Currency Fields and Lookup fields are objects in their own right, use notation like record.ParentContactId.Name or record.StatusCode.Value.

The input parameter entityLogicalName is a string containing the logical name for the entity, e.g. opportunity or incident.

Setting The Icon With A Custom Function

When selecting Custom JavaScript Function as the Icon source, you need to implement a Javascript function on the form that returns the Icon name. It must have the name and calling interface as per the example below:

function determineCustomIcon(record, entityLogicalName) {        // Return a flag icon based on Address 1 Country        if (entityLogicalName == “account”) {            switch (record.Address1_Country) {               case “United States:               case “United States”: return “Flags/” + “UnitedStates.png”;               case “United Kingdom”: return “Flags/” + “UnitedKingdom.png”;               case “Germany”: return “Flags/” + “Germany.png”;               default: return “Temp.png”;            }        }    }

The input parameters are the same as for the determineCustomColor function on the left.

Using A Custom Javascript Formatter

When selecting Custom JavaScript Function as the Formatter, you need to implement a Javascript function on the form that returns the text to be rendered on the tile. It must have the name and calling interface as per the example below:

function determineCustomFormat(record, entityLogicalName, field) {        // Analyse record and return text to display on tile        if (entityLogicalName == “opportunity” && field = “StatusCode”) {            return (record.StatusCode.Value == 0) ? “Active” : “Inactive”;        }    }

The input parameter record is a Javascript object. Each of the fields retrieved according to the tab’s tile definition is a property of this object, e.g. record.Name, record.CloseProbability or records.StatusCode. Option Sets, Currency Fields and Lookup fields are objects in their own right, use notation like record.ParentContactId.Name or record.StatusCode.Value.

The input parameter entityLogicalName is a string containing the logical name for the entity, e.g. opportunity or incident.

The input parameter field is a string containing the name of the field being formatted, e.g. StatusCode or Name.

EXAMPLE

The sample below introduces line breaks into Product Names for the “fin_policy” entity, and for the “fin_claim” entity shows the product name followed by two line breaks and then the status description in curly brackets:

function determineCustomFormat(record, entityLogicalName, field) {    // alert(entityLogicalName + “/” + field + “: ” + record[field]);    switch (entityLogicalName + “/” + field) {      case “fin_policy/fin_ProductId”: {        var t = record.fin_ProductId.Name           + “<br /><br />{” + record.fin_BrokerId.Name + “}”;        t = t.replace(“Scooter Insurance”, “Scooter<br />Insurance”);         t = t.replace(“Pension Saver”, “Pension<:br />Saver”);         t = t.replace(“Van Insurance”, “Van<br />Insurance”);        return t;      }      case “fin_claim/fin_ClaimStatus”: {         var t = “Logged”;         switch (record[field].Value) {             case 914950000: t = “In Progress”; break;             case 914950001: t = “Partially Accepted”; break;             case 914950002: t = “Fully Accepted”; break;             case 914950003: t = “Rejected”; break;         }         return record.fin_ProductId.Name + “<br /><br />{” + t + “}”;      }      default:         return record[field];    } // switch }

The input parameters are the same as for the determineCustomColor function on the left.

This post was originally published on https://markmargolis.wordpress.com.

This posting is provided “AS IS” with no warranties, and confers no rights.

Spring Wave: SharePoint, Outlook, Tablets, USD, SDK, CRM Online. Deconstructed

My last article “Microsoft CRM 2013 Spring Wave (SP1) Deconstructed”  focussed on the new application features of CRM, this time I am going to cover the following:

  • SharePoint
  • Microsoft Office Outlook
  • CRM for Tablets
  • Unified Service Desk (USD)
  • SDK
  • CRM Online

 

SharePoint

This release brings enhancements for organisation using CRM Online and SharePoint on-line by providing server side integration and authentication with SharePoint Online. Please note that for the following scenarios  you will need to continue using the List Component:

  • hybrid configuration, e.g. CRM Online, SharePoint On Premises
  • Not on office 365 e..g you are using Microsoft  liveid)
  • Different office 365 tennants

If you are running a configuration that supports the sever side integration then it is really easy to enable SharePoint. In CRM head over to Settings > Document Management > Enable Server Based SharePoint Integration and follow the online steps.

SharePoint_Integration

 

 Microsoft Office Outlook

The Outlook client has been updates to allow for the new application features and forms (e.g. SLA etc) discussed in my last post. Note the compatibility matrix below:

Outlook_Server_Compatability

 

Outlook_Server_Compatability_offline

 

Microsoft CRM for Tablets:

In this update we have added:

  • Support for Android
  • A specific Windows 8.1 App (there are now 2 apps in the store if you are running 8.1) – Offline caching for on premises deployments, resize to 500px window for split screen
  • Ability to reconfigure and or sign in  without uninstall /  reinstall
  • Added additional entity support (e.g. Cases, Queues, Entitlements , Social Activity, Social Profiles etc)
  • Additional Security configurations (URI’s for On Premises configurations)

Unified Service Desk (USD)

USD provides a configurable framework for quickly building call center applications that provides “unified” access to customer information in Microsoft Dynamics CRM and can be extended to access information in other Line of Business (LOB) applications.

  • Easily handle simultaneous interactions through voice, chat and email
  • Increase effectiveness using guided scripts and in-context application automation
  • Easy to configure and designed to integrate legacy applications
  • Reduce process complexity for end users

USD

 

You can read a lot more on this on the MSDN network here.

SDK

For the full details on what is included in the latest SDK visit the developer centre here: http://msdn.microsoft.com/en-us/dynamics/crm/dn467921.aspx or take a look on MSDN here: http://msdn.microsoft.com/en-us/library/gg309589(v=crm.6).aspx

CRM Online New Features

  • Sandbox Instances (free test instances for orgs with over 25 professional users)
  • Reset sandbox instances (deletes a sandbox instance and provisions a new one)
  • Administration Mode for Sandboxes (disables access for non admins, disable background operations, custom messages for end users)
  • Copy instances (Full or Minimal Copy). E.g. you can copy your production instance to easily create a UAT or training environment

 

This post was originally published on https://markmargolis.wordpress.com. This posting is provided “AS IS” with no warranties, and confers no rights.

 

Microsoft CRM 2013 Spring Wave (SP1) Deconstructed

The latest version of Microsoft Dynamics CRM 2013 is now available online and on premises (SP1). Below is a summary of some of the primary features included. Please be aware that some of the functionality provided in this latest release is available in previous versions (case routing via workflow for example). With this release we are able to achieve the same business functionality in a way that is much easier to configure further driving down the cost of your CRM implementation and increases the flexibility for non technical users.

CRM online updates will be auto applied but you still need to enable the features. On premises users will need to install SP1. You can check what version you are running by going to the about page in the browser (look for 6.1 to confirm that you have been upgraded).

To enable the new features:

Goto Settings > Administration >  Install Product Updates

On this page you will find links to additional resources (whats new) on the Customer centre such as : http://www.microsoft.com/en-us/dynamics/crm-customer-center/what-s-new.aspx

In this article I am going to focus on the main application features. Other enhancements that I will go into more detail another time include:

  • SharePoint
  • Microsoft Office Outlook
  • CRM for Tablets
  • Unified Service Desk
  • SDK
  • CRM Online

I’ll post details of the enhancements in the above list next time.

So right now I am going to focus on the following Feature Enhancements:

  • Case & Service Management
  • Queue Enhancements and routing
  • Automatic Case Creation
  • Social Profiles & Activities
  • Status Reason Transitions
  • Solutions
  • Other small changes

 

One of the main areas added is the service  management area:

servicemanagement

Case and Service Management

Main changes include a new entity called “social profiles” and modification to entities to Account, Contact, Case, Queues & User.

Your custom forms will not be effected. We only modify the forms with the same name of the entity, For example on the Case entity the “Case” form will be modified. Changes include:

  • Link to Entitlement
  • Associated Entitlements
  • Applicable SLA’s
  • Case Relationships (merged and child cases)
  • Additional detailed (escalated, sla’s etc
  • Social Details
  • Article sand Contract Information
  • New commands include apply routing rule, create child case etc
  • Quick Create for Case

 

On the Account and Contact form changes include:

  • Active entitlements on the form
  • Social Profiles relationship
  • Entitlements relationship

On the User entity changes include:

  • Queues I am a member of subgrid

Case Hierarchy (Parent / Child Cases)

You can now natively create parent / child cases and the behaviour of what happens can be configured (configurable cascading, close rules and inheritance options).

Associate and Merge Cases

You can now bulk associate cases and you can also merge cases (similar to the way we would merge account and contact).

Entitlements

Entitlement is a new and allows you to specify the type of service a customer receives.

Entitlements

 

 

 

As you can see above you can specify and restrict a service based on Primary customer, SLA, Terms, Type, Channels, Products and Contacts. You can create entitlement based on a template.

Service Level Agreements (SLA)

SLAExample

The SLA determines the service levels and actions that you want to apply, such as what happens when response times and resolution times are  not met.

Timer Control

It is now possible to place a timer control on forms to make take resolution times and SLA conditions more visible to end users.

Queues and Routing Rules

Private queues are now available to reduce the complexity and number of queues in the system. Users can create queues that are only visible to certain people (members). A number of other usability enhancements have been included such as additional fields and information on views and filters on lookups and commands to enable end users to more easily work with queues.

Routing Rules

Allows users to set up conditions in order to automatically route cases depending on the met criteria (e.g. high priority cases).

Automatic Case Creation

Enables users to automatically create cases from emails (or social channels). It is simple as enabling the queue and choosing a few case creation rules.

caserules

Social Profiles

Allows you associate profiles, channels and posts to records in CRM via the API. Look into the SDK for more information.

Status Reason Transitions

Enables users to more easily manage and configures the status’s of a record(s) status. For example you can use this to determine what status values might be available to a particular user at any moment. For example when a record is in the in-progress state you might only want certain options to be available (e.g. closed or on hold)

statusreason

Solution and Software Lifecycle Management – Target a CRM Version

This feature enables you export a solution to target a specific version of Microsoft CRM.

solutionversion

 

Other Enhancements

  • We have expanded the command bar options from 5 to 7
  • Ability to group conditions in workflow (AND/OR)
  • Duplicate detection is back available on the entity forms/in-line and includes autosave
  • Lync Presence available on lookup fields and activity feeds

This post was originally published on https://markmargolis.wordpress.com. This posting is provided “AS IS” with no warranties, and confers no rights.

Microsoft CRM & Microsoft ERP Event List

We run a lot of events at Microsoft and so do our partners. However it is rare that everyone knows about all the different events so I though I would start publishing a page of all the upcoming events. The criteria for for an event on my blog will be:

  • The event Topic must involve Microsoft CRM or  Microsoft ERP or another Microsoft application related to the management of client information
  • The event does not need to need be organised by Microsoft. In fact partner or User Group events are encouraged
  • I will only include major global events or events based in the UK (for now)

 

If you would like an event listed here then please contact me via   Twitter Twitter or LinkedIn LinkedIn.

 

This post was originally published on https://markmargolis.wordpress.com. This posting is provided “AS IS” with no warranties, and confers no rights.

Financial Services Demo (FinDemo) Update – Coming Soon

As I promised last time the core Financial Services demo (aka FinDemo) is being updated and along with the Retail Banking demo should be live in the next few weeks. All the changes I described on the Retail Banking demo will in included in the update below.

In summary changes include:

  • Much cleaner sitemap layout: Corporate Banking, Retail Banking, Commercial Banking, Asset Management, Wealth Management & Insurance
  • Business Configuration: Include reference entities
  • Client 360 has received some major enhancement including drag and drop configuration and active buttons that can be configured
  • The Insurance part of the demo has been cleaned up, particularly Policies and Entities
  • All Retail Banking enhancements are included. See here.
  • Simpler Onboarding process and addtitional business processes incldued

 

Slide2

Slide3

Slide4

Slide6

Slide7

Slide8

Slide9

Slide10

Slide11

Slide12

Slide13

Slide14

Slide15

Slide16

Slide17

Slide18

Slide19