Key Integration Functionality
This section outlines the functionalities of the integration between Seaware and Salesforce to streamline data management, simplify booking processes, and enhance operational efficiency for cruise lines and hotels.
Bi-directional Data Synchronization​
The integration facilitates real-time, bi-directional data synchronization between Seaware and Salesforce for comprehensive client data management. This ensures both systems possess the most recent updates, minimizing discrepancies and inefficiencies.
Customizable Data Mapping: Define a data mapping strategy that identifies specific data fields to be synchronized between Seaware and Salesforce objects. This includes mapping fields relevant to client profiles, reservations, and any industry-specific data points crucial for your operations.
Conflict Resolution Strategies: Implement robust conflict resolution mechanisms to address potential data discrepancies. This could involve strategies like "last write wins," prioritizing specific systems as the source of truth, or employing manual intervention processes for complex scenarios.
Transaction Logging and Error Handling​
Granular Logging: The integration implements granular logging, capturing successful and failed transactions. Success logs are used for auditing purposes, while failure logs provide valuable insights for troubleshooting and identifying recurring issues. Detailed logs capture timestamps, data involved, user information (if applicable), and error codes (for failed transactions).
Log Retention and Archiving: A defined log retention policy determines how long logs are stored within the system. Secure archiving mechanisms store historical data for compliance or future analysis needs.
Automated Error Handling and Retries: An automated error handling process attempts to reprocess failed transactions a predefined number of times before escalating the issue for manual intervention. This improves integration efficiency and reduces the need for manual intervention.
Alerting and Notification: Alert and notification mechanisms inform relevant personnel (e.g., IT team, business stakeholders) in case of persistent errors or critical system issues requiring immediate attention.
Seaware Touch Integration​
Seamless Data Flow: A seamless data flow from relevant Salesforce fields (e.g., client profile, reservation details) pre-populates booking information within Seaware Touch. This minimizes manual data entry, improving efficiency and reducing errors.
Secure User Authentication: A secure user authentication method (e.g., Single Sign-On (SSO) or token-based authorization) allows Salesforce operators to access Seaware Touch through the integration.
Customization and User Interface Integration: Explore potential customizations within Seaware Touch to further enhance the user experience for Salesforce operators. This could involve tailoring the interface to display pre-populated data from Salesforce in a user-friendly manner, potentially even allowing for basic edits within Seaware Touch.
Data Mapping​
Data mapping is a crucial step in establishing the communication between Seaware and Salesforce. It defines how data elements from one system correspond to fields in the other. Here's an overview of the data mapping process for the Seaware-Salesforce integration:
Initial Set of Standard Objects and Fields:
The integration utilizes a set of standard and custom Salesforce objects to represent corresponding data entities in Seaware. This serves as a foundation for mapping specific fields between the systems.
Here's a table outlining the initial mapping between Salesforce and Seaware objects:
| Salesforce Object | Seaware Equivalent | Description |
|---|---|---|
| Account (Standard Object) | Agency and Client Household | Maps agency and client household data. |
| Contact (Standard Object) | Agent and Client | Maps agent and client contact information. |
| Reservation (Custom Object) | Reservation | Synchronizes reservation details. |
| Reservation guest (Custom Object) | Reservation guest | Synchronizes guest information associated with reservations. |
Objects and fields can be mapped directly or include specific processing logic.
Agency mapping example:
| Seaware Field Name | Salesforce Field Label | Salesforce Field Name |
|---|---|---|
| AgencyHeader.DynamicFields[SALESFORCE_ID] | Id | Id |
| 'Agency' or 'Consortium' depending on AgencyHeader.isConsortium | Account Record Type | RecordTypeId |
| AgencyHeader.AgencyId | SeawareId | SeawareId__c |
| Agency.ParentLink[MAIN AGENCY].ParentAgencyID | ParentId | ParentId |
| AgencyHeader.Name | Account Name | Name |
| Phone[PRIMARY].PhoneNumber | Phone | Phone |
| Address.[PRIMARY].* | Billing Address | Billing* |
| Address.[SECONDARY].* | Shipping Address | Shipping* |
Configuration Options for Data Synchronization​
The method of synchronization, source of truth, and data to be synchronized can be customized. Synchronization method and source of truth can be specified within the context of objects or fields. For example, the Client object can be synced bidirectionally; however, certain Seaware-specific data or calculations may flow exclusively from Seaware to Salesforce or vice versa.