PRDE - Story default text according to the team DoR (Definition of Ready)

01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

• Tenant customer has DM with RT enabled.
• We should run a SQL Processing task with the parameter to store data on RT on Unified tenant.
• When the SQL Processing executed on Unified tenant returns fields that the tenant and data model on customer tenant does not have it, the process to store the data on ES is creating the fields on ES.
  • The process to store data on ES should not create fields automatically.

Issue we handled this flow on customer tenants (orchestrator):

PRDE-3450:SQL Processing: it should not create the field on "elasticsearch mapping" whe...Done

03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:

• When running the SQL Processing task on Unified Tenants, when the customer tenant has the RT enabled, the task should remove any field not available on the output Data Model (customer tenant should be the reference) to avoid creating the fields automatically.
• This scenario is observed only for tenants with RT enabled (and the SQL Task should have the parameter to save data in RT).
• This card is covering only the scope for the Unified tenant, related to the fan-out process (copy data to customer tenants).