Skip to main content Skip to complementary content
Qlik Resources
Announcements
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Splitting tasks

When handling tasks in a Merging campaign, data stewards may find that one or more of the source records of one task are inappropriate matches and should belong to a separate task.

Procedure

  1. On the TASKS page, click the name of the Merging campaign you want to open.
  2. From the list of the tasks assigned to you, whether at the initial state or at the validation state of the workflow, click the drop-down arrow to the left of the task to expand it and display the source records.
  3. Select the source record or records you want to move from the current task and group in a new separate task.
  4. In the right panel, click TASK > Split the task.
    The master records for the new task and the initial one are computed as the following:
    • If the initial or new task has only one source left, the new task uses the source values for all attributes.
    • If manual changes were performed on a given attribute, these manual changes are kept for both the initial and the new tasks.
    • If one source was explicitly selected for a given attribute, this source value is kept for the task to which it belongs.
    • Otherwise, the attribute is computed according to the rules defined in the campaign.

    The selected source records are removed from the current task and grouped in a new task which is added at the bottom of the list. Any comments attached to the task to split will be kept for the initial task and removed from the new one.

  5. Optionally, click the Undo arrow in the top-right corner to revert the split and put the source records back under the initial task.

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