Skip to content

Feature ETP-3641: Add API Changes related to CRM Connector features#637

Draft
RomanMagnoli wants to merge 2 commits intodevelopfrom
feature/ETP-3641
Draft

Feature ETP-3641: Add API Changes related to CRM Connector features#637
RomanMagnoli wants to merge 2 commits intodevelopfrom
feature/ETP-3641

Conversation

@RomanMagnoli
Copy link
Copy Markdown
Contributor

This pull request updates the developer changelogs (both English and Spanish) to document the complete removal of the CRM Connector from the core product, including all related database tables, columns, and Java event handler classes. The documentation now provides detailed guidance for developers and custom module maintainers on which entities have been removed and what actions are required before upgrading.

Key changes include:

Database Schema Removals:

  • Removed all CRM Connector tables (C_ExtBP_Config, C_ExtBP_Config_Property, C_ExtBP_Config_Prop_Opt, C_ExtBP_Config_Filter, C_ExtBP_Config_Filter_Opt) and their associated Hibernate entities and Application Dictionary entries. [1] [2] [3] [4]
  • Removed CRM-related columns from AD_Org (C_Extbp_Enabled, C_Extbp_Config_ID) and AD_ClientInfo (C_Extbp_Config_ID). [1] [2] [3] [4]

Java Class Removals:

  • Deleted event handler classes in the org.openbravo.event package related to the CRM Connector: ExternalBusinessPartnerConfigColspan, ExternalBusinessPartnerConfigFilterEventHandler, ExternalBusinessPartnerConfigPropertyEventHandler, and ExternalBusinessPartnerConfigurationEventHandler. [1] [2] [3] [4]

Documentation Enhancements:

  • Added explicit warnings and upgrade instructions for custom modules that may reference any of the removed tables, columns, or Java classes, emphasizing the need to update or remove such dependencies before upgrading. [1] [2]
  • Linked to the relevant pull request (PR #977) for further technical details in both language versions. [1] [2] [3] [4]

@RomanMagnoli RomanMagnoli requested a review from Copilot April 1, 2026 20:00
@RomanMagnoli RomanMagnoli self-assigned this Apr 1, 2026
@RomanMagnoli RomanMagnoli added the documentation Improvements or additions to documentation label Apr 1, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Etendo Classic developer API changelogs (English and Spanish) to document the removal of the CRM Connector from core, including removed database tables/columns and deleted Java event-handler classes, plus upgrade guidance for custom modules.

Changes:

  • Documented removed CRM Connector database tables and related columns removed from AD_Org / AD_ClientInfo.
  • Added lists of deleted org.openbravo.event CRM-related event handler classes.
  • Added explicit upgrade warnings for custom modules and linked to PR #977 for full technical details (in both languages).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
docs/developer-guide/etendo-classic/developer-changelog/apichanges.md Adds CRM Connector removal notes (DB + Java) and upgrade warning to the English API changes changelog.
docs/es/developer-guide/etendo-classic/developer-changelog/apichanges.md Mirrors the CRM Connector removal documentation and upgrade guidance in Spanish.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +687 to +693
### Database Schema Changes

The following changes are applied automatically during `update.database` as part of **25Q4 patch releases (March 2026)**. See [PR #977](https://github.com/etendosoftware/etendo_core/pull/977){target="\_blank"} for full details.

**Removed Tables**

The following tables and all associated columns, tabs, and Application Dictionary entries have been completely removed from core. Any custom module that directly queries or references these Hibernate entities must be updated:
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section introduces a second "### Database Schema Changes" heading (there is already one earlier in this same document) and later also repeats "### Removed Java Classes". Duplicate headings can create ambiguous/unstable generated anchors in the site TOC and make it harder to link to the right section. Consider renaming these headings to include the release scope (e.g., "25Q4 Patch – Database Schema Changes" / "25Q4 Patch – Removed Java Classes"), or nesting them under a unique parent heading for the CRM removal section.

Copilot uses AI. Check for mistakes.
Comment on lines +686 to +692
### Cambios en el esquema de base de datos

Los siguientes cambios se aplican automáticamente durante `update.database` como parte de las **versiones patch 25Q4 (marzo de 2026)**. Consulta el [PR #977](https://github.com/etendosoftware/etendo_core/pull/977){target="\_blank"} para ver todos los detalles.

**Tablas eliminadas**

Las siguientes tablas, junto con todas sus columnas, pestañas y entradas del Application Dictionary, han sido completamente eliminadas del core. Cualquier módulo personalizado que consulte o referencie directamente estas entidades Hibernate debe ser actualizado:
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aquí se introduce un segundo encabezado "### Cambios en el esquema de base de datos" (ya existe uno antes en este mismo documento) y más abajo también se repite "### Clases Java eliminadas". Los encabezados duplicados pueden generar anclas/IDs duplicados o poco claros en el TOC del sitio y dificultan enlazar a la sección correcta. Considera renombrarlos incluyendo el alcance de la versión (p. ej., "Patch 25Q4 – Cambios en el esquema…" / "Patch 25Q4 – Clases Java…") o anidarlos bajo un encabezado padre único para la eliminación del CRM.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants