Skip to main content

Veritran Docs

Glosario

Este glosario agrupa y define los términos de las categorías Construcción, Operación y Administración.

Plataforma Veritran

Administración de identidades (IDM)

Consola que permite crear, buscar y administrar las organizaciones y los usuarios.

Audit

Sistema que obtiene un historial de las actualizaciones de las entidades en otros sistemas o consolas. Realiza una auditoría en las entidades de negocio, hace un seguimiento de cómo estas se modificaron y describe cómo esos cambios repercuten en las operaciones de la plataforma.

Blue-green

Característica que te permite probar los cambios en un entorno controlado al implementarlos en una cantidad reducida de usuarios para minimizar los riesgos.

campaña

Información relacionada con los productos o servicios proporcionados al usuario de la app.

código de evaluación

Identificador único para una evaluación de transacción.

código de respuesta de una transacción

Códigos configurados para identificar la respuesta del flujo de una transacción y para establecer un mensaje que el usuario de la app ve durante la respuesta.

código de transacción

Identificador único para una transacción.

Consola de administración de reglas de negocio (BRM)

Sistema que define y aplica las reglas de negocio en las transacciones al evaluarlas y aprobarlas o rechazarlas en función de determinadas condiciones.

construir

Generación del binario de una app.

detección de alteración

Capacidad de un dispositivo para detectar si está en curso un intento activo de comprometer la integridad del dispositivo o sus datos asociados.

detector de alteración

Medida preventiva para evitar cualquier intento de alteración de una aplicación sin consentimiento.

ejecutores

Máquina virtual utilizada para generar el binario de una app.

[en] animation

[en] Effects used to change specific attributes of a component at a certain moment or upon a specific action.

[en] API REST

[en] Invoking an external service via a REST protocol.

[en] API SOAP

[en] Invoking an external service via a SOAP protocol.

[en] Application Programming Interface ([en] API)

[en] A software intermediary that allows two applications to communicate.

[en] application themes

[en] Preset packages of graphical appearance details, such as color, size, fonts and backgrounds, which define the look & feel of a screen.

[en] app template

[en] Predesigned app that offers a complete user interaction flow and is oriented towards a specific use case.

[en] app version

[en] Unique state of an application that is identified by a unique number. This number is assigned automatically in increasing order and corresponds to new developments in the app.

[en] attributes

[en] Characteristics of a component configured in the Attributes Editor of the Visual Builder.

[en] block

[en] In Lambda processes, blocks represent a variety of functions and operations that can involve transactions, registers, arrays, conditionals and more.

[en] branch

[en] Copy of an app or module used to develop and test changes made to screens and processes of an app in an independent manner.

[en] branch update

[en] Action that brings changes from the main branch to another branch.

[en] canvas

[en] Simulator that allows you to see what the screen of your app will look like while adding or removing components and setting their attributes.

[en] commit

[en] The action that brings changes made in a branch to the main branch. Each commit generates a new app version.

[en] communication protocol

[en] Set of rules that determines transmission of data between services within the same network. Also known as network communication protocol.

[en] component

[en] Element used to build a screen using the drag & drop feature that may have different functionalities depending on its function.

[en] component-type interface

[en] Interface that will be displayed as a component in the Visual Builder. To use it, the module must be linked to the app in the app dependencies.

[en] configurable transaction

[en] Transaction configured with low-code and published from Studio, interpreted and executed by the middleware.

[en] conflict

[en] Changes or differences between the main branch and another branch.

[en] container component

[en] Component that includes other several components within

[en] context

[en] Sum of app or module and a branch a user is working on in a specific environment.

[en] dependencies

[en] Studio feature that allows the user to link a module to an app or to another module to be able to use the module's content.

[en] drag & drop

[en] Feature that allows you to grab an object and place (drop) it into a different location.

[en] extensions

[en] Different types of pre-built elements – such as app templates or feature templates - available at Veritran Marketplace that accelerate the app building process.

[en] extensions subscription

[en] Acquisition of extensions in Veritran Marketplace to be used in a Studio environment to accelerate the app building process.

[en] external service

[en] Service that solves the business logic of a transaction by invoking API services (third-party services) via a REST or SOAP communication protocol.

[en] feature branch

[en] Branch created to work on a copy of the main branch without affecting the productive version of the app.

[en] feature template

[en] Type of extension that solves a specific business or cross-market functionality with a limited flow of interaction.

[en] function

[en] Logic executed within the steps of a process. Each step of a process can contain only one function.

[en] global parameters

[en] Configuration information whose scope applies to your Studio environment.

[en] global registers

[en] Registers available for all the apps within the same Studio environment. Their numeric IDs go from 1 to 1000.

[en] hotfix

[en] Immediate patch or fix applied to correct defects found within the app.

[en] hotfix branch

[en] Branch containing a hotfix to avoid making changes in the main branch.

[en] interface

[en] Functionality that communicates a module with an app or another module. It is required to use a module's content.

[en] lambda

[en] Blocks of code that can be assigned to variables, passed as an argument, or returned from a function call.

[en] lambda process

[en] Process built in the Lambda Editor through the use of a visual programming language.

[en] layout template

[en] Reusable feature configuration to enable adding instances to different components.

[en] legacy process

[en] Process built using the form method. Processes are currently created using the Lambda Editor.

[en] library component

[en] Reusable component that can be added to screen by duplicating it or referencing the original element.

[en] line

[en] Together with stations, a line is a platform object that manages in and out traffic from the Core Server. Lines define connections to the node, and works as an entry and exit port.

[en] local registers

[en] Registers that are specific to an app or module. Their numeric IDs can range from 1000 upwards.

[en] main branch

[en] Stable, read-only branch of your app or module from which new branches are created.

[en] main module

[en] Module that represents the app itself in the branch navigator.

[en] middleware

[en] Software that provides common services and capabilities to applications outside of what’s offered by the operating system.

[en] Middleware

[en] Set of processes that runs over VT-NET runtime system and routes, orchestrates and integrates client’s and third parties’ APIs to solve transactions initiated by different devices and apps.

[en] mobile app

[en] App that is accessible using a mobile device.

[en] module

[en] Reusable configuration unit that you can create for a screen or for a component.

[en] native transaction

[en] Former type of transaction created on the middleware. It can be invoked in Studio.

[en] non-fatal issue

[en] Controlled configuration issues that might affect an app's functioning.

[en] omnichannel

[en] Approach which streamlines all the customer interactions across multiple touchpoints in a unified way to deliver a consistent experience across different devices and channels.

[en] parameter

[en] Global configuration information given to the different components of the platform. It consists of an ID, type of information stored, a value, and scope (global or site).

[en] private extension

[en] Extension with restricted access to specific users.

[en] process

[en] Sequences of steps that add logic to an app. Each step runs an operation or function.

[en] Quickpublish

[en] Studio feature that allows you to generate and publish only the changes made to a process or screen.

[en] register

[en] Previously called token. Data repository where you can store any value, relating it to a numeric identifier.

[en] resource

[en] Images, icons, fonts, video files, audio files, widgets or any type of file that can be uploaded to the different systems of the VT platform.

[en] REST service

[en] HTTP communication protocol to involve services in a specific environment.

[en] screens

[en] Visual areas with distinct content that can be arranged to form a site view.

[en] screen-type interface

[en] Interface that will be displayed as a screen or screens flow in the Visual Builder. To use it, the module must be linked to the app in the app dependencies.

[en] simulator

[en] Canvas that allows the to simulate the look and feel of the screens of an app by using the drag & drop feature.

[en] site parameters

[en] Configuration information whose scope applies only to your current app.

[en] site views

[en] Groups of screens that have the same layout.

[en] snapshot

[en] Exact picture of an application that captures values for arrays and registers during its execution.

[en] SOAP service

[en] XML communication protocol to invoke services in a specific environment.

[en] station

[en] Together with lines, a station is a platform object that manages in and out traffic from the Core Server. Stations are associated with a line and take messages with their requests or responses and places them in the next process' queue.

[en] tracking

[en] Feature that allows you to collect and visualize data on how users interact with your app by setting specific tracking events and user properties.

[en] transaction

[en] Services executed in the middleware of the Veritran platform used to implement complex business logic in your app, consume databases and invoke external services and processes.

[en] universal app

[en] App that can be accessed through an internet browser or from mobile devices.

[en] variable

[en] Functionality that stores values that are then used in a transaction flow.

[en] Veritran Marketplace

[en] Digital repository for users to consume and share extensions that accelerate the building of apps in Veritran Studio.

[en] VT service

[en] Association of a VT service with a native transaction to invoke services when executing the transaction.

[en] web app

[en] App that is accessible using any web browser.

experimento Blue-Green

Prueba de la versión de una app o plataforma en un entorno controlado.

experimento cerrado

Todo experimento detenido en el sistema.

experimento del sistema

Experimento Blue-Green que permite probar una versión nueva de la plataforma.

experimento de negocio

Experimento Blue-Green que prueba las actualizaciones en un producto de la plataforma.

Inicio de sesión único (SSO)

Servicio de autenticación para iniciar sesión en diferentes plataformas o sistemas con un nombre de usuario único y una contraseña.

lista negra de dispositivos

Lista de dispositivos no tienen permitido operar la app a fin de evitar el fraude.

mapeo de código de respuesta

Proceso usado para asociar los códigos de respuesta del servicio de un cliente a los códigos de respuesta de la plataforma y agregar mensajes personalizados.

Mobile Builder

Consola utilizada para generar y administrar apps móviles, y visualizar y configurar los parámetros de la app, los entornos y sus productos asociados, las versiones de la plataforma y los ejecutores usados para generar la app.

nodo azul

Nodo de producción.

nodo verde

Nodo que recibe las actualizaciones nuevas primero. Este no es el nodo de producción.

origen

Origen de la configuración de la API de la entidad.

perfil

Recopilación de la configuración asociada a un usuario cuyos permisos e información están configurados en la plataforma de Veritran.

Perfil de VT-NET

Perfiles asignados a los usuarios de la plataforma que tienen permisos para ejecutar los comandos en Operator.

proceso de authorizator

Proceso de Middleware responsable de determinar la ruta que se le asignará a cada transacción, aplicar las reglas de negocio y transmitirlas a un sistema de procesamiento externo (host).

proceso de device handler

Proceso de Middleware responsable de permitir la comunicación con los diferentes dispositivos.

producto

Producto bancario en el que se aplican las reglas con las que se determina si una transacción se ha aprobado o rechazado.

regla de negocio

Regla aplicada a la lógica de una transacción que incluye las condiciones en las que se aprueba dicha transacción.

Servidor de notificaciones

Consola que permite crear, administrar y ejecutar campañas de mensajería personalizadas.

transacción configurable del host

Transacción de poco código creada en Studio que se crea de forma automática en el middleware.

transacción no permitida

Transacción que un usuario bancario no puede llevar a cabo y que se clasifica en un determinado perfil.

transacción permitida

Transacción que un usuario bancario puede llevar a cabo y que se clasifica en un determinado perfil.

versiones candidatas para el lanzamiento

Experimento Blue-Green dividido en grupos azules y verdes.

VT-NET

Tiempo de ejecución que brinda funciones de red, tales como la administración de las comunicaciones y la mensajería transaccional.

VT Operator

También llamado Operator. Herramienta usada para ingresar líneas de comando, reiniciar, detener, modificar o revisar procesos. Notifica a la plataforma sobre las actualizaciones de negocio requeridas y funciona como una herramienta de depuración.