Explore: remove the rejected exploration flow for Realtime storage type
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 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
Tenant or Org as SQL Only.
Pipeline asking to save data on RT
Carol shouldn’t save data on Rejected RT.
We need to review explore for Org / Tenant as SQL Only:
- Golden and Contributors
- Golden Flagged
- Golden Merged
We keep on Explore when previewing RT:
- Golden Records
- Get this data from BigQuery (number of records for the following column):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
If the Tenant or Org is SQL Only:
Carol shouldn’t save data on Rejected RT.
We need to disable/remove explore for Org / Tenant as SQL Only:
- Golden and Contributors
- Golden Flagged
- Golden Merged
We keep on Explore when previewing RT:
- Golden Records
Activity
Details
Priority
Highest
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.38.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 TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by carlosafw,carlosafw,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
feat(org/realtimeDisabled): review flags behaviors
SQLProcessingOnly: falseExplore viewSQLProcessingOnly: trueExplore view@Andre Pasold Good point, E team also confirmed this point
Github user carlosafw has just approved a PR (added as Shard Assignee in this Jira issue).
feat(org/realtimeDisabled): review flags behaviors
@Douglas Coimbra Lopes the goal of the card is to disable access to Rejected only for Realtime storage, the BigQuery Rejected should still be available
SQLProcessingOnly False
SQL ProcessingOnly True
@Andre Pasold It seems for tenants/Orgs
SQLProcessingOnly:true, the Rejected records layer is still visible/accessibleThis 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(org/realtimeDisabled): review flags behaviors
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Andre Pasold ,
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-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.