What's New in AppCentral 2.0.1.0

Article • 4/1/2026 • 2 min read

With this release, AppCentral delivers several new enhancements and stability improvements. These updates improve reliability, automation support, and the overall user experience across environments.

Features and enhancements

Automation IDs for redesigned integrations page

Automation IDs have been added to the redesigned Integrations page to support QA automation and provide consistent element identifiers during test execution.

Add responsible party to support case survey feedback

Survey feedback for support cases now includes the Responsible Party in the payload sent to Salesforce. The enhancement ensures feedback is correctly attributed, improving tracking and accountability in customer support metrics.

Resolved issues

The following issues have been resolved in this release.

ID	Description
782411	Deleting a project in Intelligence Studio did not remove the associated agent from Agent Central. Synchronization has been corrected, and deleted agents are no longer displayed.
796123	AppCentral attempted to load assets from an unintended CDN, causing inconsistent behavior. CDN resolution has been corrected to ensure stable application loading.
798237	The AI Assistant did not detect GenAI as the active product context due to incorrect meta tags. The tags have been corrected, restoring accurate context detection.
802122	The AppCentral Live provisioning logic triggered at incorrect times. It now triggers from the Closed Won Opportunity, and invite emails are sent when the AppCentral Live flag is enabled.
796485	For F&B tenants, selecting the F&B Product AI Assistance Agent in Agent Central resulted in a red box error instead of allowing the user to interact with the agent. The interaction flow has been corrected, and users can now access and use the agent without errors.
797974	For newly onboarded Traverse tenants, launching AppCentral intermittently showed a continuous loader, preventing users from accessing the application. Reloading the page was the only workaround. The loading behavior has been corrected, and AppCentral now launches consistently without interruption.
803849	Certain records were missing in the AppCentral database, causing failed GET operations. Data mismatches have been corrected, and missing entries have been restored.