Allow Custom Default Values for "Insert Relationship Table" in AEM Guides Cloud Service

Description:

In AEM Guides as a Cloud Service, the XML Editor toolbar allows customization through ui_config.json and extension JSON for multiple actions.
However, the Insert Relationship Table (reltable) action currently does not support overriding default values for:

• Header Rows
• Rows
• Columns

For our project, we need the relationship table to be inserted with the following custom defaults:

• Header Rows: 0
• Rows: 2
• Columns: 2

At present, AEM Guides always inserts a relationship table with the hard‑coded defaults:

• Header Rows: 0
• Rows: 1
• Columns: 3

These values cannot be overridden through any configuration methods.

Current Limitation (Confirmed by Adobe Support):

• The relationship table insertion dialog does not read values from ui_config.json or the extension JSON.
• Default row/column values are hard‑coded in the product and cannot be changed.
• Only standard tables/simpletables support configurable default settings as per the 2502 release updates.
• Therefore, configuring relationship table defaults is currently not supported.

Impact on Teams / Business Need:

• We rely heavily on relationship tables for structured documentation.
• Manual adjustment of rows and columns each time is time‑consuming and error‑prone.
• Having the ability to set custom defaults improves authoring efficiency and consistency.
• This is critical for scaling content creation for multiple repositories and teams.

Requested Enhancement:

Please enable configuration support for Insert Relationship Table to allow overriding default values for:

• Header Rows
• Body Rows
• Columns

Ideally, these should be configurable via:

• ui_config.json, or
• AEM Guides extension JSON
• Or a new configuration node under folder profiles

This feature would bring relationship table behavior in line with the recent enhancements made for simpletable and standard table insert dialogs.

Benefit to Adobe Customers:

• Improves authoring productivity
• Ensures consistent table structures across content teams
• Reduces manual editing and human error
• Aligns functionality with other table components already supporting default customization