Customisation and configuration

Obsolete / replaced configuration properties

• Following the update of ARender to version 2023.15.0, and if you have also updated FlowerDocs to version 2025.2.0, please note that the application.properties file is no longer required for the installation of the ARender HMI application.

Technical changes

• ARender version upgrade : 2023.15.0.

Security

• Improvements to FlowerDocs security have been made by upgrading library versions. This proactive approach ensures better protection against vulnerabilities.

Development

• Loading LDAP groups when using FlowerDocs docker-compose is now functional.
• The FlowerDocs docker-compose configuration has been optimised. This improvement aims to facilitate the use and coexistence of multiple containers of different versions, as well as their associated volumes, on the same development machine.

Behavior changes

Integrator

• The new library, flower-docs-ws-rest-client, has been integrated to facilitate interactions with FlowerDocs REST services. It can now be used for OperationHook and GUI plugins with a SecurityMode.TOKEN security configuration.
  
• Component validations now run after OperationHandler in the BEFORE phase. This change allows you to validate a component using data calculated via integration.

Search

• The display of columns in the results table has been improved for better consistency with expected behaviour. The display rules are now detailed in the documentation, available here.

Companion

To optimise document management, the FlowerDocs identifier is now stored in a JSON file named {UUID}.{fileExtension}.json, located with the associated Microsoft Office document. Previously, the name was {fileName}.json.
The old JSON files remain functional and will be automatically updated to the {UUID}.{fileExtension}.json format the next time the document is modified.

The UUID is generated by Companion and stored in the Microsoft Office file metadata to ensure it is retrieved during an update in order to identify the associated json file..

FlowerDocs GEC

The following configuration documents have been modified: :

• sol-unassign.js

FlowerDocs eProcess

The following configuration documents have been modified: :

• sol-unassign.js

API

Behavior changes

• With the FS connector, the endpoint /core/rest/documents/{id}/files/{fileId}/name now only modifies the name of an existing file, without overwriting other data..
  
• The CSV export endpoints /flower-docs-ws/rest/{category}/search now only export the columns specified by the caller (FlowerDocs GUI or integrations) in the SelectClause clause of the search..

Téléchargements

---

---

---

---

---

---

---

---

---

• Autres versions