DataModel: create fields via code (post DM as a snapshot)
Description
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?):
04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
Let’s take a look at how BQ allows us to create a new table and bring some ideas from it to our Data Model create flow.
- Focus on text mode.
Unable to render embedded object: File (image-20230612-052606.png) not found.
Unable to render embedded object: File (image-20230612-052619.png) not found.
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):
Unable to render embedded object: File (image-20230824-191435.png) not found.
Unable to render embedded object: File (image-20230825-122105.png) not found.
10 - ACCEPTANCE CRITERIA:
The entire DM schema should be saved with a single request using the snapshot endpoint, instead of manually adding each field to the DM entity;
Activity
Details
Priority
High
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
@MARCOS STUMPF ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner , @Andre Pasold , @Chámam Diomede Caires
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-10-30, 2023-11-20, 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
feat(DM): https://totvslabs.atlassian.net/browse/CAPL-4501#icft=CAPL-4501https://totvslabs.atlassian.net/browse/CAPL-4608#icft=CAPL-4608https://totvslabs.atlassian.net/browse/CAPL-5022#icft=CAPL-5022 Add datamodel via JSON schema
@MARCOS STUMPF ,
@Carlos Affonso Wagner , @Andre Pasold , @Chámam Diomede Caires
This issue was planned to be delivered until 2023-11-20. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-10-30, 2023-11-20
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.