Inform Tenants that are not SQL only on january first

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?):

We need to update the notification that mapping is being disabled by January first, to inform that it’s already unavailable.

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:

Update notification message by January first, only for tenants that are not SQL only (consider the SQL only flag):

“The Mapping and Cleansing Rules were discontinued on 30/12/2023. Check how to migrate to SQL Processing.“

Link: https://docs.carol.ai/docs/faq/migrations

Remove previous checking of mapping and ETLs Staging.
Keep it just on home page.

Activity

Automation for Jira 16 January 2024, 20:55 Jira Internal Users

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).

Automation for Jira 11 January 2024, 02:10 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 11 January 2024, 02:10 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 11 January 2024, 02:10 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 11 January 2024, 02:10 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 4 January 2024, 12:56 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by carlosafw,douglascoimbra.

Automation for Jira 4 January 2024, 12:56 Jira Internal Users

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

refactor: inform tenants that are not sql only on january first

Douglas Coimbra Lopes 4 January 2024, 12:55 Jira Internal Users

SQL PROCESSING ONLY TRUE

SQL PROCESSING ONLY FALSE

Automation for Jira 3 January 2024, 22:52 Jira Internal Users

@MARCOS STUMPF ,
@Ingo Wagner , @Carlos Affonso Wagner , @Douglas Coimbra Lopes

Flag was removed since you have just transitioned the issue status/column.

Automation for Jira 3 January 2024, 21:22 Jira Internal Users

Github user felabs01 has just commited and issue was sent back to the REVIEW column.

Douglas Coimbra Lopes 3 January 2024, 20:29 Jira Internal Users

@Ingo Wagner When the user creates a SQLProcessingOnly: false tenant, the message is not displayed on the home page. The logic seems to be inverted

When the tenant IS SQL Processing Only True, the notification appears

Automation for Jira 3 January 2024, 16:53 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 3 January 2024, 16:50 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

refactor: inform tenants that are not sql only on january first

Automation for Jira 2 January 2024, 20:32 Jira Internal Users

@MARCOS STUMPF ,
@Geny Isam Hamud Herrera ,

This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-22

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.