Esta es una versión anterior. La versión actual es 8.13.6. Hackolade 8.13.6 · Fecha de publicación:
Archivos de instalación 8.7.2
| Arquitectura | Tipo | Ámbito | Tamaño del archivo | Descargar | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (Inno Setup) | Todos los usuarios | 115,8 MB | s3-eu-west-1.amazonaws.com | VirusTotal |
El enlace y el SHA256 proceden del manifiesto comunitario del Administrador de paquetes de Windows. Conviene comparar el hash del archivo descargado antes de ejecutarlo.
Notas de la versión
- ArchiMate: added support for forward-engineering of scalar custom properties at model and entity level in Open Exchange file format
- ArchiMate: added support for forward-engineering of complex custom props and relationships in both ArchiMate and Open Exchange file formats
- Custom properties: added ability to declare them for relationships in modelLevelConfig file
- Display options: added support for composite unique keys constrains
- Excel: added support for cross-repository references in forward-engineering and in reverse-engineering, whereby $ref path is exported as defined in the model instead of being converted to absolute path
- Forward-engineering: adjusted compliance in generated JSON sample data, addressing boolean property types, additional properties, and handling of `oneOf` constraints
- Object Browser: added highlight of selected relationship, for consistency with other objects
- Reverse-engineering: enhanced performances by optimizing number of parallel workers for JSON data parsing based on available memory and CPU resources
- Workgroup: added support for sub-groups in GitLab (cloud & server) across all features: Open From, Generate Shareable Link, Save To, and Remote References
- Oracle: added support for removal of primary and unique key constraints in ALTER scripts
- Oracle: added support for removal of comments in ALTER scripts
- Oracle: added support for updating properties of datetime attributes in ALTER scripts
- PostgreSQL: ensured that definition names (UDTs) with special characters (including forward slashes) are correctly resolved throughout DDL generation process
