As an user I should not inform the staging table name when adding TOTVS connectors (Protheus, RM, and Datasul)

Description

PRDE - Story default text according to the team DoR (Definition of Ready)

02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

  • We should not show the input field “Staging Table Name” when creating TOTVS (RM, Protheus, and Datasul) connectors.

06 - ACCEPTANCE CRITERIA:

When adding a new TOTVS connector, we should not show “Staging Table Name” parameter.

When confirming the creation of a TOTVS connector, we should not show the fields “staging table name” and “crosswalkField“.

Activity

Automation for Jira 6 February 2024, 18:47 Jira Internal Users

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

Automation for Jira 5 February 2024, 22:53 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 pedrobuzzi.

Chámam Diomede Caires 5 February 2024, 22:51 Jira Internal Users

DONE

Automation for Jira 29 January 2024, 18:26 Jira Internal Users

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

Automation for Jira 27 January 2024, 22:55 Jira Internal Users

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

chore(connector): https://totvslabs.atlassian.net/browse/CAPL-5317#icft=CAPL-5317 TOTVS connectors create flow changes

Automation for Jira 22 January 2024, 20:36 Jira Internal Users

@MARCOS STUMPF ,
@Jonathan Willian Moraes ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12

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