Skip to main content

Veritran Docs

2.9.20

Release date: May 2025

Fixes
  • We fixed an issue in sending messages from an organism to its parent using the annotation E__CURRENT_MODULE_INTERFACE. Messages were not being delivered correctly, preventing their execution. With this fix, we ensure effective communication between organisms and their parents, improving feature integration and providing a smoother user experience.

  • We fixed an issue with closing loading modals that were being removed using an identifier (ID). This approach caused conflicts when multiple organisms existed, as IDs could be duplicated. Now, we remove modals directly by node instance, improving context encapsulation and preventing unexpected closures. This correction enhances interface stability when handling multiple simultaneous loading processes, offering a more reliable user experience.

  • We fixed a display issue with multilingual labels in the Delta2 component that prevented proper rendering of texts containing quotation marks due to an encoding conflict. We adjusted the system configuration to ensure translations correctly respect the established encoding.

  • We fixed an issue and added an improvement in theme assignment for views, allowing them to inherit the theme of their module by default when none is assigned. If neither the view nor its module has a theme, it will fall back to the main module’s theme.

  • We fixed an issue with the execution of processes defined in onLoad after rendering an organism or flow. Previously, if the same organism was refreshed multiple times, the onLoad process only ran the first time, causing inconsistent behavior. With this fix, the process now runs correctly on every render, ensuring a consistent and predictable user experience when interacting with dynamic organisms.

  • We fixed an error in record handling during transactions. Now, we send the correct values to the Device Handler (DH) directly from the lambda context, avoiding outdated data or record loss.

  • We fixed an issue where the disabled property was not functioning correctly, and in some cases, the icon was not rendered properly. Both issues are now resolved.