Integration input data is placed into the %EventData% variable.
Input Data Property Page |
The Input Data property page allows you to configure options that help actions identify how to process the input event data triggered by an integration.
|
|
Integration input data is placed into the %EventData% variable. |
Input Data Format
This property page is dynamic and the options displayed depend on the selected integration:
File
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Input Encoding: Specifies the encoding to use when reading the file.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.
Web Service
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.
Database
There are no options to configure for database integrations.
Email
Run actions using the Email's body content as input data: Directs the Integration Service to use the email's body contents for the input data source.
Save data to location: When enabled, directs the Integration Service to save the Email's body content to a specified location.
Location: Specifies the file system you want the Integration Service to use when saving the Email's body content. File systems or locations can include local file systems or network shares, Librarian, or a supported cloud storage location. For more information about supported cloud storage locations, see Administration Console's
File Name: Specifies the file path for the file in which you want the Integration Service to save the email's body content. You can type the folder location and file name or click Browse to locate and select the desired file. Alternatively, you can add a variable to specify the desired file or add a special character to the value you have entered.
File Encoding: Specifies the encoding to use when saving the Email's body content. The default is Unicode (UTF-8).
Run actions for each Email attachment and use the attachment's content as input data: Directs the Integration Service to use the email's attachments for the input data source. The Email integration's action(s) will run for each attachment, using each attachment as the input data source.
Save email attachment(s) content to file system: When enabled, directs the Integration Service to save the email attachment(s) to a specified location.
Location: Specifies the file system you want the Integration Service to use when saving the email attachments. File systems or locations can include local file systems or network shares, Librarian, or a supported cloud storage location. For more information about supported cloud storage locations, see Administration Console's
Folder: Specifies the folder in which you want the Integration Service to save the email attachments. You can type the folder location and file name or click Browse to locate and select the desired file. Alternatively, you can add a variable or add a special character to the value you have entered.
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Input Encoding: Specifies the encoding to use when reading the email attachment(s). Available when you have enabled Run actions for each Email attachment and use the attachment's content as input data.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.
Network Socket
Encoding: Specifies the encoding method to use when reading the message.
Stop Reading When: Specifies when the Integration Service stops reading the message.
Sequence of Characters is Received: Directs the Integration Service to stop reading the message after a specific sequence of characters has been received.
Characters: Specifies the sequence of characters that tells the Integration Service to stop reading the message.
Include sequence in input data contents: Specifies that the indicated sequence of characters are read as part of the data contents.
Number of Characters is Received: Directs the Integration Service to stop reading the message after a specific number of characters has been received.
Characters: Specifies the maximum number of characters that the Integration Service will accept in the message.
Port Becomes Idle: Directs the Integration Service to stop reading the message after the port is idle for a specified period of time.
Time to Wait: Specifies the amount of time the port can be idle before the Integration Service stops reading the message.
Socket is Disconnected: Directs the Integration Service to stop reading the message when the socket becomes disconnected.
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.
Serial Port
Encoding: Specifies the encoding method to use when reading the message.
Stop Reading When: Specifies when the Integration Service stops reading the message.
Sequence of Characters is Received: Directs the Integration Service to stop reading the message after a specific sequence of characters has been received.
Characters: Specifies the sequence of characters that tells the Integration Service to stop reading the message.
Include sequence in input data contents: Specifies that the indicated sequence of characters are read as part of the data contents.
Number of Characters is Received: Directs the Integration Service to stop reading the message after a specific number of characters has been received.
Characters: Specifies the maximum number of characters that the Integration Service will accept in the message.
Port Becomes Idle: Directs the Integration Service to stop reading the message after the port is idle for a specified period of time.
Time to Wait: Specifies the amount of time the port can be idle before the Integration Service stops reading the message.
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.
Message Queue
Input Data Format: The data contents type. When the trigger is detected, the Integration Service first processes the contents as per this format before running any actions.
Data is contained in a SOAP message: When enabled, the Integration Service expects the data to be contained in a SOAP message.