Project News
Upcoming Changes on the Anthology Student 26.0 Release
The Anthology Student (AS) 26.0 release, expected sometime in January 2026, will bring changes that may impact the integrations and reports that TCCS and 5C developers have built. Field Length Increases: The maximum character lengths for several key data fields will expand to improve usability by allowing longer names, addresses, and other information. Since the changes will be applied at the database level, 5C developers must review their custom reports, SQL queries, integrations, and any related user-defined fields or validations for potential impacts. Developers are encouraged to review the list of affected fields on the secure SIS Project Box folder and assess any dependent reports or integrations to ensure a smooth transition. Integration Authentication: Anthology is retiring the shared API user account and requiring all integrations to authenticate using application keys. Basic authentication, bearer tokens, and client-side OAuth will continue to function, but server-side OAuth using client credentials and direct API key authorization will no longer be supported. Integrations using these methods must shift [...]
Upcoming Changes on the Anthology Student 26.0 Release
The Anthology Student (AS) 26.0 release, expected sometime in January 2026, will bring changes that may impact the integrations and reports that TCCS and 5C developers have built. Field Length Increases: The maximum character lengths for several key data fields will expand to improve usability by allowing longer names, addresses, and other information. Since the changes will be applied at the database level, 5C developers must review their custom reports, SQL queries, integrations, and any related user-defined fields or validations for potential impacts. Developers are encouraged to review the list of affected fields on the secure SIS Project Box folder and assess any dependent reports or integrations to ensure a smooth transition. Integration Authentication: Anthology is retiring the shared API user account and requiring all integrations to authenticate using application keys. Basic authentication, bearer tokens, and client-side OAuth will continue to function, but server-side OAuth using client credentials and direct API key authorization will no longer be supported. Integrations using these methods must shift [...]
















