Centralize Integration Configuration
Maintain the integration name, logic, properties, mappings, and triggers in one administrative definition.
Integration Configuration
Configure External System Connections and Transformation Logic
Define the integration. Secure the connection. Map the information exchanged.
Explore the capabilityOverview
Protrak Integration Configuration provides an administrative area for defining integrations with external systems. An integration combines a named connection definition with configurable program logic, connection properties, property mappings, and trigger mappings.
The demonstration uses a Salesforce-oriented integration to explain the configuration model. Salesforce is a representative example; the capability is not limited to that system.
Domain Modelling Studio
Configure Integrations as Managed Platform Definitions
Create and Maintain Integration Definitions
Central Integration List
Configured integrations are maintained in a central administrative list and identified by name and integration type.
Named Integration Configuration
A new integration is created with a meaningful name and an applicable program or integration type.
Separate Integrations by Purpose
Multiple integration definitions can be maintained where external systems, endpoints, or business purposes require separate settings and logic.
Configure Integration Program Logic
Program-Based Integration Behavior
The integration definition includes a program area where the logic required to communicate with the external system can be configured.
Keep Logic with the Integration Definition
Program logic is maintained as part of the named integration rather than being disconnected from its configuration.
Support Connection-Specific Processing
The program can use the properties and mappings configured for the integration.
Manage Configurable Connection Properties
Property Name and Value Configuration
Connection and integration settings are maintained as named properties so environment-specific details can be supplied without embedding every setting in program logic.
Protect Sensitive Values
Properties can be marked so credentials, secrets, tokens, or other sensitive values are hidden in the interface.
Maintain Properties Independently
Properties can be added, updated, or removed without requiring the complete integration to be recreated.
Map Protrak and External System Information
Property Mapping
The property-mapping area defines how values used by Protrak correspond to values or properties required by the external system.
Multiple Mapping Entries
An integration can contain multiple mapping rows, allowing different pieces of information to be paired according to the exchange requirement.
Separate Connection Settings from Business Mapping
Connection properties and property mappings are configured in distinct areas.
Configure Trigger Mappings
Trigger-Oriented Configuration
Supported platform triggers can be associated with the integration behavior.
Map Processing to Business Events
Trigger mappings identify when the configured program and mappings should participate.
Maintain Trigger Definitions with the Integration
Event configuration remains visible alongside the program, properties, and value mappings that it activates.
Configured process
Representative Integration Configuration Flow
- 1
Create a named integration and select the applicable integration or program type.
- 2
Configure the program logic used for the external interaction.
- 3
Add connection properties and protect sensitive values where required.
- 4
Define property mappings between Protrak and the external system.
- 5
Add the applicable trigger mappings.
- 6
Save and maintain the integration from the central integration list.
Configured application
Representative Configuration Scenarios
- Maintain the integration name, logic, properties, mappings, and triggers in one administrative definition.
- Supply connection-specific values through configurable properties rather than embedding all values in code.
- Hide sensitive property values from normal display in the configuration interface.
- Map Protrak properties to the values required by the connected system.
- Use trigger mappings to associate the integration with applicable processing points.
- Create separate integration definitions where systems, endpoints, or business purposes require different configurations.
Operational value
Business Benefits
Separate Settings from Program Logic
Supply connection-specific values through configurable properties rather than embedding all values in code.
Protect Credentials and Secrets
Hide sensitive property values from normal display in the configuration interface.
Configure Value Translation
Map Protrak properties to the values required by the connected system.
Connect Integration Processing to Events
Use trigger mappings to associate the integration with applicable processing points.
Support Multiple Connection Requirements
Create separate integration definitions where systems, endpoints, or business purposes require different configurations.
Domain Modelling Studio
Configure Integrations as Managed Platform Definitions
Protrak Integration Configuration brings together program logic, connection properties, sensitive-value handling, property mappings, and trigger mappings within a managed integration definition.
Define the integration. Secure the connection. Map the information exchanged.