I see that you are not "adding tasks" via the "ordered acrtivities" but by triggering a workflow.
When an automatic rule creates a task, that task is an "auto-activated" task. This means that if the rule is re-evaluated and the rule condition is false, then its tasks are deactivated and hidden.
However, this apparently does not apply to workflows, only to adding tasks via the "ordered activities"
With "ordered activities" used to asdd tasks, this does work. (that is the idea and concept of these rules)
- a rule, condition "Incident Type = DDos3 ==> action : add task(s) related to "DDoS"
- a rule, condition "Incident Type = Geral V2" ==> action : add task(s) related to "Geral V2"
Changing incident type to "DDoS" will remove all tasks created by a rule that was based on any other incident type and add those from DDoS rule
Changing incident type to "Geral V2" will remove all tasks created by a rule that was based on any other incident type and add those from Geral V2
------------------------------
Guido Janssens
------------------------------
Original Message:
Sent: Tue November 10, 2020 08:28 AM
From: Vítor Fagundes Alves Nogueira
Subject: Changing playbook tasks
------------------------------
Vítor Fagundes Alves Nogueira
Original Message:
Sent: Mon November 09, 2020 08:52 AM
From: Ben Lurie
Subject: Changing playbook tasks
The adding/removing of tasks is typically accomplished by configuration of Rules based on incident type conditions. Can you post the screenshots of the Rule configurations that control this?
Ben
------------------------------
Ben Lurie
Original Message:
Sent: Fri November 06, 2020 08:03 AM
From: Vítor Fagundes Alves Nogueira
Subject: Changing playbook tasks
Hi,
I have a scenario in my environment that if for some reason I need to change the "incident type" of an incident, I need the playbook tasks to be replaced, but this does not happen. Following are prints.
Is there any way I can do this?
------------------------------
Vítor Fagundes Alves Nogueira
------------------------------