Visual Mapping

CRM Integration Field Mapping (aka Visual Mapping) enables an easy setup of CRM to Pricefx field mapping in front-end integration between supported CRM applications and supported Pricefx documents, without the need to write an Interceptor.

The Field Mapping is triggered before the Dynamic Interceptors functionality. So Interceptors can overwrite or modify the values from Field Mapping.

Supported CRMs: In version 11.0, only Salesforce, MS Dynamics and SugarCRM are supported.

The supported documents: Quotes, Rebate Agreements, Agreements & Promotions and Compensation Plans.

Limitations:

• Values from Configurators, Line Item inputs and structured objects are not supported in Visual Mapping. They can be, however, set by Interceptors.

• Pricefx inputs are filtered not to display complex objects and some inputs which are not possible to use for mapping such as: calculationStatus, dirty, refreshInputs, numberOfAttachments, etc.

• There is no logic or conversion behind the mapping, so caution is needed when you do the mapping. Be aware of the type of the Pricefx input you are trying to prefill with some value.

Configuration

The Field Mapping configuration can be found in Administration > Configuration > CRM Integration. To be able to access this section, you need the Develop Interceptors user role.

The setting is saved in the Advanced Configuration Options as visualMappingConfig. This configuration is checked every time when a CLIC object is created.

We recommend to open this configuration page inside of the iFrame integrated in a CRM application on the Opportunity or Account page. This allows you to see the actual content of the payload with values coming from the CRM site.

Open

Steps to Configure

1. Select PFX Object for mapping (marked “2” in the image above). You have to set up:

   • Object Name – One of the supported CLIC objects.

   • Object Type – There can be different types with different logics inside – this will load different Pricefx inputs in the next step.

   • CRM Module – You can choose between the Opportunity and Account modules where mapping will take affect.

2. For different Pricefx Objects you will see different Mapping between CRM and PFX (marked “3”) sections. In this step you will add the mapping which will be performed between CRM Value (a list of values coming from CRM) and PFX Input fields (a list of inputs on the Pricefx side).

   1. The Add Mapping dialog has the autocomplete feature, which can help you to select the proper field from CRM.

      Open

      

      Example of autocompletion of CRM field in Add Mapping dialog

   2. Instead of a value coming from CRM, you can define a static value.

   3. If you need to modify the values coming from CRM, you can define the modification in JavaScript in the Transformation field. Examples:
      const newStr = 'Id ${value} CRM'; return newStr;

      return value.toUpperCase()

3. To finish, click Save Changes (marked “4”). If there are any unsaved changes, you will see a warning on the top of the page.

Temporary Visual Mapping

It is possible to use the Field Mapping configuration only in the current browser session. In that case, the configuration is in a different file and it will not affect other users on the same Pricefx partition.

This functionality is enabled by default. You can enable/disable it by checking/unchecking the Set Visual Mapping as temporary option and clicking Save Changes.

Example of Field Mapping in Salesforce

1. Open Visual Mapping in iFrame on the Opportunity page and prepare mapping for label and External Reference. Make sure you save the changes.

2. Open Visual Mapping in iFrame on the Account page and prepare mapping for Customer Group.

3. Test your mapping by creating a new Rebate Agreement, type Default on the Opportunity page.

4. Test your mapping by creating a new Rebate Agreement, type Default on the Account page: