Veritran Docs

We added a new title to the legacy processes diagram feature to identify to which process each diagram corresponds, so that the user does not have to hover the cursor over each tab for the tooltip to be displayed.

We added the Low-Code Test files to the merge request details and to the resolution of conflicts sections.

We fixed an error in the legacy processes diagram feature that caused that, if the user invoked an inexistent process, the screen went blank.

We fixed an error that caused the screens and legacy processes cache not to work properly when a cherry-pick was run in Gitlab, and, as a result, entities were not properly updated.

We fixed an error that showed an incorrect user when a merge was executed if a cherry-pick was previously run in GitLab in the source branch of such merge.

We fixed an error that caused that, when the user saved a screen, multiple commits were executed in reference to the files of the entities involved in such saving.

We improved the order of published targets. Now, targets are displayed in descending order by last published target.

We improved the 504 publication error to inform the user that the error involves a Workspace timeout and does not refer to a publication error, which continues in process.

We made UI adjustments to the contrasts in Studio dashbord, to improve legibility and the responsive design in different resolutions.

We added an improvement in the legacy processes diagram feature that allows the user to click on a process flow and open it in a new screen with its respective diagram.

We added an improvement in the screens editor right panel and now, when adding a value to a corner, the value is no loger configured for the remaining corners by default.

We fixed an error that changed to lower-case letters the writing of inputs and outputs values entered in modules interfaces.

We fixed an error in the screens editor that caused the Actions tab of the right panel to empty when the user activated the “Configured attributes only” switch in a fragment component.

We fixed an error that caused the Radius value to recalculate when the user changed the unit of measurement.

We fixed an experience error that occurred during the app creation process. Now, Marketplace is only involved when the user creates an app from a template (Create from Template option).

In this version, we implemented the Radius editor features included in Studio 3.0.

We fixed an error in Webfly that caused changes in publications not to appear.

We fixed an error in Diagnostics and now the Unlinked dependencies rule is available. This rule analyzes whether the modules are activated when it identifies that an app invokes an screen-type or component-type interface. If the app is invoking either of them, but the module containing such interfaces is not activated, Diagnostics will show an error to inform it.

We eliminated the maxValue in reference to the smallest value of Height/Width in the screens editor right panel.

We eliminated the “”…“” of the units of measurement modal in the screens editor right panel.

We added a tooltip to the screens cards to enable reading the complete text of those tags that were incomplete due to their length.

We unified the syntax of screens (V00|Contents 1:S000) to appear the same way in the screens cards and in App Flow.

We added the "No Theme" option to the drop-down menu of the Theme Info field in the Settings section of apps and modules.

We sorted alphabetically the branch drop-down menu in the dashboard and in the top menu of the overview.

We fixed an error in the Text Input component that caused the component to be deleted when clearing the content of the Value attribute.

We fixed an error in the App Flow diagram that did not generate the diagram when the flow included screens with processes that other screens invoked internally.

We fixed an error in App Flow where, upon reaching the memory limit, the updated information would not load. Now, the functionality is blocked when this happens and is made available again once the information is updated.

We resolved an error in Used in that didn't allow the use of the ";" character after a numerical value. This resulted in the inability to search for tokens with expressions such as #S{7010;F}.

We fixed an error in Used in that caused intermittent loading of results. This resulted in a brief period where no results were found, and then the results appeared.

We fixed an error in Used in that caused the "See all used" functionality " to not work when there were tokens declared as aliases.

We fixed an error in Diagnostics where the functionality threw false positives in the broken connections rule for legacy processes, as it could not distinguish if a value corresponded to a process or to a string starting with "P".

We fixed an error in the legacy process Diagram feature where, upon loading multiple outputs (next) to a process step, only the first one was diagrammed.

We fixed an issue where the execution of merges with conflicts would fail.

We removed the Quick Publish option from the save menu of a screen when that screen belongs to a module since modules, by definition, are not published.

We implemented an update in Studio so that the Workspace session does not timeout when the browser reaches its memory limit.

We enabled the characters á-é-í-ó-ú in the Charset attribute of components.

We updated App Flow to recognize legacy processes that contain spaces in their names.

We updated App Flow so now it detects outputs to screens when there is an event in the beginning of the syntax, such as the system pop-up.

We updated Diagnostics to properly recognize outputs through events, such as a system pop-up calling a screen.

In Diagnostics, we improved the tooltip on orphan entities to clarify that they are only orphan because they are not being used in a screen or process.

We adjusted Middleware's (Lyra) error messages when publishing to make them more understandable for users.

We enhanced the user experience in Studio. The buttons on banners (e.g., the "Try Again" button) are now disabled after clicking, so users don't perform unnecessary actions while waiting for the action to be completed.

We fixed an issue where some registers names appeared broken in the registers list.

We fixed an error in the save button for global parameters that returned an error but still saved the changes. Now the error message does not appear when global parameters are saved correctly.

In Diagnostics, we fixed an error that caused all entities to appear as orphans when running a diagnostic on a new branch.

We resolved an issue with the banner that appears blocking the screen when Studio crashes, and now the user can click "Try Again" to continue working once Studio resumes.

We fixed an error with Studio and cherry-pick (a Git command that selects and applies specific commits from one branch to another), and now, when running cherry-pick in GitLab, changes are visualized in Studio.

We improved legacy processes' Diagram feature by switching the cursor to a hand icon when hovering over clickable elements.

We improved legacy processes' Diagram feature to recognize and diagram when a legacy process exits to another process.

We updated App Flow so that, when merging changes, it detects changes that have been introduced to the branch and updated its data base to reflect those changes on the flow.

Legacy processes Diagram feature, Diagnostics and App Flow and Used In now recognize custom error values set as outputs in legacy processes.

We updated screens' thumbnails shown during a merge so that they reflect changes applied to the branch.

We added a validation to prevent updating two different unrelated entities when saving changes in Studio. Now, every time a change is saved, only one entity is updated.

We implemented an update that, when logging in again with the "Try again" button, opens the log in screen in a new tab.

We made an improvement in the screens editor that now allows the user to leave the height field empty when configuring interfaces, to improve responsiveness.

We improved apps' generation process to reduce memory consumption.

We added zooming options in the legacy processes' Diagram feature.

We updated Used In and now tokens and arrays can be searched by number or alias.

We improved the Diagram in legacy processes and now, when selecting a step, it highlights its previous and next steps.

In the screens editor, in the Accessibility Order field, we implemented the use of frequent keyboard shortcuts.

In the screens editor, in the Accessibility Order field, it is now allowed to use the "-" character to implement negative numbers.

We extended response time in Used In so that, when looking for an entity within a large app, it does not throw a false error.

We fixed an issue on the screens editor that broke texts and background images in the Button component.

We fixed an issue that occurred when generating and publishing a splash screen. If this splash contained a Progress Bar component, the app opened with an error.

We fixed an issue in App Flow and Used in that did not show updates in processes.

We fixed an issue with the "Try again" login button.

We solved an issue that prevented users from seeing recent changes made by other users in lambda processes.

We fixed an issue that did not show background images in buttons when they did not receive a height value.

We fixed an issue in the Accessibility Order field that did not allow values with the numbers 0 or 9.

We fixed screens previews in App Flow.

We fixed an error in Used In that happened when searching for arrays or tokens and switching from one category. Used In persisted the results from the previous search.

We fixed tooltips in Used In that overlapped with content.