Limitation on sending TaskToDomain Mapping as a part of the event body

[junaidHussain-clari]

Hi @apanicker-nflx @v1r3n @manan164 ,
I have some questions about task domain and events:

1. Suppose an event triggers a workflow using the start_workflow action in an event handler. Can we pass taskToDomain mapping in the event so that the event handler can catch and start the workflow with the passed mapping? As per my understanding, the current implementation is to hardcode the taskToDomain map as a part of the event handler. But that means all the workflows this event handler starts will have that taskToDomain mapping and as a result run in Isolation.

2. If we can't send the taskToDomain map as a part of the event body when triggering a workflow by the event handler, can you help me understand the reason why it was done this way?

3. If we want to change this behaviour and allow the taskToDomain map to be passed with other inputs as a part of an event, can you please suggest what's the recommended way to do this?

4. Same question for the SUB_WORKFLOW task. We need to define the taskToDomain map at the time of registering the parent workflow definition. Therefore, we can't pass different taskToDomain maps at the start of the subWorkflow.

We are trying to use Task Isolation and the above limitations are blocker for us. Thank you.

[junaidHussain-clari]

Hi Team, Can someone please help me with the above queries? Thank You.