Job Configuration

Overarching points -Picking endpoints - Using variables from the platform provided to define content types

Jobs are what we use our endpoints for this is how we define where we want to connect and also how we sync our content. Impulse will use set endpoints as a source or a destination, the amount of endpoints you can have as a destination is as many as you want where currently we only support one source. We are going to be setting up this job with the endpoints we created in endpoint configuration which will be a simple job sync set up from dotcms to contentful or strapi. Setting up a job your going to be promted to choose a source endpoint, the only endpoints you'll be able to see are the ones with the active checkmark in the endpoint configuration so if you dont see it here make sure to go back and select that checkbox. Now we select the endpoint we want the content from dotcms to move to our other platform so we will be selecting dotcms as our source endpoint. Now endpoints have a few additional configuration to them when they are inside of a job. We wont cover all of them but the ones that are needed to make this sync work. For the dotcms Source we are configuring it comes with required configuration in the job screen for dotmcs we must add a content type we use content types to define what the content we want to sync is, as we can sync entire structures of content we want to sync only a specific content type in this sync so we simply would add the identifer from the source platform we are bringing content from.

For Example Dotcms uses variables attached to content types so we would find this variable that is located in dotmcs and add it to the value to sync over for impulsesync to recognize what we are syncing over when impulsesync connects to the dotcms instance. after setting up the configuration for the content type we want to sync it should look like this:

After adding a source endpoint we can add a destination endpoint this is where impulse will sync the content to so lets select our endpoint we created earlier and on this endpoint configuration lets select where the content will end up, we have created a collection type for the content to be synced into so lets take the id of what strapi defines their collection types as just like dotcms they use variables strapis variables look a bit like this api::testing.testing but its still the same idea of using the variable to fill out the collection type option, after adding the collection type we want it to sync in theres two more configurations we need on for this job in particular we are going to add a contentTypeRoute and deliverContentType set to false.

The first option tells impulse at what level to pick up the content or at what level to sync the content and where with a bit of a better defined route, the second option will deliver the content to the correct way so we can visible see it in our strapi instance. After setting these configurations and set up it should look something like this: