Skip to main content

Veritran Docs

Studio

The release notes available include the following Studio versions:

3.0.4.37

Release date: March 2024

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

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

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

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

  • We adjusted the error messages in Middleware (Lyra) when publishing to make them more understandable for users.

  • 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 enhanced the user experience in Studio, and now the buttons on banners (e.g., the "Try Again" button) are disabled after clicking, so users don't perform unnecessary actions while waiting for the action to complete.

Fixes
  • We fixed an issue where broken registers were displayed in the registers list.

  • 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 that prevented viewing changes in Studio when running cherry-pick (a Git command that selects and applies specific commits from one branch to another) in GitLab.

3.0.4.34

Release date: February 2024

New Features and Improvements
  • 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.

Fixes
  • 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.

3.0.4.28

Release date: February 2024

New Features and Improvements
  • 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.

Fixes
  • 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.

3.0.4.14 to 3.0.4.20

Release date: January 2024

New Features and Improvements
  • We enabled the use of the PROCESSING_TITLE constant during the execution of a transaction in lambda processes. This constant allows you to obtain the value configured in the Processing Message field of that transaction.

  • We improved the text that describes the weight and size specifications shown when the user uploads a thumbnail to a theme in Studio.

  • In the Themes section, we introduced the following improvements:

    • We added the Flex component to the Styles list.

    • We removed the limit in variables creation, such as colors and fonts.

    • We eliminated the limit in styles creation.

    • We added the tertiary variable by default for colors.

    • We added the margin and padding variables.

    • We added the option to configure the margin and padding settings for each style.

    • We added the opacity field to color variables.

  • To improve performance when generating and publishing an app, we added the possibility to use the cache to obtain processes and resources already generated. In those cases where the cache is not necessary and the user prefers to generate and publish using the former process, we added a toggle in the Generate & Publish modal that includes this option.

  • We enabled a new Function block in lambda processes that allows the user to decrypt static and custom tokens.

  • We added a new block in lambda processes that allows the user to manage errors in transactions and customize the logic executed in the case of each error.

  • We added detailed information of the transactions invoked in lambda processes.

  • We added a new function type block that emulates the behavior of an #R expression. This block reads the 157 token that contains a JSON with a predefined structure.

  • We added a block in the MATH section that receives a numeric value as input and returns such value in Veritran notation.

  • We added the download of search matches for screens and processes in App Flow's Used In feature.

  • We added the download of search matches for tokens and arrays in App Flow's Used In feature.

  • We added an improvement in Diagnostics that provides greater detail in searches by including entities invoked by dynamic tokens in orphan entities.

  • We added a unified search panel for the Flow Search and Used In features in App Flow that results in an improvement in the user experience.

Fixes
  • We fixed a problem that prevented lists in the cache to load when they were previously deleted by the user, which caused an error when opening a screen.

  • We fixed an error that, when the user used the "Ctrl+S" shortcut outside the screens editor, caused the associated screen to block and to show the Studio re-connection message.

  • We fixed an error in lambda processes that caused the Length of array block not to obtain the number of rows.

  • We fixed an error in lambda processes that occurred when the user invoked a transaction if a RgisterString was changed to a RgisterNumber in the Code tab.

  • We fixed an error that occurred when saving a screen of a module that contained only one screen and interface.

  • We fixed an error in App Flow that did not make it possible to correctly update the list of tokens and arrays when changing the search chip.

  • We modified the App Flow interface. Now, the empty state only appears when no results can be found during a search.

  • We fixed an error that occurred when importing or deleting a lambda process that invoked a transaction that did not exist in the environment.

  • We fixed an error that prevented all the elements to remain within the floating panel.

  • We fixed an error that prevented the correct visualization of images configured in the Background Image and Simulator Background Image attributes for panel components.

  • We fixed an error that affected the font size used by default in label components.

Deprecations
  • We eliminated the ActionsTLC attribute from the right panel of the screens editor.

  • We eliminated the message parameter in the execute async transaction block of lambda processes.

3.0.4.1 to 3.0.4.4

Release date: December 2023

New Features and Improvements
  • We reduced the amount of changes when merging in GIT.

  • We added a new breakpoint for the construction of responsive web apps in the screens editor and we updated the devices' list.

  • We enabled editing on widget components.

  • We removed the Thumbnail and ThumbnailHash tags on screens' XML. They are now stored on the database to remove unnecessary fields when merging in GIT.

  • We migrated XML thumbnails to the database.

  • We improved processing time for actions that involve resources.

  • We improved logs during the thumbnails migration process. As a result, it is easier to track errors.

  • We improved how the components list refreshes in the screens editor after a widget component is deleted.

  • We improved entities lists loading time.

  • We implemented an update that, when creating a branch, copies the screens' previews into this new branch.

  • We added a new modal window that appears when creating or saving screens, legacy and lambda processes, that allows users to describe the updates made to those entities and write down the ticket number where the updates were requested (if needed). This feature improves the integration with Jira and the entities' change history, and helps prevent conflicts when merging changes, since the entity's description is no longer used to provide the commit message.

  • We added the "Used in" functionality to App Flow. It allows the user to search where certain screens, processes, transactions, tokens and arrays are being used within the branch they are working on. This feature also lists every token and arrays that are in use to quickly detect free numeric ranges.

Fixes
  • We fixed an issue that prevented fragments from being visible in the screens editor.

  • We fixed the configuration generation on react components. Now it is only possible to export assets in use depending on the platform and the app.

  • We fixed the apps import process by adding a unique identifier to the ComponentInstance.

  • We fixed an error under which, when deleting an asset and uploading another one with the same name, Studio returned an incorrect preview.

  • We fixed an issue that caused the lambdas editor to freeze when switching tabs in Studio.

  • We fixed an issue that caused the screen to freeze when using the "Ctrl + S" shortcut in Studio.

  • We fixed an error that did not allow to import screens in Studio.

Deprecations
  • No new deprecations.

3.0.3.15 to 3.0.3.23

Release date: November 2023

New Features and Improvements
  • We modified the scope of App Flow's diagram for internal processes, thus improving the visualization of the flow.

  • We improved times in the generation of apps and modules, and in the load of diagrams in App Flow.

  • We created the "Unverified token set as next” rule in Diagnostics, to cover those cases in which an entity calls a token and Diagnostics cannot validate whether its content is correct.

  • We improved module serialization for Delta2, in order to perform it sequentially instead of in parallel.

  • We implemented an update to avoid processing indentations in the CDATA fields of entities to improve their saving process.

Fixes
  • We fixed an error that allowed opening screens with a widget component previously deleted. Now, when opening the screen, a component will indicate that the widget does no longer exist and must be eliminated to be able to close the screen.

  • We fixed an error in the screens editor's right panel that did not allow copying an attribute's value and pasting it into another attribute.

  • We fixed an error that did not allow saving changes to screens containing widgets.

  • We fixed an error that did not show the option selected in the Action attribute's drop-down menu.

  • We fixed an error when duplicating a tab with an active session in the browser, which blocked the screen and did not allow it to be reactivated.

  • We fixed an error in Diagnostics that threw false positive results when calling screens using the short syntax.

  • We fixed an error in Diagnostics that caused the Broken Connections rule to thows a false positive results when legacy processes invoked lambda processes using the "Z" expression.

  • We fixed an error in Diagnostics that caused the Broken Connections rule to throw false errors on screens with identical names.

  • We fixed an error by which App Flow could not recognize calls to lambda proceses using the "Z" expression in the legacy processes' Next field.

  • We fixed an error by which App Flow could not recognize calls to lambda proceses using the "Z" expression in the Next blocks' free fields.

  • We fixed an error in App Flow that did not show information about component-type interfaces in the screens where they were invoked.

Deprecations
  • We removed the access to the Quality Assurance feature from the Branch Actions section in the overview's navigation bar.

3.0.2.23 to 3.0.3.8

Release date: October 2023

New Features and Improvements
  • We updated App Flow's VTUI (design system) version.

  • We added a feature to block the entire Studio user interface when failing to subscribe to SSE (server-sent events).

  • We reduced the screens' loading time.

  • We modified the layout of the last update information in the asset's card so that it matches with how that information is displayed in the asset folders' cards.

  • We added the View Only mode in App Flow applicable to the navigation through interfaces flows when the user is working in an app. This mode allows the user to navigate through the flow but not to open screens and processes within the interface.

  • We replaced the term “Action Library” for “Action Libraries” in the Action Libraries screen, tab and menu header.

  • We added three new attributes for the Map component. The attributes are: on Change Map Region, Dynamic Center y Animated Zoom.

  • We added the Progress Indicator component to the component's section in the screens editor for mobile apps.

  • We improved the previous connections' loading time in App Flow.

Fixes
  • We fixed a new error that duplicated the Studio container when a session crashed.

  • We fixed an error that, instead of showing the site views of the user's current context, showed those of another context previously opened by the user.

  • We fixed an error in Diagnostics that showed screens as broken entities.

  • We fixed an error in Diagnostics that showed those screens called by a lambda process as orphan entities.

  • We fixed an error in App Flow that caused an entity's tags to exceed the limits of the entity's card.

  • We fixed an error in Diagnostics that caused the results of a new diagnostic test to appear in the results panel but not in the details panel.

  • We fixed a new error that duplicated the lambda and legacy processes' name.

  • We changed the type of container in the Accessibility Order attribute for it to support numbers instead of text, also removing the translation functionality for the values there included as it was no longer required.

  • We fixed an error in the screens editor that caused the left panel not to be visible when collapsed.

  • We fixed the copy and paste functionality in the drop-down component input value.

  • We fixed the width and height calculations in the Progress Indicator component, which, in certain cases, showed the value infinity.

  • We fixed the highlight functionality in App Flow, which did not allow to highlight the selected flow when starting from the last entity of the diagram.

  • We fixed an error in App Flow that did not allow lambda processes to be correctly drawn.

  • We fixed an error in Diagnostics where the Broken Connections rule included as an error any case of an entity invoking an error or lambda process.

  • We fixed an error in the screen saving process when switching from one app type to the other (from a desktop app to a mobile app or viceversa).

  • We fixed an error that did not allow the Icon component to display its image and show the correct color.

  • We fixed an error in Diagnostics where the Broken Connections rule included as an error any case of an entity invoking a token not saved in a register.

  • We fixed an error which caused that the screens that were invoked using a short syntax appeared as deleted screens.

  • We fixed an error in the dashboard where web apps were displayed with the mobile app icon.

Deprecations
  • No new deprecations.

3.0.2.1 to 3.0.2.10

Release date: September 2023

New Features and Improvements
  • We added the option to display previous connections on App Flow's diagrams.

  • We introduced a new way to navigate through contexts and manage sessions.

  • We introduced performance improvements when running Diagnostics.

  • We changed the appearance of the local assets folder to differentiate it from global assets.

  • We standardized the layout template's file name structure to avoid exporting files with the same name. The new structure is: export-layoutTemplate-{name}-{date}.xml.

  • We added the name of the user who performed the last modification to an asset into that asset's card.

  • We improved the message shown when a user tries to open an asset previously deleted by another user.

  • We improved App Flow by closing the search panel after a search and by hiding the minimap by default.

  • We improved the message shown in App Flow when a user tries to edit an interface that belongs to another context.

  • We improved App Flow and now search results persist after closing.

  • We added a loader to the sessions banner that shows when Studio is connecting to the server.

  • We improved Studio by preventing SSE to connect to the server automatically. This will prevent browser crashes.

Fixes
  • We fixed an error that duplicated the Studio container when a session crashed.

  • We added the message and option to run Diagnostics before publishing to the Generate & publish modal.

  • We added a message to warn the user that assets can only contain alphanumeric characters or underscores, any other type of character is invalid.

  • We fixed the button used to upload CSS files in the Themes' CSS tab.

  • We fixed an error that caused the filters selected in the list of assets to remain selected when entering an asset's folder, filtering the folder's content as well.

  • We fixed an error that changed the steps' order when saving a legacy process and caused crashes.

  • We fixed an issue that prevented lambdas to be shown on App Flow.

Deprecations
  • No new deprecations.

3.0.1.15

Release date: August 2023

New Features and Improvements
  • We improved loading times in the lambdas editor.

  • We improved the entities list loading times in the cache. The entities included are: screens, legacy and lambda processes, and assets.

  • We improved response times when loading the Next field on a process' Settings tab and when loading processes on a component's Actions tab.

Fixes
  • We fixed an issue that caused lambda processes to appear as unknown entities on App Flow's diagrams.

  • We fixed an issue that caused deleted lambda processes to appear on an App Flow's diagram.

  • We fixed an issue involving Diagnostics, which showed an error when running a diagnostic test on branches that contained lambda processes.

  • We fixed a timeout error that occurred when trying to run Diagnostics on a branch that contained a large data volume.

  • We included a new error message when trying to open a deleted asset from another browser tab.

  • We fixed an issue that prevented users from editing a process that was created on a deleted branch.

Deprecations
  • No new deprecations.

3.0.1.3

Release date: July 2023

New Features and Improvements
  • We added the option to individually export transactions with their dependencies and import them into another environment.

  • We added the option to save transactions as libraries and reuse them as other transactions' actions.

  • We integrated the lambdas and the transactions editors, so that lambdas can also be reused as transactions' actions.

  • We solved false merge conflicts related to the siteID and the siteViewEntityID.

  • We added a checkbox to identify assets (previously called resources) as remote, so that they can be updated from Middleware without the need to update the app's binary or configuration.

Fixes
  • We fixed an error that did not allow the user to visualize the component's attributes correctly in the Visual Builder's right panel. To do so, we enabled the use of double inverted commas when entering variables to attributes with drop-down menues.

  • We enabled App Flow and Diagnostics, which needed to be modified to work with GIT.

Deprecations
  • We deprecated the smartwatch and wearable options, as they were no longer in use and caused errors when generating the app.

3.0.0.214 to 3.0.0.225

Release date: June 2023

New Features and Improvements
  • We added a feature to clean orphaned contexts and tabs IDs when the user logs into Workspace.

  • We hid the Library checkbox in functions.

  • We hid the Institution and Group fields in screens.

  • We removed the headerHash, contentHash and hashAlgorithm fields from screens.

  • We added the option to filter last published targets by app.

  • We included the option to manage the access to the Go to Gitlab and Create branch functionalities from Workspace.

  • We added the justify button to the Text Align options in the Visual Builder's right panel.

  • We added a feature to block the entire Studio user interface when an app's screen is being saved.

  • We added the Author and Unique Identifier information to the entity's details in commit messages.

  • We removed case sensitivity from the Src attribute in the Visual Builder's right panel.

  • We added a loader when saving changes to the processes screen. This blocks performing other actions while saving is in process.

  • We added a scrolling feature that, when adding a new step to a legacy process, automatically jumps to that new step (located at the bottom of the steps list).

  • We added a modal where the user can change the name of a legacy process when importing it.

  • We set a 35-character limit when defining the name of an app during its creation.

  • We added site origin information to a branch's settings, to allow the tracking of that branch's parent.

  • Now, when exporting a legacy process, the process and branch name are included inside the .xml file to make the process easier to identify.

  • We added a modal for the user to validate the target of a quick publish action when that target has already been published in another branch.

  • We added a clearer error message when Redis is down and does not allow the user to switch from one branch to another.

  • Now, when duplicating an asset, a loader appears after clicking the Save button so that the user cannot keep interacting until the result is shown.

  • Now, when adding an action to a component in the Visual Builder, a loader appears after selecting the process option to allow the list of processes to fully load and not appear empty.

  • Now, when editing a function library, a loader appears after saving so that the user cannot keep interacting until the result is shown.

Fixes
  • We fixed an issue involving the change of an app's name when importing an app with a name that already exists.

  • We fixed an issue involving the removal of an existing process before adding a new one with the same name to avoid its duplication in the cache.

  • We fixed an issue involving the visualization of changes in a recently merged screen.

  • We fixed an issue that caused the automatic logout from a context after generating and publishing an app with dependencies.

  • We fixed an issue involving a broken Go to new branch button in the modal that appears after creating a new branch.

  • We fixed an issue involving the color indicator of the modal that opens when a legacy process cannot be imported due to a duplicated name.

  • We fixed an issue involving the Save and Close option when creating a new legacy process.

  • We fixed an issue involving the implementation of classes defined by typing them in the CSSClass attribute of a component only if the class exists in the mobile app theme's CSS section.

  • We fixed an error that caused the automatic logout from Studio when attempting to generate and publish the app.

  • We fixed an issue that caused a failure in Delta2 to export resources when the app was downloaded.

  • We fixed an issue involving the import of screens that use component libraries.

  • We fixed an issue that caused a delay in the opening of the Generate and Publish modal that appears when publishing an app.

  • We fixed the themeText and viewTheme fields when generating a screen.

  • We fixed an issue with the componentInstance ID field, whose content disappeared when the screen was resaved.

  • We fixed the expiration date of all entries saved in Redis by increasing the time frame.

  • We fixed an issue involving Git reset, which showed the last local commit after rollbacking the remote branch, instead of the head of the remote branch.

  • We fixed an issue that caused the feature names to appear as null instead of showing the name given to them.

  • We fixed an issue involving the elimination of screens.

  • We fixed an issue that caused a connection failure in a Git pull.

  • We fixed an issue that made warning messages appear when adding variables such as #A{50:0:1;G} to the labels of a screen.

  • We fixed an issue that made warning messages appear when a adding variables correctly written such as #S{APICallResult} to the attributes of a component.

  • We fixed an issue that caused the Visual Builder's canvas to disappear when opened after a component library is linked or duplicated.

  • We fixed an error that caused function libraries not to appear in the steps of a legacy process.

  • We fixed an issue involving switching branches from the drop-down menu.

  • We fixed an issue involving the sorting criteria in processes list.

  • We fixed an issue that caused the success toast message not to appear after importing a screen.

  • We improved the wording of the confirmation toast message when duplicating a screen.

  • We fixed an issue involving the selection of aliases when completing the attributes of a component in the Visual Builder.

  • We fixed an error that made it impossible to close the Function Library modal when it failed, by adding a close (X) button.

  • We fixed an issue with the Studio breadcrumb which, instead of showing a new branch's name, showed the placeholder "My new app".

  • We improved the texts in the asset duplication process.

  • We fixed an issue that caused an error while generating a component tree.

  • We fixed an issue involving the duplication of a lambda process.

  • We replaced underscores with hyphens when naming an app, to make the app name fit into the card space.

  • We fixed an error that caused a random success toaster to appear when entering the Function Libraries page.

  • We fixed an issue involving the visualization of the View/area dropdown.

  • We fixed an issue that caused an endless loader when modifying a function library from a legacy process which is using that function library.

  • We fixed the visualization of the More options menu, which was partially hidden when filtering transactions in the transactions list.

  • We fixed an error that happened when trying to open and edit a process created by another user from the processes list.

  • We included the possibility to try again when there is an error while listing remote branches in Gitlab.

  • We fixed an error that generated a commit to the repository when a screen was saved without any changes.

  • We fixed an issue that caused poor performance when loading the processes list due to the lack of pagination.

  • We improved the wording of the confirmation toast when deleting a screen.

  • We fixed an issue that caused the Site dropdown, when creating a register, to show the app name repeatedly instead of the branches' names.

  • We fixed an error that happened when creating a component in the Component Library.

  • We fixed an error in the visualization of the Visual Builder's canvas, that caused the visualization to fail whenever a JavaScript function failed.

Deprecations
  • No new deprecations.