Veritran Docs

We fixed a problem in the resolution of the array attribute in the Repeater component to allow dynamic expressions to be resolved properly.

We fixed a parameter validation error in VTString component functions that caused incorrect results or runtime failures when invalid values were entered. This fix improves system stability and ensures VTString functions handle invalid inputs properly.

We fixed an issue that did not allow to hide pop-ups correctly when their parent panel had screenshots disabled. This will allow to hide pop-ups as expected when recording a screen to enhance users' data privacy.

We fixed an issue that closed apps when executing a lambda process.

We fixed an issue that did not allow to combine custom and basic styles correctly. Now, it is possible to concatenate styles correctly (among style and custom) and, if there are any repeated attributes, the last defined value will be taken into account.

We fixed an issue where the Flex component remained visible on the screen even after it had been destroyed.

We fixed an error that prevented sending events to two components contained within different fragments, as only one of them would execute the event.

We fixed a position calculation error in the Flex component that caused a 1-pixel gap between components on some devices.

We fixed an issue in the VTPanel with active scrolling that prevented the Move Over Keyboard from working correctly.

We fixed an issue that caused the status bar to overlap with the app views. Now, the interface elements are displayed correctly, ensuring better visibility and user experience.

We fixed a bug in the Card Container component that caused the card to move while a process was running.

We fixed an issue that caused the application to close when simultaneously reloading a VTDataGrid.

We fixed a bug in the Input component that caused a quick flicker when setting the default text.

We fixed an issue where the Stretch property was not correctly applied when text contained multiple font styles using #O.

We fixed an issue that occasionally caused the application to crash when scrolling in a Repeater Component.

We fixed an issue that prevented a Flex Panel from closing properly when triggering the event that was supposed to destroy it.

We fixed an issue that caused the application to unexpectedly close when loading a masked input. Now, users can enter data in formatted fields without interruptions, improving stability and user experience.

We fixed an issue where Flex Container components of type LazyLoad were not created in the specified order during their creation.

We fixed an issue where the image name of an item was overwritten with the name of the selected image.

We fixed an issue that caused the ProgressBar to pause before completing its execution. Now, the progress bar remains active until it finishes correctly, ensuring a better user experience and a more accurate flow in progress visualization.

We fixed an issue that prevented a Button component from resizing correctly when triggering a refresh event.

We fixed an issue that prevented new content from loading correctly in the Repeater component when executing an UPDATE_CONTENT event.

We resolved a problem that occurred when performing drag and drop on a panel, which caused it not to position correctly in the configured breakpoints. Now, elements align precisely according to the configurations.

We adjusted the UserAgent configuration to prevent unnecessary reports to Mobile Troubleshooting, improving performance and stability on mobile devices.

We added a new version of the Firebase Performance SDK which allows to track different metric automatically.

We fixed an issue that caused the app to close unexpectedly when selected a "from" date on the calendar component when accessibility was activated.

We fixed an issue that did not assign accessibility focus correctly when a flexComponent had exclusiveForAccessibility activated.

We added a new version of the Firebase Performance SDK which allows to track different metric automatically.