What's New in AppCentral 2.0.0.1
With this hotfix release, key stability and setup improvements have been introduced in product activation and configuration workflows. These updates ensure smoother setup experiences across modules such as Ship Setup, EAM Setup, and APIA Node initialization.
Resolved Issues
The following issues have been resolved in this release.
| ID | Description |
|---|---|
| 800003 | During Aptean Ship setup, the State field appeared blank and Carriers were missing, preventing users from completing configuration. The issue has been corrected, allowing successful Ship Setup completion. |
| 799980 | When activating the EAM module, prepopulated data failed to load, showing an RBE error message. The setup process has been refined to ensure relevant data is displayed correctly, and unnecessary RBE checks have been removed. Users can now complete setup without interruption. |
| 800366 | APIA Node data was not automatically created during activation. The system now runs automated scripts to generate the required node data, ensuring seamless activation and reducing manual setup effort. |
| 795433 | Activating the Ship module caused most apps to disappear from the All Apps and My Apps screens, leaving only a few visible. The activation flow has been corrected so that all apps remain visible, and Ship now shows the proper Activating status without impacting other modules. |
| 800585 | For non-bundle customers, completing the CRM setup triggered an RBE error and did not update the Setup button automatically. The frontend logic has been updated, and the setup status now refreshes correctly without requiring a manual page reload. |