Declarative Configuration Guide (FDM)

APPLIES TO | CUNEIFORM FOR CRM FIELD AND DATA MANAGEMENT

Once installed, Cuneiform for CRM: Field and Data Management requires little manual configuration from Admins to enable profiling against your org’s Salesforce objects. Admins must complete these four configuration activities before profiling features are enabled in your Salesforce org.

The activities listed below are separated into multiple, easily digestible sections. We recommend completing these activities in order – and have included visual point-and-click walkthroughs to make this as simple as possible.

Declarative Configuration Guide

Complete the activities outlined in the following four (4) steps to finish your Cuneiform for CRM: Field and Data Management configuration. Once you’ve completed the configuration, you can verify it using the Cuneiform for CRM: Control Panel.

Create a
Self -Signed Certificate

Create a Self-Signed Certificate for our Connected App
FIVE MINUTEs

The APIs Cuneiform for CRM leverages (including Metadata, Tooling, and Query APIs) must be accessed securely. We use a self-signed certificate to accomplish this in alignment with Salesforce security recommendations and best practices.

You’ll create a self-signed certificate and download it – so you can use it to create the Connected App we’ll use to broker the Salesforce API requests performeding during Salesforce Object and field profiling.

Create the Application Permission Sets

Create the Administrative Permission Sets for Application Access
TEN MINUTEs

Cuneiform for CRM provides Salesforce Admins with a permission set template supporting admin application access. As a first configuration step, you’ll create a permission set and permission set group to manage associations to our Admin and Connected App assignment permission sets together.

You'll create a Cuneiform for CRM: Administrators permission-set group, and associate our Cuneiform for CRM: Administrative User and Cuneiform for CRM: Connected App Assignment permission-sets to this group. Use the Cuneiform for CRM: Administrators permission-set group to provide profiling access to the users in your Salesforce org.

Create the Application Connected App

Create the Connected App to Securely Access Salesforce APIs
TEN MINUTEs

Cuneiform for CRM leverages a connected app to securely profile Salesforce orgs. Salesforce org Admins must create the connected app – as independent software vendors (ISVs) cannot package this feature. In this section, you’ll create the connected app, configure its OAuth policies, and configure which profiles and permission sets can access it.

You’ll create a Connected App following our guidance – and apply the self-signed certificate to it. You’ll also associate the Connected App to the Cuneiform for CRM: Connected App Assignment permission-set created in the previous step.

Update the Application Configuration Profile

Update the Cuneiform for CRM Active Configuration Profile
FIVE MINUTEs

The configuration profile provides Salesforce Admins with a secure way to customize the configuration of Cuneiform for CRM. These properties are only available via Salesforce Setup and aren’t exposed to end-users as part of the application experience. In this section, you’ll retrieve and apply the necessary properties to update the Cuneiform for CRM configuration profile.

You’ll take the API Name of the self-signed certificate, the label of the Connected App, and the Consumer Key of the Connected App – and apply them to Cuneiform for CRM’s configuration profile. With this step complete – you can verify your installation via the Control Panel.