Veritran Docs

List of Blocks

In this page, you will find information about Veritran-specific blocks and their functionality. Blocks in categories that don't appear in this list have help enabled in context (right-click the block and click Help).

Registers

Registers are data repositories where you can store any value, relating it to a numeric identifier. The register where information will be saved or read from depends on the context of execution (app, module, or component).

Get

Register number (0)

Obtains the value of a register as a number. This block converts the value of a register to number, accepting integers, decimals and the Veritran floating-point expression "N+XXX".

Register text (0)

Obtains the value of a register as text.

Dump

Save register (0) with value ()

Saves a value within a register. Accepts text or numbers (integers or decimals).

Clean

Clean all images

Clears the value of all registers used to store images.

Clean all registers

Clears the value of all registers. This operation can delete important information, use with caution.

Clean register (0)

Clears the value of a specific register.

Arrays

Arrays are data repositories with a numerical identifier. In the Veritran format, one-dimensional arrays are represented as lists, while two-dimensional arrays are represented as tables.

Veritran arrays have their row 0 and column 0 reserved for selector and tags information, so storage of data begins at index position 1.

Arrays

Clean all arrays

Clears the value of all arrays.

Clean array (0)

Clears the value of a specific array.

List

[Get] Array list (0)

Obtains a one-dimensional array as a list of texts (the javascript equivalent is string[]). If the array is saved as a table, it is converted to json format as a list of every row element in the table.

[Dump] Save array (0) with list ()

Saves a one-dimensional array as a list of texts.

Table

[Get] Array table (0)

Obtains a two-dimensional array as a table of texts (the javascript equivalent is string[][]). In case the array was saved as a list, it automatically converts into a one-column list.

[Dump] Set row to array table (0) with list (array) on index

Saves a list to an array table as a row in a specific position.

[Dump] Add row to array table (0) with list (array)

Saves a list to an array table as a new row.

[Dump] Save array (0) with table ()

Saves a two-dimensional array as a table.

[Clean] Remove row from array table (0) on index (0)

Removes a specific row from a table.

Selector

[Get] Selected row on table (0)

Obtains the index position of the table row selected.

[Dump] Unselect row on table (0)

Unselects the selected row on a table.

[Dump] Select row (0) on table (0)

Selects a specific row on a table.

Transactions

Transactions blocks can invoke configurable or native transactions, which allows the client to consume services via the internet.

Error event

On transaction (this) fail with timeout

Event triggered by timeout error. This block masks the error branch configuration of transaction steps for the timeout event LOCAL UA269.

On transaction (this) fail with no connection

Event triggered by no connection error. This block masks the error branch configuration of transaction steps for the no connection event LOCAL UA233.

Execute

Execute transaction ()

Executes a synchronous transaction and waits for a response before executing the next step. If an error occurs, it looks for execution-related events (or global events) and interrupts the process.

Execute async transaction () with next (" ") and message (" ")

Executes an asynchronous transaction. Does not wait for a response before executing the next step. Optionally, you can set a next step and specify a message to obtain when the transaction is finalized.

Services

Dynamic blocks generated upon creation of a configurable transaction.

Call APIs

Call API blocks are related to the mechanism that calls APIs of custom functionalities integrated with the platform. Since Call APIs are implemented natively for each platform (web or mobile), the ability to use them depends on the permissions granted in each binary. These permissions are validated (through AVAILABILITY) before the call is executed.

Result Fail

On call API (this) fail with error (code)

Event triggered when the call API ends with an unexpected result (any result other than 000). The event returns the error code specified for each call API.

Execute

Execute call API ()

Executes a call API function.

Execute call API () and response code

Executes a call API function and returns the response code.

Execute call API <> and response success

Executes a call API function and returns a boolean upon success code. Returns true if the result is 000, otherwise returns false.

Call APIs

Dynamic subcategories and blocks generated upon creation of Call APIs in the middleware. Contact your admin to obtain information about each specific call API and its configuration.

Errors

Error blocks contain the error handling mechanism, which can execute a series of actions depending on the unexpected trigger event.

On error default

Default event triggered by any error that doesn't have a specific error block assigned.

On error with type [] and code (" ")

Event triggered by an error with a specific type and code. This block allows you to select the type of error between EVENT, ERROR and LOCAL, and to enter the error code as text.

On error with []

Event triggered by a specific known error. This block allows you to select an error from a list of main errors (such as UA233, 0000, 0001, etc.).

Next

Next blocks contain the stack of actions that will try to be executed in order as soon as the process is finished.

Clean

Clean next stack commands

Clears the entire next stack. This allows you to reformulate the stack or to simply abort calling any actions.

Screen

Request next render view (" ")

Adds a screen request to the stack. This block solves the expression V{view}.

Request next render sequence (" ") into layout (" ") for view (")

Adds a sequence request to the stack. This block solves the expression V{view}|{layout}:{sequence}.

Component

Request next event (" ") for component (" ")

Adds a component event request to the stack. This block solves the expression E{component}({event}).

Logic

Request next process (" ")

Adds a legacy process request to the stack. This block solves the expression P{process}

Request next lambda (" ")

Adds a lambda process request to the stack. This block solves the expression Z{lambda}

Command

Request next command (" ")

Adds a command request to the stack. This block allows you to write expressions not yet supported or added as blocks.

In this section: