DataModel: edit Fields via code editor
Description
Issue Component(s) on Oct 29, 2023, 1:27:48 PM: DATA_MODEL | MAINTENANCE
Context:
- to have the new code editor for DataModel Fields working to edit an existing DataModel
- we should support/test:
- adding fields
- removing fields
- reordering fields
- cover cases when the user might mess up with children fields, changing its scope, to make sure we have a solid and consistent functionality
- make sure that after saving, the store is up to date and the current UI is working fine, showing the changes comparing Draft/Published, for instance
- discuss with UX how to anchor this new flow along with the current one (replace it or add a new link to edit fields via code)
Acceptance Criteria
- be able to edit DataModel fields of an existing DataModel
Activity
Show:
Details
Priority
MediumAssignee
Moises Jose Soares Filho
Reporter
Andre Pasold
Labels
PLANNED
Due Date
1 January 2024
Fix versions
CAPL_3.97
Components
DATA_MODEL | MAINTENANCE
Created
29 October 2023, 13:27
Updated
4 January 2024, 21:08
More fields
Created: 29 October 2023, 17:27
Updated:
5 January 2024, 01:08
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.39.0
No associated issue on JIRA TOTVS BRAZIL.
@Andre Pasold ,
@Pedro Buzzi , @Moises Jose Soares Filho , @Andre Pasold , @Douglas Coimbra Lopes , @Moises Jose Soares Filho
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-11-20, 2023-12-11, 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
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.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,moisesjsf.
This card has been validated by the QA team.
@Moises Jose Soares Filho UI improvements when there are no available fields
@Moises Jose Soares Filho The global field list issue has been mapped and a card was created for the BE team.
For now, the issue will remain for new tenants and we will work on the fix at another time. @Andre Pasold @Geny Isam Hamud Herrera
We will work on an improvement to make the code editor bigger in that scenario.
The global list field does not appear.
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
feat(DM):
CAPL-4938 Done allow users to edit a DM field schema via JSON
@Andre Pasold ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner ,
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-11-20, 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Andre Pasold ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner ,
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-11-20
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.