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

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):
03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

We need to communicate to some tenants that they are still using Mapping and Cleansing Rule, and it is going to stop working (discontinued) on 30/12/2023.

We have documentation on how to migrate to SQL Processing and also on how to remove mapping and cleansing rule.

We will define the rule to show the message, some insights so far:

• Still using mapping and cleansing rule
• Tenant isn’t flagged as SQL Only.
• We won’t communicate customers tenants (example: clockin’s customer).

04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
05 - WHO CAN USE THIS FEATURE (USER ROLES):
06 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
07 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):
08 - ALTERNATIVE STEPS:
09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
10 - ACCEPTANCE CRITERIA:

• Notification related to End-of-life of Mapping and Cleansing Rule.
• Criteria to show:
  • query data from a global DataModel via api-ui endpoint
  • check via endpoint api/v1/connectors/stats/all?fetchCounters=true if the tenant has ETL or Mapping as true