Veritran Docs

[en] The process name must be clear, specific, and concisely describe the process objective. When naming a process, consider the following best practices:

[en] The process description provides additional context to the name, explaining the purpose of the process, when it should be executed or any other relevant considerations.

[en] Processes tags help organize and find processes within the project. They can be used to identify the transaction code or API call being invoked within the process (e.g. TRX1031); and in those cases where the process serves a specific purpose, (e.g. VALIDATION, FILTER, SEARCH, NAVIGATION). When adding tags to a process, consider the following best practices:

[en] Lambda variables are used during the execution of the process. Unlike parameters, these variables can be used anywhere within the lambda process and are not limited to a specific function. When creating variables, consider the following best practices:

[en] Functions allow you to encapsulate parts of a process logic, improving reusability, readability, and code organization. Each function can receive input parameters, process information, and return a value. Functions are local to the lambda process in which they are defined.

[en] Functions share many principles with other structures like processes and variables. When creating functions, consider the following best practices:

[en] Parameters allow information to be passed to functions. Using parameters enables better encapsulation and decoupling of specific logic. The best practices outlined for variables also apply to parameters, as well as the following: