Veritran Docs

We fixed an infinite‑loop issue that occurred when an organism or flow onLoad property pointed to a lambda process which, in its next action, rendered another view—and that view in turn loaded the same lambda process.

We improved the lambda interpreter to resolve an execution error that arose when the context contained arrays with null values. This fix prevents unexpected lambda processes failures, ensuring correct completion and greater processing robustness.

We added new functionality to context synchronization for organisms, enabling dynamic output generation and registration directly from the interface. Outputs are no longer limited to predefined names, resolving parent‑child synchronization problems when custom attributes are used. These outputs are now stored as tokens in the proper sequence, guaranteeing their availability to the backend.

We corrected an issue in components that use autodump and parsable CSS classes, where the arrayId and arrayRow values were not preserved during an onChange event. The array information now remains intact through parsing, improving data‑update accuracy and providing a more consistent user experience with autodump‑enabled components.

We fixed a problem in event concatenation that blocked sequential execution of messages when organisms needed to be updated with a REFRESH message.