Impacted Areas 9.0

Nov 19, 2015 • 5 minutes to read

Caspio 9.0 is scheduled to be released in December 2015. The following is a list of behaviors that will be impacted in this release. Some of the changes go into effect in the 9.0 release, while others are planned for a future release (but are included here to notify customers in advance).

Aggregation with Collapsible Grouping

Change area	Rendered Tabular Report DataPages
Impact area	Any custom JavaScript that relies on the row count in tabular reports that contain collapsible grouping and aggregation.
Description	When a group is collapsed, if the display of aggregations is set to “Below”, then the first aggregation is moved to the grouping row.

New CSS Classes for Numeric and Date Values in Subgroup Aggregation

Change area	Rendered Tabular Report DataPages
Impact area	Any custom JavaScript that reads or sets numeric and date CSS classes in subgroup aggregations.
Description	New CSS classes are introduced for subgroup aggregation values for alignment. You can view these classes in the Advanced tab of Style objects.

All REST API Calls Require HTTPS

Change area	Web Services Profiles
Impact area	All non-HTTPS REST calls.
Description	For security purposes, all REST API calls will have to use HTTPS.

New SOAP API Calls Require HTTPS

Change area	Web Services Profiles
Impact area	New SOAP API profiles.
Description	All newly-created SOAP API profiles will have to use HTTPS. Pre-existing SOAP profiles are not affected at this time, but we highly recommend you change all HTTP calls to HTTPS.

HTTPS Deployment Code

Change area	DataPage Deployment
Impact area	New DataPage Deployment
Description	For data security purposes, all future DataPage deployments will default to the HTTPS protocol. No option will be provided on the Deployment screen to automatically change the deploy code to HTTP (as it’s not recommended), however if necessary, customers can still modify their deploy code to use HTTP instead of HTTPS, provided that the checkbox to “Enforce encryption over HTTPS” is not enabled on the Deployment screen. Note that within a single app, you must deploy all DataPages using the same protocol to avoid repeated login screens.

Change area

DataPage Deployment

Impact area

New DataPage Deployment

Description

For data security purposes, all future DataPage deployments will default to the HTTPS protocol.

No option will be provided on the Deployment screen to automatically change the deploy code to HTTP (as it’s not recommended), however if necessary, customers can still modify their deploy code to use HTTP instead of HTTPS, provided that the checkbox to “Enforce encryption over HTTPS” is not enabled on the Deployment screen.

Note that within a single app, you must deploy all DataPages using the same protocol to avoid repeated login screens.

Style Update to Auto-Align Dates and Numbers in Tabular Reports

Change area	Caspio Styles
Impact area	Tabular Report DataPages using Caspio’s original Styles without any modifications.
Description	All Caspio-provided Style objects that have not been modified by you will be automatically updated to change the default alignment of data cells from “left” to “auto-align” based on the data type. After this update, number and date fields will automatically be right-aligned in tabular reports. Cell alignment can easily be changed in the Styles wizard at any time. If you have modified the Styles in your account, Caspio will not automatically replace them, but you can download the latest version of Styles and Localizations from the 9.0 Release Notes for import into your account.

Change area

Caspio Styles

Impact area

Tabular Report DataPages using Caspio’s original Styles without any modifications.

Description

All Caspio-provided Style objects that have not been modified by you will be automatically updated to change the default alignment of data cells from “left” to “auto-align” based on the data type. After this update, number and date fields will automatically be right-aligned in tabular reports. Cell alignment can easily be changed in the Styles wizard at any time.

If you have modified the Styles in your account, Caspio will not automatically replace them, but you can download the latest version of Styles and Localizations from the 9.0 Release Notes for import into your account.

“For” Attribute in <LABEL> Tags

Change area	Rendered DataPages
Impact area	Any JavaScript or CSS that relies on the “for” attribute in <LABEL> tags.
Description	The “for” attribute in <LABEL> tags is changed to refer to the element ID instead of the element name due to compatibility with HTML5.

End of Support of IE 6 & 7 for Deployed DataPages

Change area	System requirements for deployed DataPages
Impact area	All deployed DataPages.
Description	Due to current security standards, deployed DataPages are no longer accessible in Internet Explorer 6 and 7, and instead display the message “Your browser version is unsupported.” It is important for end users to upgrade to IE 9.0 or higher, as older versions of IE do not utilize the latest security technology.

Change area

System requirements for deployed DataPages

Impact area

All deployed DataPages.

Description

Due to current security standards, deployed DataPages are no longer accessible in Internet Explorer 6 and 7, and instead display the message “Your browser version is unsupported.”

It is important for end users to upgrade to IE 9.0 or higher, as older versions of IE do not utilize the latest security technology.

“Width” Attribute in <TD> and <TH> Tags to be Deprecated in Feb 2016

Change area	Rendered DataPages
Impact area	Any JavaScript or CSS that relies on the “width” attribute in <TD> and <TH> tags.
Description	The “width” attribute in <TD> and <TH> will be removed in February 2016 due to compatibility with HTML5. If you have inserted custom JavaScript or CSS that refers to the “width” attribute, you will need to prepare for this deprecation over the next three months.

“Name” Attribute in andTags to be Deprecated in Feb 2016

Change area	Rendered DataPages
Impact area	Any custom JavaScript or CSS that relies on the “name” attribute (i.e. name = “cbTable” or name = “groupX” in andtags respectively).
Description	We have introduced a new attribute “data-cb-name” for andtags as an alternative to the obsolete “name” attribute. The “name” attribute will be removed in February 2016 to ensure full HTML5 compatibility of our applications.If you have inserted custom JavaScript or CSS that refers to the “name” attribute, or if you implemented Responsive DataPages, you will need to prepare for this deprecation over the next three months.The Responsive DataPages instructions will be updated with revised code, which you will need to apply to any Responsive DataPages. The 9.0 Release Notes will include more details and instructions.

Change area

Rendered DataPages

Impact area

Any custom JavaScript or CSS that relies on the “name” attribute (i.e. name = “cbTable” or name = “groupX” in andtags respectively).

Description

We have introduced a new attribute “data-cb-name” for andtags as an alternative to the obsolete “name” attribute. The “name” attribute will be removed in February 2016 to ensure full HTML5 compatibility of our applications.If you have inserted custom JavaScript or CSS that refers to the “name” attribute, or if you implemented Responsive DataPages, you will need to prepare for this deprecation over the next three months.The Responsive DataPages instructions will be updated with revised code, which you will need to apply to any Responsive DataPages. The 9.0 Release Notes will include more details and instructions.

Obsolete Attributes in Grouping <SPAN> Tag to be Removed in Feb 2016

Change area	Rendered DataPages
Impact area	Any JavaScript or CSS that relies on the “cbgrouplength” and “collapsed” attributes in grouping <SPAN> tags.
Description	The “collapsed” and “cbgrouplength” attributes will be replaced with “data-cb-collapsed” and “data-cb-group-length” respectively. Additionally, the obsolete “isvalue” attribute will be removed without any replacement.