Experience Manager Forms Data Integration provides an Azure storage configuration to integrate forms with Azure storage services. The Form Data Model can be used to create Adaptive Forms that interact with Azure server to enable business workflows. For example:
Before executing these steps, ensure that you have an Azure storage account and an access key to authorize the access to the Azure storage account.
After creating the Azure storage configuration, you can create the Form Data Model. Specify the folder that contains the Azure configuration in the Data Source Configuration field while creating the Form Data Model. You can then select the configuration from the list of configurations that exist in the specified folder name.
After creating the Form Data Model and data model objects, you can add Azure services to the Form Data Model.
To add Azure services:
In the Edit mode, select the services from the Services section in the left pane and tap Add Selected. The selected services display in the Services tab of the Form Data Model.
In the Services tab, select the service and Edit Properties. Based on the service, define the input or output model objects for the service.
Tap Save to save the form data model.
The following table describes the available Azure services:
|Get Blob from Azure||Retrieve data stored as a Blob in Azure storage using an ID or a name|
|Get Blob with binaries URL from Azure||Retrieve data stored as a Blob with URL for binaries in Azure storage using an ID or a name|
|Save Blob in Azure||Use a Blob ID to save data in Azure storage|
|Update Blob in Azure||Use a Blob ID to update data in Azure storage|
|Retrieve list of Blob IDs from Azure||Retrieve a list of Blob IDs from Azure based on the number defined in the input request.|
|Retrieve SAS URLs for Blobs from Azure||Retrieve SAS URLs for Blobs from Azure based on Blob IDs in the input request.|
|Delete Blob from Azure||Use a Blob ID to delete data from Azure storage|
To define a data model object property as a search key:
After defining data model object properties as search keys, the hash values are stored in Azure index tags and Base64 encoded values are stored in the Azure metadata.
Only 10 search keys are allowed per Azure entity since Azure only allows 10 tags per Blob and properties value marked as search keys are stored in Azure index tags after hashing.