Intent Tasks are being picked wrongly since Task class & Starting Flow are same
Can we have different Intent Tasks with the same Task class & Starting Flow (Intent Tasks are of different name)? we have a requirement to use so, but it's not picking the correct intent and always picking the first Intent that is found in the D_Interaction_Driver categories with this Task class and flow name for different Intents.
D_Interaction_Intents page is getting populated with the same intent details always.
Is there any way of customization that we can handle this scenario?
Yes, we use the same flow to be invoked in both tasks. but the task names are different, task names are different. based on task name, business functionality will changes for each task internally.
Basically, here we have upgraded application from 6.2 to 7.2. it was working fine in 6.2 with same Task class and starting activity in 6.2, but in 7.2 it's unable to handle the OOTB logic while pulling the Intent from Interaction Drive.
I am not sure that your requirement can be easily implemented for now.
I did a search on how intent task is created. Hope this will help you in some way.
Intent Task depends on data source rule. Each data source rule is mapped to a class. For ex: Account data source is mapped to PegaCA-Interface-Account class and Contact data source is mapped to PegaCA-Interface-Contact class. Same Intent task is copied in to different class to display it in a different Category
Basically, you can create the Data Sources that map the class of the Task to the category in the Interaction Driver.
Steps to create Intent Task:
First we need choose the category in which you want to put the Intent Task
This associates the Intent Task with the data source that is configured in the Interaction Driver category
Give the task a name and description.
The associated class field allows us to choose which interaction this Task can be used for, or if we want it to be available for all interaction types then we enter PegaCA-Work-Interaction