Roadmap
More planned needs
- Support MongoDB sharding architecture
- Support for multiple data centers
- Manager 3.x (Support enabling sharding storage for specific tables; Support configuring log data archiving strategies)
v6.1.0
Developing
- Manager v3.1 (Alarm, Database Slow Query, Index Suggestion)
- Support for configuring the validity period of login sessions (internal users/external portals/apps) in system settings
- Sync HAP SaaS Edition v11.1.0
v6.0.0
Developing
- Support for configuring password policy descriptions in multiple languages in system settings.
- Support for configuring AI services (based on OpenAI) and autonomous integration in system settings
- Support for configuring OCR services (based on Tencent Cloud) and autonomous integration in system settings
- Support minimum installation mode (minimum resource requirements)
- Manager v3.0 (Monitoring Capability)
- Sync HAP SaaS Edition v11.0.0
v5.8.0
Released(2024-11-05)
- Application logs support archiving
- Support configuring customized app push channels
- Support configuring map services (Amap, Google)
- Sync HAP SaaS Edition v10.7.0
v5.7.0
Released(2024-09-29)
- Support viewing archived data (workflow execution history, worksheet record modification logs)
- Workflow AIGC node supports configuring OpenAI models
- Sync HAP SaaS Edition v5.7.0
v5.6.0
Released(2024-07-24)
- Support configuring hidden plugin modules
- Support setting to enter designated application after successful login
- Single sign on support for using Google accounts
- Support enabling new version release reminder
- Support enabling aggregation table functionality
- Support AI mode for configuring workflow AIGC related nodes
- Support configuring AMap API Key
- Sync with HAP SaaS v5.6.0
v5.5.0
Released(2024-06-24)
- Storage component: MongoDB upgraded to v4.4, Kafka upgraded to v3.6
- Support enabling AI features (worksheet field suggestions, automatic generation of workflow code blocks, and application of multilingual intelligent translation)
- Single sign on support for configuring ADFS identity source