Document toolboxDocument toolbox

A new version of Qualitia Automation Studio 7.2.x is now available. We highly recommend you upgrade. Find more details here.

Conflicts in a Task

Owned by Sagar Dubewar (Unlicensed)
Last updated: Apr 18, 2017 by Rajesh M (Unlicensed)
2 min read

The conflicts that may arise while performing a Save As in a Task are as follows:

The step sequence in the Source or Target Task is changed.

Example:

  • "Task1" present in Source Project has three steps A, B, and C.
  • It has been copied to Target Project so the Target Project also has the same task with three steps as A, B, and C.
  • If the "Task1" step sequence is changed to say B, A, C in the Source or Target and a Save As is performed again, a conflict will occur and the task will not get copied.

Steps have been added in the Target Task.

Example:

  • "Task1" present in Source Project has three steps as A, B, and C.
  • It has been copied to Target Project so the Target Project also has the same task with three steps as A, B, and C.
  • If the "Task1" has one or more additional steps added in the Source or Target and a Save As is performed again for the "Task1," a conflict will occur and the task will not be copied.

Steps have been removed from the source or target task.

Example:

  • "Task1" present in Source Project has three steps as A, B, and C.
  • It has been copied to Target Project so the Target Project also has the same task with three steps as A, B, and C.
  • If the "Task1" has one or more steps removed in the Source or Target and a Save As is performed again for the "Task1," a conflict will occur and the task will not be copied.

The Task Name in the Source or Target Task is changed.

Example:

  • "Task1" present in Source Project. It has been copied to Target Project so the Target Project also has the same task.
  • If the name of "Task1" has been changed in the Source or Target and a Save As is performed again for "Task1," a conflict will occur and the task will not be copied.

The static data value for the step in the source or Target Task is changed.

Example:

  • "Task1" present in Source Project has been copied to Target Project. So the Target Project also has the same task. If the static data value for a step has been changed in the Source or Target and a Save As is performed again for "Task1," a conflict will occur and the task will not get copied.

The Objects used in the Target Task may be conflicting.

The Custom Actions in the Target Task may be conflicting.

Not finding what you need?