Pre-built Connectors

Pre-built connectors allow you to integrate your business systems with Sentinel EMS directly from the business system user interface (UI). These connectors function as add-ons, eliminating the need to learn about APIs or write code, and instantly creating integration flows.

The following connectors are supported in Sentinel Connect:

>Salesforce

>Zuora

>SAP

>MS Dynamics

>Oracle

Contact your Thales sales representative if you do not see the connector you are looking for.

This topic primarily focuses on the Salesforce connector, detailing its user-level settings and field mappings. For information on configuring our range of ready-to-use connectors, and mapping configurations related specifically to SAP and Zuora connectors, please see the Configuring Pre-built Connectors page.

NOTE   Thales supports configuring mappings directly in the Sentinel Connect app for the out-of-the-box connectors for MS Dynamics and Salesforce. Mapping configurations for SAP and Zuora are managed in the Sentinel Connect.

Each pre-built connector has its own login and configuration requirements, with settings unique to the business system (ERP/CRM) with which it is integrated. The next section discusses these settings specifically in Salesforce. Contact Thales Customer Support for assistance with pre-built connector configuration settings.

Sentinel User Setting in Salesforce

Sentinel User Setting

The Sentinel User Setting tab contains user-level configurations that users must set to trigger and access the connector functionality from Salesforce. These settings are the global settings that govern the order and quote processing from the Salesforce connector to Sentinel Connect.

>Enable Order Sync: Allows automatic synchronization of all order updates between Salesforce and Sentinel Connect, ensuring order data stays updated across systems. This checkbox is cleared by default, so order data is not pushed from Salesforce to Sentinel Connect unless selected.

>Enable Quote Sync: Allows automatic synchronization of all quote updates between Salesforce and Sentinel Connect, ensuring quote data stays updated across systems. This checkbox is cleared by default, so quote data is not pushed from Salesforce to Sentinel Connect unless selected.

>Only process Thales-enabled products: Ensures that Sentinel Connect processes only those products that have the Thales checkbox enabled in Salesforce. The 'Only process Thales-enabled products' checkbox does not apply to quotes.

The Thales checkbox, shown in the following screenshot, appears when you add a new product in Salesforce.
Thales Setting while Adding New Product

The Thales checkbox, shown in the following screenshot, appears when you edit an existing product in Salesforce.

Thales Setting while Editing a Product

If a product already exists in Sentinel EMS, select Thales checkbox to enable automatic entitlement creation through Sentinel Connect. Products without the Thales checkbox enabled are skipped during processing. Selecting this option has the following advantages:

Avoid 400 errors

Reduce dashboard noise

Reduce transaction noise

Improve debugging experience

When 'Only process Thales-enabled products' checkbox is selected and the order does not contain any Thales-enabled products, a user can see the warning message in Salesforce Order details "Order Skipped: Orders without Thales-enabled products are excluded from the Sentinel Connect submission" and the transaction is not logged.

NOTE   By default, Only process Thales-enabled products checkbox is selected when Sentinel Connect version 2.7 is installed in the Salesforce instance. In the case of an upgrade from a previous version, this option is cleared.

Clear the 'Only process Thales-enabled products' checkbox to allow Sentinel Connect to process all products, regardless of whether the Thales checkbox is enabled. This may result in processing errors for products without the Thales checkbox enabled.

>Timeout (in ms): Specify the duration, in milliseconds, that the system waits after triggering a Sentinel Connect request before timing out. When a Sentinel Connect request is initiated from this point, the system waits for a response up to the specified timeout value.

NOTE   Set the timeout to '60000' ms or higher to allow sufficient time for the system to receive a response.

>Add Fields To Layout: The Add Fields To Layout button helps administrators automatically add Sentinel Connect-required custom fields to selected Salesforce object page layouts, without manually editing layouts in Salesforce Setup. This ensures that all required Sentinel Connect fields are consistently available on relevant Salesforce objects used by the connector.

When you select Add Fields To Layout, a modal window opens that allows users to select page layouts. The dropdown lists all available layouts (both standard and custom) for the selected Salesforce object, allowing administrators to choose the exact layout to which the fields should be added. Each layout option corresponds to a specific Salesforce object. Selecting a layout adds Sentinel Connect–related fields to that object’s page layout under a dedicated Sentinel Information section. Users can select one or more layouts and click Add to apply the changes.

Page Layouts in Salesforce

Following are the layout options and the fields added in each layout:

Order Layout:: Adds the following fields to the Order object layout:

EID

Last Sync

Sync Error

Warning

These fields are used to track synchronization status, errors, and warnings related to order processing.

Quote Layout: Adds the following fields to the Quote object layout:

EID

Last Sync

Sync Error

Warning

These fields provide visibility into quote-level synchronization and processing status.

Product Layout: Adds the following field to the Product object layout:

Thales

This field identifies products that are eligible for Sentinel processing.

OrderItem Layout: Adds the following field to the OrderItem (Order Product) object layout:

PKID

This field captures product-level identification from processed order.

Validation and user feedback

The system provides the following validation messages and user feedback during layout selection and updates:

>If no layout is selected, the system displays a warning: “Please select a layout.”

Warning if no layput is selected

>If selected fields already exist on the layout, the user is informed, and no duplicate fields are added.

Page Layout Fields Message when the fields already exist

>Any errors during layout updates (for example, permission-related issues) are displayed as clear error messages.

Setup

The Setup tab performs a one-time configuration required to enable Sentinel Connect functionality on Salesforce Quotes. Once completed, the setup cannot be re-run.

Setup Tab when record is created successfully in Salesforce

Executing setup ensures that all required quote-related components are created upfront, allowing Sentinel Connect to work seamlessly with Salesforce Quotes while minimizing manual configuration. Executing setup performs the following configurations:

>Adds required Sentinel Connect configuration fields — EID, Last Sync, Sync Error, and Warning — to the Quote object.

>Adds required automation triggers to the Quote object to support quote processing.

>Creates and prepares the custom object Quote_JSON__c in the instance, which tracks processed Quote records.

Setup Tab when already executed in Salesforce

Additional notes on Setup

>Setup runs only when Salesforce Quotes are enabled in the Salesforce. When Salesforce Quotes are not enabled, setup is skipped and quote-related configuration is not applied.

>Setup applies only to Non-CPQ managed packages. Salesforce CPQ instances do not support this setup process.

Field Mapping Framework

The Field Mapping Framework facilitates the transformation and transfer of data from a business system (source) to Sentinel EMS (target). This framework allows administrators to define exactly how transactional data (such as Orders, Line Items, Customers, Partners, and Contacts) is interpreted by Sentinel EMS.

Field Mapper Interface

The field mappers within the connectors are a set of UI forms that enable you to easily bind data from your business system to a specific field in Sentinel EMS, and vice versa.

Accessing the Field Mapper

The entry point to the mapping screen varies depending on the connected business system:

Connector

Access Path

Salesforce

Salesforce > Open App Launcher > Sentinel Connect > Order Field Mapper or Quote Field Mapper

SAP

Sign in to Sentinel Connect as a Customer Admin* > Client Management > Order Configuration or Quote Configuration

Zuora

Sign in to Sentinel Connect as a Customer Admin* > Client Management > Order Configuration

Microsoft Dynamics

MS Dynamics 365 > Sentinel Connect > Order Field Mapper

*See Configuring User Accounts for more information on user roles and permissions.

Mapping Screen Components

The Field Mapping screen is divided into two distinct panels:

>Left Panel (the Source Field from Business System): Displays ERP-specific fields, which are the data points available from the upstream object (for example, Source Order Number, Source Customer ID).

>Right Panel (the Target Field from Sentinel EMS): Displays Sentinel EMS attributes or data fields, which are the destination fields within Sentinel EMS.

Order Field Mapper: Supported Entities and Field Mappings

Mappings can be defined for following key business entities:

>Entitlement

>Entitlement Line Item or Product

>Customer

>Users

>Channel Partner

The Order Field Mapper is a user interface within the business system (for example, Salesforce) that enables flexible and precise data mapping between Salesforce and Sentinel EMS attributes for orders.

Attribute Types

Target attributes in Sentinel EMS are categorized into two types:

>Standard Attributes: Standard Attributes are available by default in the right-side panel and represent core system data (e.g., Entitlement ID, Start Date, Product Name).

>Custom Attributes: Custom Attributes are user-defined attributes required when the business system contains data that does not map to a Standard Attribute. Custom attributes that exist in Sentinel EMS are not available by default on the Field Mapper screen. To enable mapping, the business system administrator or Sentinel Connect Customer Administrator must add these attributes by clicking the “+” icon in the Custom Attribute Section of the relevant Entity Tab and entering the name of the custom attribute to be mapped in the target system. Field names may vary as they are defined according to the customer-specific data model in Sentinel EMS.

NOTE   When creating a new attribute in the source business system, ensure that you use a unique and descriptive name (e.g., Order_Type__c) to prevent conflicts with existing ERP field names. This practice helps maintain data integrity and ensures smooth integration between ERP and Sentinel EMS.

Configure Field Mappings

Installation of the Sentinel Connect package into business systems creates default mappings for each object type (e.g., Entitlement, Product). If no mapping is defined, the user can click the “+” sign in the mapping row to define one.

The following tables describe the supported entities and demonstrate how Sentinel Connect configuration works within the Salesforce application.

Source fields (from Salesforce) are not prescribed in this table due to the variation in business requirements, data models, and source fields across different business systems. The business system administrator should select the fields that best align with their own system configuration and business processes.

>Entitlement: This tab controls the core entitlement data, allowing you to transfer order details from Salesforce to Sentinel EMS fields.

NOTE   Specific custom attributes are required to handle renewal or continuous order logic.

ClosedEntitlement Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Optional EID Unique entitlement identifier. Auto-generated if omitted.
+ Optional startDate Start date of the entitlement.
+ Optional endDate End/expiration date of the entitlement.
+ Optional externalId External reference linking entitlement to the originating system.
+ Required status

Status of an entitlement:

>Draft

>Enabled

>Disabled

>Closed

+ Optional userRegistration Indicates if end‑user registration is required.
+ Optional sendNotification Send notification email after creation.
+ Optional activationAllowed Allows immediate entitlement activation.
+ Optional revocationAllowed Allows entitlement revocation.
+ Optional ccEmail Additional email addresses for notifications.
Entitlement Custom Attributes
+ Optional Order Type Determines the type of order. Any value other than 'Initial Order' indicates Add-on or Subsequent order. Create a custom text field in ERP Order object with a unique name (e.g., Order_Type__c) to avoid conflicts with ERP field names.
+ Optional Previous Entitlement ID Stores previous Entitlement IDs for upgrade or renewal scenarios. Implement as a custom text or lookup field in Salesforce. Ensure proper data mapping and validation during integration.
+ Optional Key ID Captures previously activated Key ID for continuity and compliance. Create as a custom text or lookup field. Apply field-level security and include in page layouts for visibility.

>Entitlement Line Item or Product: This tab maps the specific products within an order. The License Model Attribute section allows you to overwrite default license terms at the line-item level.

ClosedEntitlement Line Item Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Optional refId1 Reference identifier that identifies the Entitlement Line Item in an external system.
+ Optional refId2 Reference identifier that identifies the Entitlement Line Item in an external system.
+ Required externalId Unique identifier for the line item.
+ Required totalQuantity Total number of seats/licenses associated with this line item.
+ Optional activationMethod

Defines Activation behavior:

>Fixed

>Partial

>Full

>Unlimited

+ Optional availableQuantity Quantity available for activation.
+ Optional fixedQuantity Fixed number of licenses consumed per activation.
+ Optional itemState

Lifecycle state of the line item:

>DRAFT

>ENABLE

>DISABLE

>CLOSED

+ Optional memoryText Memory string associated with LDK-based products.
+ Optional startDate Line-item–specific start date.
+ Optional endDate Line-item–specific end date.
Entitlement Line Item Custom Attributes
+ Optional PlanType Indicates plan level for this line item (e.g., Base, Advanced, Premium).
License Model Attribute
+ Optional EXECUTIONS Used for license model mapping. Available only in Salesforce connector.
+ Optional CONCURRENT_INSTANCES
+ Optional FLOATING_USER_LIMIT
Memory Text / ERP Memory Attribute
+ Optional Memory Text Attributes Memory Text string associated with Sentinel LDK-based products. Memory management applies only to Sentinel LDK enforcement.
+ Optional fileName File name for the Memory Text configuration file. ERP may provide this when memory configuration is stored as a file reference.

>Customer: This tab maps the customer details from Salesforce to Sentinel EMS.

ClosedCustomer Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Required externalId External identifier representing the customer record in the originating system.
+ Required customerName Legal or commercial name of the customer organization.
+ Optional customerIdentifier Unique customer ID; Sentinel EMS auto-generates one when not provided.
+ Optional CRMID Internal CRM identifier used for traceability or cross-system reference.
+ Optional refId Reference identifier that identifies the customer in an external system.
Customer Custom Attributes
+ Optional Customer Region Stores geographic region (for example, North America, EMEA, APAC). Helps Sentinel EMS apply regional compliance rules or activation limits.
+ Optional Customer Tier Represents customer tier (for example, Gold, Silver, Platinum). Used for entitlement prioritization or special activation privileges.

>Users: This tab controls the mapping of Users (contact) data associated with a customer.

ClosedUsers Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Required contactName Full name of the contact person.
+ Required contactEmail Email address used for notifications and delivery.
+ Optional customerName Name of the customer linked to the contact.
+ Optional externalId External reference identifying the contact in the business system.
+ Optional refId1 Additional reference identifier for integrations.
+ Optional refId2 Secondary external reference identifier.
+ Optional loginAllowed Allows the contact to log in to the EMS portal.
+ Optional password Password for portal access (if not using SSO).
+ Optional billingAddress.address Billing street address.
+ Optional billingAddress.city Billing city.
+ Optional billingAddress.state Billing state or region.
+ Optional billingAddress.country Billing country.
+ Optional billingAddress.postalCode Billing postal/ZIP code.
+ Optional billingAddress.useBillingAddressAsShippingAddress Indicates if shipping and billing addresses are the same.
+ Optional shippingAddress.address Shipping street address.
+ Optional shippingAddress.city Shipping city.
+ Optional shippingAddress.state Shipping state or region.
+ Optional shippingAddress.country Shipping country.
+ Optional shippingAddress.postalCode Shipping postal/ZIP code.
+ Optional userType User Type.
+ Optional userId User Id.
Users Custom Attributes
+ Optional Preferred Language Preferred Language preference for activation instructions and entitlement communication. Supports localization in Sentinel EMS.

>Channel Partner: This tab maps the channel partner details from Salesforce to Sentinel EMS fields. Use this tab if your sales model involves distributors or resellers.

ClosedChannel Partner Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Optional partnerName Name of the channel partner.
+ Optional partnerIdentifier Unique identifier for the channel partner; auto-generated if not provided.
+ Optional externalId External reference identifier used to identify the channel partner.
+ Optional refId1 Additional reference identifier for integration or partner tracking.
+ Optional refId2 Secondary reference identifier for integration or partner tracking.
+ Optional status

Channel Partner status:

> Enabled

> Disabled

+ Optional billingAddress.address Billing street address of the channel partner.
+ Optional billingAddress.city Billing city.
+ Optional billingAddress.country Billing country.
+ Optional billingAddress.state Billing state or province.
+ Optional billingAddress.postalCode Billing postal or ZIP code.
+ Optional billingAddress.useBillingAddressAsShippingAddress

Indicates whether billing address is reused as shipping address.

> Yes: To use the same address for both billing and order shipment.

> No: To expand the pane and specify a different Shipping Address for receiving orders.

+ Optional shippingAddress.address Shipping street address of the channel partner.
+ Optional shippingAddress.city Shipping city.
+ Optional shippingAddress.country Shipping country.
+ Optional shippingAddress.state Shipping state or province.
+ Optional shippingAddress.postalCode Shipping postal or ZIP code.
+ Optional partnerLogin.userIdentifier Unique identifier for partner login; auto-generated if not provided.
+ Optional partnerLogin.email Email used by the channel partner for login.
+ Optional partnerLogin.userName Username used to access the Sentinel EMS portal.
+ Optional partnerLogin.externalId External reference identifier for the partner login user.
+ Optional partnerLogin.password Password used to log on to the Sentinel EMS portal.
Channel Partner Custom Attributes
+ Optional Partner Discount Percent Default discount from ERP; can drive pricing calculations associated with entitlements.

>Activation: This tab maps activation-related fields such as activation date, code, or custom attributes. This ensures accurate transfer of activation data between source and target systems during order processing.

NOTE   The Activation tab is available only in the Order Field Mapper in the Salesforce connector.

ClosedActivation Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
+ Optional Activation Description Text describing activation details or notes.
Activation Custom Attribute
+ Optional CustomActivationRegion Region where activation occurred.

>Entitlement Status: This tab maps the entitlement status details from Salesforce to Sentinel EMS fields.

NOTE   The Entitlement Status tab is available only in the Order Field Mapper.

ClosedEntitlement Status Field Mapping Reference

Source Field / Source Attribute in Business System Required? Target Field / Target Attribute in Sentinel EMS (Standard or Custom) Description
Draft Required Draft No call is made.
Activated Required Commit Commit the entitlement.
+ Optional Closed Close the entitlement.
+ Optional Disabled Disable the entitlement.

Mapping Methodologies

There are two ways to instruct the system on how to fill in the data fields:

>Dynamic Mapping (Variable Data): Use this method to link specific data from your source ERP to a target Sentinel EMS standard or custom attribute.

You map a specific source field (such as Order.id, Customer.Name, or Quantity) to the target Sentinel EMS attribute.

Unique data for every order (e.g., Order 101, Order 102) is preserved in Sentinel EMS.

>Fixed Value Mapping (Static Data): Use this method to stamp a single, permanent value onto every transaction, regardless of the source data.

Instead of selecting an ERP field, you manually type a specific text, number, or Boolean value (e.g., "Region: US-East"). For details, see Supported Data Types for Fixed Values.

Identical data is applied to all orders in this workflow.

Supported Data Types for Fixed Values

The Salesforce connector enables users to assign a fixed value (string, integer, or Boolean data type) to any attribute in Sentinel EMS. The input is validated based on the selected data type before being mapped. You can enter fixed values of the following data types:

>String

>Integer

>Boolean (True/False)

For each attribute in the Quote or Order Field Mapper, the input is validated based on the selected data type before being mapped to Sentinel EMS.

NOTE   Fixed values are not supported for date-type Sentinel EMS attributes. If you attempt to assign a fixed value to these date fields, the interface blocks the mapping and shows a restriction message.

The Fixed Values have the following data type considerations:

Standard Attributes: For standard Sentinel EMS attributes such as entitlement attributes, the system respects the predefined attribute data type when mapping a fixed value. For instance, if 'refid1' is a string-type attribute, only string values are allowed to be assigned as fixed values.

Custom Attributes: For custom Sentinel EMS attributes, there is no data type validation when mapping fixed values. Unlike standard entities, all fixed values are treated as strings during mapping. Therefore, while users can input any data type (string, integer, or Boolean), they must ensure that the fixed values align with the attribute’s actual data type as defined in Sentinel EMS.

NOTE   String values are limited to 255 characters due to Salesforce field constraints.

Salesforce Field Mapping Examples

Map Salesforce Values to Sentinel EMS Attributes

The Salesforce connector enables users to assign a fixed (or constant) value, whether string, integer, or Boolean data type, to any attribute (standard and custom attributes) in Sentinel EMS while mapping orders and quotes using the Field Mapper interface. This enhancement overcomes the previous limitation where only Salesforce fields could be mapped to Sentinel EMS attributes. By using fixed values in the data-mapping process, users can ensure consistent value mapping across all orders and prevent invalid data entry.

Steps to Map an Order Field

1.Go to Order Field Mapper in the Salesforce Connector UI.

2.Click the entity tab corresponding to the field you want to map.

3.Click plus (+) next to the field you want to map. This opens the screen to choose the field you want to map.

4.Select either Salesforce Field or Fixed Value.

Salesforce field: Choose from the available fields in the list.

Fixed Value: Enter a fixed value in the value input field. In case of a Boolean value, select 'True' or 'False'.

5. Click Save.

Map a User ID to Sentinel EMS

The Salesforce connector includes the userId field within the Users entity tab in the Field Mapper interface. This field is visible on the Users page under User Attributes in the Sentinel EMS UI. This enables seamless association of Salesforce user identifiers with Sentinel EMS user data.