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

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Douglas Coimbra Lopes

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?):

• Once we perform the Copy Data from a customer tenant to the unified list, we should find a way to avoid the user dropping staging tables that are part of the SQL manifest pipeline for copy data.
• 
  For this case, we’re copying data from stg_nlp_purchaseorder & stg_nlp_product
• 
  Nowadays, the customer is able to delete any of the staging tables that are being copied from the unified tenant
• 
  The staging table has been dropped from the customer tenant
• 

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):

• Create a unified tenant
• Create a customer tenant
• Create a Carol app
• Attach the app to the Unified tenant
• Link the app with a GitHub repository
• Release and approve the app for installation
• Install the app on the customer and unified tenants
• Add the customer to the Allowed list (If the app is a hybrid SQL Strategy)
• From the Customer tenant, try to drop one of the staging tables that are part of the copy data.

08 - ALTERNATIVE STEPS:
09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
10 - ACCEPTANCE CRITERIA:

• Must block drop STG when it belongs to pipeline manifest = Look at the Tenant Mapping.