Block Step Data
Last Update há um ano
Blocks are the building blocks of the flow's business logic. A user can use these blocks in any order to build a meaningful flow. Nodezap provides you with numerous blocks serving various functions.
Each block has to be provided with its basic configurations for the smooth functioning of the block and flow. The block configurations can also use values returned by the previous blocks in the flow. Block Step data dialog is visible on the right-hand side of the configuration dialog. On clicking any data point in the dialog the value gets populated in the input which is in focus (the input on focus should be of reference type). While the execution of the flow, at runtime these values will be used in these places appropriately. Based on the type of value the input expects, all other data points in the dialog will be greyed out (i.e. disabled) and cannot be used. Block step data dialog also helps users to understand the overall logic of the flow defined by appropriately displaying the results of each block, which helps the user to understand and configure the current block appropriately.
Apart from having the block's result set, the block step data also has the context of the execution of the flow which the admin can utilize while configuring the flow. The variables available are as follows:
This variable stores the user and the current flow context.
- The user object has the reference of the current user whose action has triggered the execution of this flow. For eg: A user creates a record, this variable will be populated with the user's details at runtime.
- The roleID is populated by the current user's access role as defined in the Roles section of the app.
- The appID gets populated by the current app's id in which the flow is defined.
- The controlID gets populated by the current flow's id.
- Each execution of the flow gets a randomly generated requestID which can be uniquely used to determine the execution of the flow.
This variable has a list of all environment variables defined by the app admin. These variables can be used anywhere in the flow and will be populated at runtime while the flows execute.