[Improvement] Observability Metafields available on the platform to the staging table view page/Datamodel Explore
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):
@Douglas Coimbra Lopes
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
- Since we have the below fields available and queriable for Observability, in order to improve the tracking of data on the platform, we should study to make the meta fields available for:
- StagingTable view page:
mdmAuditId,mdmBatchId,andmdmBatchIdSequence;- All fields are string type.
- DataModel Explore:
mdmAuditId,mdmTaskId,mdmBatchIdandmdmBatchIdSequence- All fields are string type.
- Nowadays we only have them available from the query editor to be queried
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
This fields will not be added on RT.
It’ll be available for all BQ versions.
06 - ACCEPTANCE CRITERIA:
- Allow the user to filter and sort these new fields.
- Staging Area (all fields are string):
mdmAuditId,mdmBatchId,andmdmBatchIdSequence
- Explore (all fields are string):
mdmAuditId,mdmTaskId,mdmBatchIdandmdmBatchIdSequence
Activity
Show:
Details
Priority
HighestAssignee
Carlos Affonso Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
11 December 2023
Fix versions
CAPL_3.96
Components
CONNECTOR | STAGING_TABLEDATA_MODEL | MAINTENANCEEXPLORE | MAINTENANCE
Created
27 October 2023, 15:26
Updated
4 December 2023, 12:43
More fields
Created: 27 October 2023, 18:26
Updated:
4 December 2023, 15:43
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.37.0
No associated issue on JIRA TOTVS BRAZIL.
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 felabs01,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
feat(ST/DM): https://totvslabs.atlassian.net/browse/CAPL-4932#icft=CAPL-4932 added new meta columns to records explorer
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner , @Ingo Wagner , @Moises Jose Soares Filho
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.
@Douglas Coimbra Lopes Yes. All BQ versions.
@Carlos Affonso Wagner Just for confirmation, will we only have the metafields for the BQ layer on Explore?
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(ST/DM): https://totvslabs.atlassian.net/browse/CAPL-4932#icft=CAPL-4932 added new meta columns to records explorer
@Robson Thanael Poffo ,
@Andre Pasold , @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.