Tax FSO Demands notifications and assignment of ticket to Tax OTO

For Tax FSO demands we need below changes:

1. Add notifications for Tax OTO as we receive for RTH demands -

[SB] This is already working. When the intake is first with RTH OTO and they update the ‘Regional Specific Demand’ as Yes to confirm the same, a notification gets sent to the Tax AREA OTO. PFB the notification.

2. Any FSO demand in an RTH region should be notified to FSO OTO & Tax OTO

[SB] This can be taken as a requirement. We will wait for the below two requirements to be clarified.

3. Add a mechanism to route the ticket to Tax OTO without removing the FSO domain from the ticket. This is so a ticket can be managed by Tax OTO if needed but keeping FSO flag for our reporting purposes

[SB] Could you please help us with a business case? What is the expected process in such a scenario?

[SK] Kelly is fine tax working on these demands. She wants to reassign these intakes to tax OTOs without changing the Portfolio/domain.

[SB] Sandeep will have an internal call with Joel, FSO and RTH. CT DMA core team has shared the RACI matrix.

4. Possibility of auto-selecting a PPEDD on the basis of selected Area for FSO demands. Like Stuart Lang for all FSO EMEIA demands. Full matrix to be provided later.

[SB]: Need to ask Kelly for the approval matrix for the PPEDD list for SL and portfolio combinations.

[SB]: A new idea (https://ctdma.ideas.aha.io/ideas/CTDMA-I-98) has been created for the 4th item to track it separately.