Invoke Configuration Page

Enter the configuration values for your integration.

Publish Events To Topic

If you selected Publish Events To a Topic with Custom schema, Publish Events To a Topic with Event Grid schema, or Publish Events To a Topic with Cloud schema on the Basic Info page, the following options are displayed.

Element Description
Select a Topic Select a topic name to publish events.
Do you want to specify the message structure?
  • Click Yes to provide the JSON/Avro or XML sample and publish the event in JSON/Avro or XML format.
  • Click No to publish the event in opaque (stream reference) format.
Enable payload fields

Select the check box to enable payload fields. Click Add to specify the static fields to be mapped.

Note: The Enable payload fields option is not supported for the Publish Events To a Topic with Event Grid schema action.

Enter payload fields

If you select the check box for Enable payload fields, a table appears for adding payload key fields. This field is mandatory and must not remain empty.

Select the request payload format Select the payload format.
  • Sample JSON
  • AVRO Schema
  • Sample XML

Note: Upon selecting AVRO Schema or Sample XML, note that the Enable encoding option is not applicable.

Enable encoding Select the check box to enable encoding data of the JSON payload received.

Note: If you selected the custom headers type as dynamic on the Trigger Configuration page of the Adapter Endpoint Configuration Wizard, the Enable encoding check box should be deselected.

Provide XML namespace

Select the check box and enter the XML namespace.

Note: Only a single namespace is supported.

Enter XML namespace

If you select the check box for Provide XML namespace, a text box appears for entering the XML namespace.

Enter data fields for request payload Enter a sample request payload to describe the structure of data.
Opaque (Stream Reference)

Publishes the files belonging to any format through the specified topic.

Note: The event published in the topic is Base64-encoded.

Publish Events To Domain

If you selected Publish Events To a Domain with Event Grid schema, Publish Events To a Domain with Custom schema, or Publish Events To a Domain with Cloud schema on the Basic Info page, the following options are displayed.

Element Description
Select a Domain Select a domain name to publish events.
Select a Topic Displays a list of domain topics for selection based on the domain selected.
Do you want to specify the message structure?
  • Click Yes to provide the JSON/Avro or XML sample and publish the event in JSON/Avro or XML format.
  • Click No to publish the event in opaque (stream reference) format.
Enable payload fields

Select the check box to enable payload fields. Click Add to specify the static fields to be mapped.

Note: The Enable payload fields option is not supported for the Publish Events To a Domain with Event Grid schema action.

Enter payload fields If you select the check box for Enable payload fields, a table appears for adding payload key fields. This field is mandatory and must not remain empty.
Select the request payload format
Select the payload format.
  • Sample JSON
  • AVRO Schema
  • Sample XML

Note: Upon selecting the AVRO Schema or Sample XML, note that the Enable encoding option is not applicable.

Enable encoding Select the check box to enable encoding data of the JSON payload received.

Note: If you selected the custom headers type as dynamic on the Trigger Configuration page of the Adapter Endpoint Configuration Wizard, the Enable encoding check box should be deselected.

Provide XML namespace

Select the check box and enter the XML namespace.

Note: Only a single namespace is supported.

Enter XML namespace

If you check the check box for Provide XML namespace, a text box appears for entering the XML namespace.
Enter data fields for request payload Enter sample request payload to describe the structure of data.
Opaque (Stream Reference)

Publishes the files in any format through the specified domain.

Note: The event published in the domain is Base64-encoded.