Impacted Areas 70.0

This article lists product areas and functions that are affected by the Caspio 70.0 release.

• DOM Structure Updates
• Webhooks Date/Time Handling

DOM Structure Updates

What changes were made

As part of ongoing platform improvements, Caspio 70.0 introduces several DOM-level updates that may affect some applications using custom HTML, CSS, or JavaScript. These changes include updates to element attributes, event handling, and markup structure across Bridge DataPages and Flex DataParts.

If your applications rely on specific DOM structures, class names, IDs, attributes, or event handlers, review your custom code and make any necessary updates to ensure continued compatibility after your site is updated to Caspio 70.0.

What you should do

If your applications include custom code that targets Caspio-generated markup, review and test your customizations after your site is updated to Caspio 70.0.

Calendar DataPage (Bridge) – record action container

What changed

In Calendar DataPages (Bridge), the record action container has been updated with new data attributes to support improved interaction handling. The onfocusin and onfocusout event handlers have been removed.

New attributes:

• data-cb-interactive-record-action-panel="true"
• data-panel-id
• data-suffix

Potential impact

This change may affect custom CSS or JavaScript that relies on focus-based event handlers or assumes a specific DOM structure or attribute set.

Markup changes

Before:

<div data-cb-name="RACtnr" class="cbResultSetPanelCalendarRAContainer" id="pnl34_5a4edf1b5fd107" style="position: absolute; bottom: 0; opacity: 0" onmouseenter="f_ShowCPDirect_5a4edf1b5fd107('pnl34_5a4edf1b5fd107');" onmouseleave="f_HideCPDirect_5a4edf1b5fd107('pnl34_5a4edf1b5fd107');" onfocusin="f_ShowCPDirect_5a4edf1b5fd107('pnl34_5a4edf1b5fd107');" onfocusout="f_HideCPDirect_5a4edf1b5fd107('pnl34_5a4edf1b5fd107');" tabindex="0" > … </div>

After:

<div data-cb-name="RACtnr" class="cbResultSetPanelCalendarRAContainer" id="pnl34_14fd27ab55b221" data-cb-interactive-record-action-panel="true" data-panel-id="pnl34_14fd27ab55b221" data-suffix="_14fd27ab55b221" onmouseenter="f_ShowCPDirect_14fd27ab55b221('pnl34_14fd27ab55b221');" onmouseleave="f_HideCPDirect_14fd27ab55b221('pnl34_14fd27ab55b221');" tabindex="0" > … </div>

Card Report DataPage (Bridge) – record action container

What changed

In Card Report DataPages (Bridge), the record action container has been updated with new data attributes and removal of focus-based event handlers.

New attributes:

• data-cb-interactive-record-action-panel="true"
• data-panel-id
• data-suffix

Removed:

• onfocusin
• onfocusout

Potential impact

This change may affect custom code that depends on focus events or targets the container based on its previous structure or attributes.

Markup changes

Before:

<div data-cb-name="RACtnr" class="cbResultSetPanelColumnarRAContainer" id="pnl52_748ee384530249" onmouseenter="f_ShowCPDirect_748ee384530249('pnl52_748ee384530249');" onmouseleave="f_HideCPDirect_748ee384530249('pnl52_748ee384530249');" onfocusin="f_ShowCPDirect_748ee384530249('pnl52_748ee384530249');" onfocusout="f_HideCPDirect_748ee384530249('pnl52_748ee384530249');" tabindex="0" > … </div>

After:

<div data-cb-name="RACtnr" class="cbResultSetPanelColumnarRAContainer" id="pnl6_ac3ab37627dc66" data-cb-interactive-record-action-panel="true" data-panel-id="pnl6_ac3ab37627dc66" data-suffix="_ac3ab37627dc66" onmouseenter="f_ShowCPDirect_ac3ab37627dc66('pnl6_ac3ab37627dc66');" onmouseleave="f_HideCPDirect_ac3ab37627dc66('pnl6_ac3ab37627dc66');" tabindex="0" > … </div>

Card Report DataPart (Flex) – paginator container

What changed

In Card Report DataParts (Flex), the “per page” label has been moved from a <span> element to a <label> element. The order of elements within the paginator container has also been updated, and an additional CSS class has been introduced.

Changes:

• <span> replaced with <label>
• Label is now associated with the dropdown using the for attribute
• New class added: cas-paginator-dropdown
• Element order updated

Potential impact

This change may affect custom CSS or JavaScript that targets the paginator label or relies on the previous DOM structure or element order.

Markup changes

Before:

<div class="cas-paginator-element-container"> <div class="p-dropdown p-component p-inputwrapper p-inputwrapper-filled">(dropdown content)</div> <span>per page</span> </div>

After:

<div class="cas-paginator-element-container cas-paginator-dropdown"> <label id="rows-per-page-dropdown-10-appKey" for="rows-per-page-dropdown-10-appKey">per page</label> <div class="p-dropdown p-component p-inputwrapper p-inputwrapper-filled">(dropdown content)</div> </div>

Access denied page (Flex) – external deployment

What changed

In externally deployed Flex applications, the Access Denied page now includes an additional wrapping <div> element around the existing error message container.

Potential impact

This change may affect custom CSS or JavaScript that assumes a specific DOM hierarchy for the error page.

Markup changes

Before:

<div class="ErrorPage-module_error-message-container-HK4Pm cas-datapart-error-message"> <div class="ErrorPage-module_error-message-b1FKt" data-testid="error-page"> ... </div> </div>

After:

<div class="ErrorPage-module_apppage-container-kqx6H"> <div class="ErrorPage-module_error-message-container-HK4Pm cas-datapart-error-message"> <div class="ErrorPage-module_error-message-b1FKt" data-testid="error-page"> ... </div> </div> </div>

Webhooks Date/Time Handling

What changes were made

Caspio 70.0 updates webhook behavior when processing values from Text (255) and Text (64000) data type fields. Previously, if a value resembling a date/time (for example, 2026-02-23T10:00:00-16:00) was included in a webhook payload, the system could interpret it as a date/time value and modify it (for example, adjusting the time or removing the time zone offset).

With this update, webhook payloads now treat Text (255) and Text (64000) fields strictly as text. Values are sent exactly as stored, without conversion, formatting, or time zone adjustment. This change corrects unintended behavior where text fields were implicitly processed as date/time values.

What you should do

If your integrations rely on webhook payloads that include date/time-formatted strings stored in Text (255) or Text (64000) data type fields, review how your applications process these values.

If you previously depended on Caspio modifying or normalizing these values, update your integration logic accordingly. After your site is updated, test any webhook-based integrations to ensure they continue to function as expected.