Starting a Transaction

Running a Job

Now that you created a job, you will want to "run" it to sync the content from you selected source to your selected destination.

You can run a job from the "Jobs" screen. This screen lists all the jobs you have created and allows you to run any of them. Simply press the "Run" button found in the "Transaction" column of the job you want to run. We'll run the job just we just created called "my-first-job."

When you "run" a job, you start a "transaction." A transaction is an individual run of a job. Meaning a job can run many transactions. You can find details about transaction from the "Reports" screen.

After pressing the "Run" button a progress bar appears in it's place. This progress bar measures approximately how far along the transaction for the job is to completion.

Once the progress bar disappears, the transaction is finished. You can now check your destination repo to verify the content is synced.

Congratulations, you've now successfully performed a sync!

Start Transaction Options

A job can be run with different config or options on start. This allows for a job to be configured but a single run can have a different configuration, such as a specific query for a subset of content. To accomplish this, open the run menu and select "Run with Options".

This will take you to a page similar to the job edit page.

From here, job config for endpoints or manipulators can be changed or added. After the endpoint and manipulator config changes you want have been made, go to the "Job Preview" page. From this page you can then run the job with the overwritten config you just set.

Any changes made to overwrite the job config is not saved over the job. The original job still exists and is saved. This allows for a job to be created and configured, then a single sync to be ran with a different set of config, without having to update the job or create another job.

Start transaction options can be saved to a pipeline allowing for the overwrite config to be maintained.

Limitations

• Start transaction options cannot remove manipulators.

  • All base manipulators set for a job will be run. Their configuration can be adjusted, but the manipulator cannot be removed with the start transaction options.