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 have a scenario where data is not propagated due to pipeline processing failure, having as root cause the customer's DATASUL database which is Oracle, and in it has TYPES of fields different from the rest of DATASUL's standard, causing failure in the pipeline due to the TYPE of the field (String, datetime, long, etc).

In the case in question, the field in Oracle is of type NUMBER and in Carol the field is classified as DOUBLE, when the desired is LONG.

More details here:

PRDE-2493: DLABSCAPL-3279 - OSG - Tipagem do banco de dados do Datasul é number porém o ...Done

04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

Create a 2C boolean parameter indicating if there is a Datasul connection.

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:

• When creating a new Database, it should ask the user if this Database is Datasul (yes/no).

• If this new parameter indicates that the connection is Datasul, and the connection is with an Oracle database:
  • It should assume any NUMBER (without specifying the precision) data type, for any staging table, as LONG in Carol Platform (today it considers as double).
• If the Oracle database has a field defined as NUMBER with precision: NUMBER(3,2) it should create in Carol as double.