Skip to main content Skip to complementary content

Defining a workflow in the Resolution campaign

Workflows control the transitioning of tasks from one state to another. They define how data stewards can collaborate to resolve the campaign tasks, that is which stewards can access which task state or transition.

About this task

For the Product Catalog campaign, you want to add two validation steps to the workflow to give specific rights to different stewards to visualize data. Only the steward assigned to the first validation step, Price validator, has a read-write access to the price values.

Each of the two validation steps enables data stewards to accept or reject the modifications done on the tasks. The data steward added to the last validation step, Data validator, can mark the tasks as resolved or send them back to any step in the workflow.

Procedure

  1. Click Add a validation step to add one validation step in the workflow.
  2. Click in the New field and select the roles from those you defined in the Roles section and for which you want to give access to the new tasks.
    Overview of the Workflow step to create a Resolution campaign.
  3. Do the same in the other fields and decide what data stewards should have access to the first and second iterations of validations and to the resolved tasks.
    Data stewards who have access to the resolved tasks can reopen them and decide to send them back to any previous state in the workflow.
  4. Optionally, click the edit icon next to the name of any step in the workflow and rename it according to your needs.
  5. Click Add campaign to create the campaign and save it.

What to do next

  1. Use a Talend Job to load tasks into the campaign.

    For further information, see Data Stewardship components.

    On Talend Cloud Pipeline Designer, you can also read from and write into campaigns.

    For further information, see Talend Cloud Data Stewardship campaigns .

  2. Assign tasks to data stewards.

  3. Start tasks resolution.

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 – please let us know!

Leave your feedback here