Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page

Was this helpful?

  1. Services

Motator

Motator's responsibility is to map Content Types and Fields between different systems. Let's say that you have a WebContentGeneric content type in the source but a RichText content type in the target, that will store the same data. You will need to use the Motator to achieve it.

Important

  1. All mapped content will live under Diesel /mapped bucket, using the same ID that the motation.

  2. All matches are case-sensitive. Be aware of that when using the API.

  3. You could use the All keyword to use mapping saved to All endpointId or/and to All originUniqueId.

  4. If you have a mapping for All endpoints, and you also have a mapping for a specific endpoint. The mapping with the specific endpoint will take priority.

PreviousSchedulerNextMotator Service

Last updated 2 years ago

Was this helpful?