In CRM 2011, all DocumentsCorePack templates are stored in custom entities. The name of this custom entity is DocumentsCorePack Template (ptm_mscrmaddons_dcptemplates).Every record of this entity has the template attached as a note.
Per default, CRM metadata information for DocumenstCorePack is stored here:
Sometimes, you may be asked to create a new settingskey for one of our products. This article outlines how to do so.
This blog article will walk you through the required steps on how to install GroupCalendar and ActivityTools in a claims-based environment.
This article is valid for GroupCalendar for CRM 2011, 2013, 2015 and 2016 but only for CRM 2013 and older versions of ActivityTools. From CRM 2015 onwards ActivityTools does not have to be configured for IFD anymore!
The steps are the same for both products, so instead of an explicit product name, we will use the term the addon in this guide.
CTI 2011 TAPI wrapper needs a TAPI driver that is suitable to your Phone PBX server.
Each PBX phone-system vendor has its own TAPI driver.
Our TAPI wrapper has not an active role on the TAPI lines, it is just a passive listener to random TAPI driver events and eventually, it triggers them in case of outgoing calls, accepting the incoming offers.
If you outgoing calls are successful when made from CTI client, but not from the CRM entity, simply check the Internet Explorer Security Options. Please make sure that your CRM Server is included in the Trusted Sites Zone.
Before an entity or PhoneCall activity can be opened by an incoming/outgoing phone call, the phonenumber must be resolved.
The CTI supports only one call at the moment.
However, when transferring existing calls to a third party, it can happen that some sessions are not correctly closed. You can compare that with a broken Lync conversation.
The fields.xml Settings are server-side CRM Settings.