On-screen actions - Native block

The native block provides the actions to communicate like SMS, email, and call.

native block

Call

This action allows you to call the configured phone number which could be a default number or fetched from an input control or sheet column.

  • Phone number: This is the phone number in the valid format that would be used. In case you want to enter multiple numbers they would be comma-separated or fetched using the keywords.

You can then specify a condition as to when to execute the action and which environment. An Action Unique name is important that would help you identify the tasks in the flow.

SMS

This action allows you to send an SMS to the configured phone number which could be a default number or fetched from an input control or sheet column.

  • Phone number: This is the phone number in the valid format that would be used. In case you want to enter multiple numbers they would be comma-separated or fetched using the keywords.

  • Message: Is the message to be delivered to the given phone numbers.

You can then specify a condition as to when to execute the action and which environment. An Action Unique name is important that would help you identify the tasks in the flow.

Email

This enables you to configure the fields like email subject, recipient, and body of an email action, which is typically required as a confirmation on completion of some activities.

  • Subject: This is the Subject line for your email message. You can use keywords to pick up the subject line input or provided from some form control.

  • Body: This is the actual body or message to be sent to the intended user. You can use keywords to pick up the subject line input or provided from some form control.

  • Enter Recipient(s): This is the recipient email that you can enter or select from the keywords.

You can then specify a condition as to when to execute the action and which environment. An Action Unique name is important that would help you identify the tasks in the flow.

Install Microapps

This enables you to install the Microapps using the Action flow. This can be useful in scenarios where you want conditional installation or any other scenario.

install microapps

  • To use the feature, under Native block , select Install Microapps and click Continue.

  • Under Action button ID , select the MicroApp to install from the App List and click Continue .

  • You can also specify a condition when to execute the action and which environment. An Action Unique name is important that would help you identify the tasks in the flow. Click Finish .

ENDACTIONFLOW

The ENDACTIONFLOW is a native block, on-screen action which is used to terminate the whole action flow available under it.

The ENDACTIONFLOW is used ordinarily in the action flow with provided some conditions. When the condition(s) is satisfied or found true, the whole further action flow gets terminated.

NOTE: After using BRANCH logic of on-screen action, you cannot find the ENDACTIONFLOW native block of on-screen action, under any leg of the branch action block.

ENDBRANCH

The ENDBRANCH is a native block, on-screen action which is used to terminate further actions in any branch action flow.

The ENDBRANCH is used ordinarily in the action flow under branches with provided some conditions which result in TRUE/FALSE to decide whether to execute this action or not. When the condition(s) is satisfied or found true, the whole further action flow of that particular branch gets ended.

So, if two branches are executing all together and one of them is met with true condition for ENDBRANCH action then that particular branch leg with all other actions further, will not execute and will continue from where all the branches are combining.

Example:

In the above image, there are two branches, each having ENDBRANCH action. Now, whichever ENDBRANCH action meets the provided condition, that particular leg of the branch will terminate and it will exit from the leg and continue the action flow out of that branch leg.

So, if ENDBRANCH condition is true for branch_2 then, branch_1 will execute, branch_2 will skip and combine with other branches and execute the toast action.

NOTE: Until and unless the BRANCH action block is used, you cannot find or use the ENDBRANCH action block other than inside the branch leg in the action flow.