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

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

• Allow to reprovision more than one table at once.
  • Select automatically all with problems?
  • Allow to select one by one?

• Original issue:
  CAPL-4604: As a tenant admin I should be able to provision staging tables individuallyDone
• Figma: https://www.figma.com/file/FiL1iRG6RPjuNCgVzgGqvaZ3/%F0%9F%9F%A3-Carol-3.0?type=design&node-id=30206-184020&mode=design&t=1RjlSpKSKfWpvTqq-0

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

https://www.figma.com/file/FiL1iRG6RPjuNCgVzgGqvaZ3/%F0%9F%9F%A3-Carol-3.0?type=design&node-id=34529-153381&mode=design&t=ginW2fS64cRXTvmE-4

06 - ACCEPTANCE CRITERIA:

• Allow to select more than one Staging table with checkbox.
• After selecting one or more, show options above search field:
  • Number os staging tables selected
  • Cancel
  • Reprovision Staging tables
• Show confirmation modal with information about the selected stagings
  • Staging name
  • BigQuery records
  • Last consolidated
  • Last record processed
• The provisioning flow should consider the following strategy:
  • Unified Tenant: migration (we would not have the partial provisioning flow)
  • Other tenants (dev/customer): not migration flow - the one that drops the table and provision it again.

Ps:

• We have another ticket to consider the provisioning of data model for the future. The problem associated with Data Model provisioning is that all data will be removed since we don’t have CDS data for golden records.