How to Integrate the Application with Azure and AWS Cloud Services
Required Permissions
This section requires the Application Designer permission from your Domain's administrator.
Check What are the Design Tasks? to learn more about permissions to work with Design Mode and other tools.
Learn how to create the Custom Action that execute inside your application Microsoft Azure Functions or AWS Lambda Functions.
Note
This document explains how to configure in eLegere already existing Microsoft Azure Functions or AWS Lambda Functions inside your application as Custom Actions. This document doesn't teach you how to create Azure Functions or ASW Lambda Functions.
If you want to learn how to create Azure Functions or AWS Lambda Functions, check their documentation websites.
Refer to their respective documentation websites also to retrieve the required values for the parameters in this tutorial.
Configure an AWS Lambda Function¶
Learn how to configure a Custom Action to launch an AWS Lambda Function.
-
In Design Mode, click on the icon in the upper-right corner of any panel.
The action leads to the Custom Actions panel.
-
Click on the Enable Module toggle switch to activate the Custom Actions in your application.
-
Click on the New Action drop-down menu button.
-
Choose Invoke AWS Lambda from the list of Custom Actions types. This action creates a Custom Action.
This action creates the Invoke AWS Lambda Custom Action to be configured.
-
Insert in the Info section the required information.
- (1) Name Insert a name for the Custom Action.
- (2) Description
optional
Insert a description for the Custom Action. - (3) Manual If enabled, the Users launch this Custom Action manually. If disabled, choose at (4) Event a triggering condition to launch the Custom Action. (By default, the toggle switch is enabled.)
- (4) Event If (3) Manual is disabled, choose a trigger condition from the drop-down list.
Event - Triggering Options
For the Event option, when the Manual toggle-switch is disabled, choose a moment when the Custom Action runs.
PRE ROW INSERT Before inserting a row.
POST ROW INSERT After a row's insertion.
PRE ROW UPDATE Before any changes apply to a row.
POST ROW UPDATE After having edited a row.
PRE ROW DELETE Before deleting a row.
POST ROW DELETE After having deleted the row.
PRE ATTACHMENT INSERT Before uploading an attachment to a row.
POST ATTACHMENT INSERT After having uploaded an attachment to a row.
POST MASTER INSERT After having inserted a row on the Master table.
POST MASTER UPDATE After having saved an edited row on the Master table.
POST MASTER DELETE After having deleted a row on the Master table.
- (5) Async Enable to run the Custom Action in the background instead of waiting for its completition to use the application. (By default, the Async toggle-switch is enabled when (3) Manual is enabled. Otherwise, the toggle-switch is disabled.)
- (6) Execution
optional
Click to open the Formula Editor. Insert a Formula to define the conditions for executing the Custom Action. - (7) Visibility
optional
Click to open the Formula Editor. Insert a Formula to define the conditions to display the Custom Action in the application. - (8) Refresh
optional
If enabled, the application refreshes the data on the table when the Custom Action has finished to run. - (9) Icon
optional
Choose an icon for the Custom Action. - (10) Context Decide if the User launches the Custom Action from the Custom Actions drop-down menu in the application or from the Row's Options (). Disabled if (3) Manual is disabled.
- (11) Table Choose the table where the Custom Action runs.
-
In the Parameters, insert the requested values.
Question
Check the AWS documentation to learn how to retrieve the required values.
If you aren't either a developer or administrator, ask the parameters' values below to who concerns.
- (1) The URL of the AWS Lambda Function's endpoint.
- (2) The method of the request: GET or POST.
- (3) The Access Key as first part of the access credentials.
- (4) The Secret Key as second part of the access credentials.
- (5) The Service executing the action on the Amazon Web Services.
- (6) The Region of the AWS server executing the action.
- (7) If the Use Context toggle switch is enabled, the Custom Action will pass the row's context with its values with the request.
- (8) Provide the Body: all the keys and values that the AWS Lambda Function needs. (Click on New to define a value and a key. Click on the Reset button to clear all the values and keys from the section.)
-
This step is optional. Follow this step if you want to block the use of one application while the Powershell Script Custom Action is running.
In the Application Lock, click on the Enabled toggle switch to enable the application's locking. (By default, Enabled is turned OFF.)
Choose one or more applications from the drop-down list to lock while the Custom Action is running.
-
When you have completed the configuration, click on the Save button () in the top-left corner to save the Invoke AWS Lambda Custom Action.
Success
You have configured an AWS Lambda Function as Custom Action in your application.
Tip
If you want to disable the Invoke AWS Lambda Custom Action without deleting it from the Application, click on the toggle switch next to the Custom Action's name to hide it from the users.
Tip
If you want to delete a Invoke AWS Lambda Custom Action, click on the Remove in the Info section.
A window will ask for confirmation. Click Yes to confirm the deletion. (Click No to abort the deletion.)
Click on the Save button () in the top-left corner to save the deletion.
Configure a Microsoft Azure Function¶
Learn how to configure a Custom Action to launch an Microsoft Azure Function.
-
In Design Mode, click on the icon in the upper-right corner of any panel.
The action leads to the Custom Actions panel.
-
Click on the Enable Module toggle switch to activate the Custom Actions in your application.
-
Click on the New Action drop-down menu button.
-
Choose Invoke Azure Function from the list of Custom Actions types. This action creates a Custom Action.
This action creates the Invoke Azure Function Custom Action to be configured.
-
Insert in the Info section the required information.
- (1) Name Insert a name for the Custom Action.
- (2) Description
optional
Insert a description for the Custom Action. - (3) Manual If enabled, the Users launch this Custom Action manually. If disabled, choose at (4) Event a triggering condition to launch the Custom Action. (By default, the toggle switch is enabled.)
- (4) Event If (3) Manual is disabled, choose a trigger condition from the drop-down list.
Event - Triggering Options
For the Event option, when the Manual toggle-switch is disabled, choose a moment when the Custom Action runs.
PRE ROW INSERT Before inserting a row.
POST ROW INSERT After a row's insertion.
PRE ROW UPDATE Before any changes apply to a row.
POST ROW UPDATE After having edited a row.
PRE ROW DELETE Before deleting a row.
POST ROW DELETE After having deleted the row.
PRE ATTACHMENT INSERT Before uploading an attachment to a row.
POST ATTACHMENT INSERT After having uploaded an attachment to a row.
POST MASTER INSERT After having inserted a row on the Master table.
POST MASTER UPDATE After having saved an edited row on the Master table.
POST MASTER DELETE After having deleted a row on the Master table.
- (5) Async Enable to run the Custom Action in the background instead of waiting for its completition to use the application. (By default, the Async toggle-switch is enabled when (3) Manual is enabled. Otherwise, the toggle-switch is disabled.)
- (6) Execution
optional
Click to open the Formula Editor. Insert a Formula to define the conditions for executing the Custom Action. - (7) Visibility
optional
Click to open the Formula Editor. Insert a Formula to define the conditions to display the Custom Action in the application. - (8) Refresh
optional
If enabled, the application refreshes the data on the table when the Custom Action has finished to run. - (9) Icon
optional
Choose an icon for the Custom Action. - (10) Context Decide if the User launches the Custom Action from the Custom Actions drop-down menu in the application or from the Row's Options (). Disabled if (3) Manual is disabled.
- (11) Table Choose the table where the Custom Action runs.
-
In the Parameters, insert the requested values.
Question
Check the Microsoft Azure documentation to learn how to retrieve the required values.
If you aren't either a developer or administrator, ask to who concerns the parameters below.
- (1) The URL for the HTTP request triggering the Azure Function.
- (2) The request method: GET or POST.
- (3) The Auth Key is the key required to access and launch the Azure Function.
- (4) If the Use Context toggle switch is enabled, the Custom Action will pass the row's context with its values with the request.
- (5) Provide the Body: all the extra keys and values that the Azure Function might need. (Click on New to define a value and a key. Click on the Reset button to clear all the values and keys from the section.)
-
This step is optional. Follow this step if you want to block the use of one application while the Invoke Azure Function Custom Action is running.
In the Application Lock, click on the Enabled toggle switch to enable the application's locking. (By default, Enabled is turned OFF.)
Choose one or more applications from the drop-down list to lock while the Custom Action is running.
-
When you have completed the configuration, click on the Save button () in the top-left corner to save the Invoke Azure Function Custom Action.
Success
You have configured an Azure Function as Custom Action in your application.
Tip
If you want to disable the Invoke Azure Function Custom Action without deleting it from the Application, click on the toggle switch next to the Custom Action's name to hide it from the users.