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

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM): @Robson Thanael Poffo

02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

We got two incidents in a week related to Carol App making significantly changes on staging table schemas, and it broke part of the tenant for several tenants.

To avoid new incidents, we need to make all staging tables for the connector “protheus_carol” not changeable by Carol App installation.

The Carol App installation will only materialize the connector and skip and creation of staging tables.

We should allow, for this moment, a way to force the installation. This should be a parameter on the endpoint to install the Carol App. This is needed because we are still fixing some tenants with the problem.

03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

• When installing a Carol App, do not materialize staging tables for protheus_carol.
  • Only create the connector, in case it is not there.
  • Log a message on Carol App installation.
• When installing a Carol App, allow a force parameter to force the materialization on the install carol app endpoint.

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

• When installing a Carol App, do not materialize staging tables for protheus_carol.
  • Only create the connector, in case it is not there.
  • Log a message on Carol App installation task.
• When installing a Carol App, allow a force parameter to force the materialization of staging table for this Carol App installation task. (Scenario today when force = TRUE)