Skip to main content

Populating campaigns dynamically using campaign IDs

This Job loads tasks into campaigns defined in Talend Data Stewardship using campaign technical names. Context parameter are used to pass technical names as context variables to the Job at runtime.

Suppose that you need different testing and review stages to go through before validating and pushing data into a production campaign on a Talend Data Stewardship instance. You will need to push data first to experimental and QA campaigns to make sure all is working as it should.

This Job shows you how to use campaign IDs as context variables and push data to different campaigns on the same instance.

For more technologies supported by Talend, see Talend components.

This scenario applies only to subscription-based Talend products.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!