Today Auto Task creation can be based on the following:
Task Template Mapping => Based on SR Type, Product Category/Product, Problem Code mapping. For this mapping, Territories need to be setup to determine the Task Owner. If Territories are not setup, the application will not auto create Tasks.
Task Type Attribute Configuration => Based on SR Type <=> CIC Attributes mapping. In this mapping definition, the Task Owner field is required to be setup. Whenever Tasks are auto created, the Task Owner setup in the definition is used.
For Task Dependency - what is the requirement? For a SR Type if three Tasks A, B, and C need to be auto created - are you looking for functionality to first create only Task A and when Task A is closed to create only Task B and when Task B is closed to create Task C?
One clarification for the autask creation process.
In 12.1.2 the autotask creation process was enhanced to have the same functionality as when creating a task manually in the SR Task Tab.
- Assignment Manager and Territories can be used to assign the task owner
- If the auto assignment fails to retrieve the owner, Task Owner Type and Task Owner will be defaulted from the profiles
-Task Owner can be optional based on the value of the profile option Service: Service Task Owner Optional
- This functionality applies to the following task creation flows:
* Task created from the Use Template button
* Automatic Task creation based on Task Template Mapping
* Automatic Task creation based on Task Type Attribute Configuration
Thanks for the response, Denzil. Regarding the task dependency, we need to create all tasks regardless of the dependency with the status as "waiting for pre-req" but parent task number column should get populated with the parent task number value.
Thanks adpulido. Issue with the task templates is there is no provision to enter the task owner (need to set up territories which is a overhead) and task dependency not getting applied as expected (as mentioned in the original post) AND issue with attribute mapping is - not able to set the dependency.
You are rigth. Currently the task template does not allow to define a task owner. We will need to create an ER for this.
Who is the customer and what release are they using?
I have similar issues with auto task creation using task templates and then establish task dependencies. I think I am clear on the task template mapping as to how I need to derive task owner (setup territories). But, as you mentioned the dependency between Tasks A, B & C, how do I establish such a dependency using Auto task creation process?