Get Started
Tailor-Made ItinerariesTour & Cruise ItinerariesFIT Package ItinerariesRole Guides
Kaptio AdminSupplier ContractingProduct Design/BuildProduct ContentTraining ManagerData ExpertsDevelopersKaptio Platform Architecture
Architecture OverviewDevelopment GuidelinesFunctional DecompositionPlatform FAQNew to Salesforce?Security & ComplianceManage your EnvironmentsData Import & ExportGlobal Platform Setup
Getting Started with Core ConfigurationManage Global SettingsConfigure ChannelsManaging Users, Roles & AccessUnderstanding Your Sample DataPIM: Supplier Contracting
Managing SuppliersSetup LocationsManaging ServicesConfigure PricesBulk Import Service DataManage InventoryPromotion & Discount SetupPIM: Tour & Package Design
Getting Started with PackagesUnderstanding Departure TypesManage Package PricingSetup Package ContentConfigure Package DefaultingCRM Module
Customizing Kaptio TravelManage Account Record TypesSetup Trip & Itinerary WorkflowManage Salesforce FeaturesCONNECT: Land & Air Connectivity
Getting Started with ConnectivityPNR Import Setup & UsageIntegrating Amadeus Hotel Connectivity Setup & UsageDOCS Module
Getting Started: ContentManaging Content & MediaSetup Document StagesSetup TemplatesBuilding Custom Content ComponentsBulk Import Content DataUsing the Document Starter KitUsing the ATOL Certificate Starter KitPersonalizing DocumentsGenerating DocumentsCustomer Access to DocumentsEmail Setup & UsageAdvanced Sample Email TemplateCRS: Training Guides
Getting Started: TrainingTraining Reservation TeamsTraining Finance TeamsPAY: Payment Gateway Integrations
Getting Started: PaymentsImplementing Braintree/PayPalIntegrating Your Own GatewayData Migration
Guide to Booking MigrationPeripheral Integration Guides
Accounting IntegrationData Warehouse IntegrationWebsite IntegrationFunctional Decomposition By Capability: Common Extensions on the Kaptio Platform
The following section provides a high-level overview of the most commonly extended capabilities on the Kaptio platform, emphasizing how the data model layer can be extended to meet specific business requirements. This guide focuses on areas where data model extensions are typically necessary and highlights the uniformity of the data layer and the potential for custom extensions and components across different capabilities.
Common Data Layer Characteristics
For each capability discussed, the following characteristics of the data layer remain consistent:
- Extendable Domain Data Validation: Ensures that data integrity and quality are maintained across all customizations and integrations.
- Standard API for CRUD Operations: Facilitates the creation, reading, updating, and deletion of records through a standardized interface, ensuring smooth interactions with the extended data model.
- Configurable Security Model: Provides a shared and robust security framework that can be tailored to protect data according to specific business rules and compliance requirements.
Custom Service Extensions and User Experience Components
Across all capabilities:
- Custom Extension Services: Developers can add bespoke services to enhance or supplement the core functionalities of each capability, tailored to specific operational needs.
- Custom UX Components: Tailored components can be built to enhance user interfaces or add unique functionalities that are not covered by standard Kaptio or Salesforce components.
Data Model Layer Characteristics: Core vs. Extendable Objects
In the Kaptio platform, the data model layer is crucial for managing how data is structured, stored, and interacted with. This layer includes both core and extendable objects, each serving specific roles within the platform's architecture. Understanding the distinction between these two types of objects is essential for effectively extending the platform's capabilities.
Characteristics of the Data Model Layer
The data model layer in Kaptio's architecture facilitates comprehensive data management tailored to the needs of the travel and tourism industry. Key characteristics of this layer include:
- Scalability: The data model is designed to scale efficiently as data volume grows, ensuring that performance remains robust under varying load conditions.
- Flexibility: While core objects provide the necessary structure for the platform's essential functions, extendable objects offer the flexibility needed to tailor the platform to specific business requirements.
- Integration Readiness: The data model is structured to facilitate easy integration with external systems, providing clear pathways for data synchronization and updates.
Core vs. Extendable Objects
Core Objects:
- Definition: Core objects are the fundamental elements of the Kaptio data model that support the primary operations of the platform. These objects are pre-defined by Kaptio and are essential for the platform's basic functionality.
- Characteristics: Core objects are highly optimized for performance and are tightly integrated within the platform's ecosystem. Modifications to these objects are generally not recommended as they can affect the platform's stability and the integrity of future updates.
Extendable Objects:
- Definition: Extendable objects are designed to provide customization options without altering the core structure of the data model. These objects can be modified or extended to meet specific business needs.
- Characteristics: Extendable objects allow for the addition of custom fields, relationships, and even entirely new objects tailored to specific processes or business models. They are designed to integrate seamlessly with the core data model while offering the flexibility needed for customization.
By Capability
The diagrams below illustrates which objects within the Kaptio platform are core and which are extendable by Module & Capability. This visualization helps developers and system architects understand where they can safely make modifications or additions to enhance functionality without compromising the core operations of the platform.
- Functional Decomposition By Capability: Common Extensions on the Kaptio Platform
- Common Data Layer Characteristics
- Custom Service Extensions and User Experience Components
- Data Model Layer Characteristics: Core vs. Extendable Objects
- Characteristics of the Data Model Layer
- Core vs. Extendable Objects
- By Capability
- PIM: Supplier Contracting
- PIM: Content Management
- PIM: Tour & Package Design
- BOOK: Availability & Booking Feeds
- OPS: Passenger Registration
- OPS: Tour Production