You can assign values to scalar variables in integrations with an assign action.

You can translate a message to or from the Electronic Data Interchange (EDI) format in an integration with the B2B action.

1. Add a B2B action to the integration in either of the following ways:
   • On the right side of the canvas, click Actions and drag the B2B action to the appropriate location.
   • Click at the location where you want to add the for-each action, then select B2B.
   The Configure B2B Action Wizard is displayed.
2. Enter a name and optional description.
3. Select how you want to use the B2B action, then click Continue.
   • B2B Trading Partner mode: Select to include B2B trading partner profiles and message persistence in your integration.
   • Standalone mode: Select to use the B2B action independently in your integration without a B2B trading partner profile or message persistence.
4. If you select B2B Trading Partner mode, follow these wizard steps:
   1. Select the B2B message direction for this B2B action:
      • Inbound: The B2B message is sent from the trading partner to the host trading partner (partner where Oracle Integration is installed).
      • Outbound: The B2B message is sent from the host trading partner (partner where Oracle Integration is installed) to the trading partner.
   2. Select the operation for the B2B action to perform based on the direction.

      If You Selected...	Then Select an Operation...
      Inbound	Fetch Message: Fetches a B2B business message from the persistence store, given a message identifier. Translate: Translates an inbound EDI message to an Oracle Integration message. Mark As Error: Marks a B2B business message with a failed processing status.
      Outbound	Translate: Translates an Oracle Integration message to an outbound EDI message. Mark As Error: Marks a B2B business message with a failed processing status. Fetch raw messages: Fetches a B2B business message payload from persistence stored for processing.

   3. If you select either of the following, the Select Data Format page is displayed.
      • Inbound message direction and Fetch Message operation
      • Outbound message direction and Translate operation

      1. Select the document definition for the B2B action to handle, and click Search to refresh the page.
      2. Select the document standard, version, and type.
      3. Click >.
   4. Review your selections on the Summary page, then click Done.
5. If you select Standalone mode, follow these wizard steps:
   1. Specify the message translation and document format details.

      Element	Description
      Select the direction in which to translate the message	Inbound EDI message to Oracle Integration message: When an integration receives an EDI document from a business partner, it is considered an inbound document (an EDI document is translated to XML). Oracle Integration message to outbound EDI message: When an integration sends an EDI document to a business partner, it is considered an outbound document (an EDI document is generated from XML).
      Document Standard	Select the document standard to follow when exchanging business documents between partners. Custom Delimited EDIFACT FixedLength OAG X12 X12HIPAA
      Document Version	Select the version of the document standard to use.
      Document Type	Select the document type (for example, purchase order, invoice, shipping notice, or others). The document types available for selection are based on the document version you selected.
      Document Definition	Select the document definition that you created on the Documents page. For EDIFACT, X12, or X12HIPAA, you can also select Standard. See Create Custom Document Definitions in Using B2B for Oracle Integration 3.
      EDI Character Encoding	Select the character encoding that the inbound EDI document is expected to use.
      Perform validations on input data	Yes: Validates the structure and data of an inbound EDI message. Enabling message validation has an impact on performance. If errors are found, translation does not succeed. No: Errors are ignored during translation and the message is passed through in its current format. You can override this setting at runtime with the Validate request element in the mapper.

   2. Click Continue.
   3. Specify to optionally upload sample data to test that translation is successful.

      Element	Description
      Run a test translation with sample data (optional)	Select or drag and drop a sample file. To test inbound EDI message translation, upload an EDI document. To test outbound EDI message generation, upload an XML document.
      Translate	Click to translate your sample data. Output is displayed in the Output of translation field. Any errors are displayed in the Error in translation field.

   4. Click Continue.
   5. Review your selections on the Summary page, then click Finish.

You can incrementally build a message payload from one or more existing payloads with the data stitch action. The data stitch action provides a Configure Stitch panel that enables you to assign values to variables.

You can convert a message to or from HL7 format with a healthcare action in an integration. The healthcare action converts native inbound HL7 messages into Oracle Integration XML payloads for use in your integrations and generates native HL7 messages from Oracle Integration XML payloads to send to external applications that support HL7.

1. Add a healthcare action to the integration in either of the following ways:
   • On the right side of the canvas, click Actions and drag the Healthcare action to the appropriate location.
   • Click at the location where you want to add the healthcare action, then select Healthcare.
   The Configure healthcare action call wizard is displayed.
2. Enter the following details:

   Element	Description
   Name	Enter a name.
   Description	Enter an optional descriptions for what this action does.
   Operation	Select an operation to perform: Convert message reference to document: Use this operation to identify the incoming message type and version. This operation returns a reference to a translated message and metadata needed to route the integration to an appropriate child integration to process the message. When you call the operation, you need to specify a list of HL7 documents with which you want to match. Match and translate inbound message: Use this operation to convert inbound HL7-formatted messages into XML format. Specify the documents you want this action to receive. These are the documents that you configured during design time. This operation takes a raw HL7 message off the wire, parses it, and matches it with the document definition you select in the Choose documents section. The message is then converted to an Oracle Integration XML payload. Translate to outbound message: Use this operation to convert an XML payload message to an outbound HL7 message.
   Choose documents This field is displayed if you select the Match and translate inbound message operation.	Select all the HL7 message definitions that you expect to receive on the port number you configured for your MLLP Adapter connection. This integration receives and routes all messages sent to that port number. Documents that are not selected are ignored. If you created the integration in a project, only documents available in that project are visible for selection.
   Document This field is displayed if you select the Convert message reference to document or Translate to outbound message operation.	Select the document to use. If you created the integration in a project, only documents available in that project are visible for selection.

   For example:

   • If you select Match and translate inbound message, the selected ADT_A08 message document is converted from HL7 format to an Oracle Integration XML-formatted message.

     
     
     

   • If you select Translate to outbound message, the selected ADT_A08 message is converted from an Oracle Integration XML message to an HL7-formatted message for delivery to an external application that supports HL7.

     
     
     

   • If you select Convert message reference to document, the message reference is converted into a mappable payload. This operation returns the contents of the HL7 message as a variable in your integration that is ready to use in the business logic and mapper of your integration. The variable appears on the source side of the mapper.

     
     
     

3. Click Finish.

You can log messages to the activity stream and diagnostic logs by adding the logger action at any point in the integration. You create a log message in the logger action that is a static message or variable-populated message.

You can add placeholder notes similar to sticky notes to an integration. For example, you have not yet defined an invoke connection and want to add a placeholder note in the integration indicating that you plan to define the invoke connection later. Another integration developer reads that note and may add the invoke connection or the note reminds you to add the invoke connection at a later time when you again work on the integration.

1. Add a note action to an integration in either of the following ways:
   • On the side of the canvas, click Actions and drag the Note action to the appropriate location.
   • Click at the location where you want to add the note action, then select Note.

   • Click Edit under Configure Note to enter a name and optional description for the note action.

2. Enter your notes, then click Save. You can add up to 256 characters.
3. Hover over the icon to display the note text.

You can send a notification email to relevant users at specific points in the processing of an integration. You can set the to, from, and subject parts of an email. You can create the body part of an email using parameters defined in the Expression Builder. You can also add attachments to the email if your integration includes them. The total size limit on a notification email is 1 MB for Oracle Integration and 2 MB for Oracle Integration Generation 2. Both the email body and attachment are considered in calculating the total size.

1. Add a notification action to an integration in either of the following ways:
   • On the side of the canvas, click Actions and drag the Notification action to the appropriate location.
   • Click at the location where you want to add the notification action, then select Notification.
2. Click Edit under Configure Notification to enter a name and optional description for the notification action.
3. Click the To field.
   This opens the Sources tree for defining an expression and a second To field for editing immediately after the first field.
4. Manually enter an email address, select from the drop-down list, or drag an element from the Sources tree to the To field:

   
   
   

5. Click the From field.
   This opens a second From field for editing immediately after the first field.

   
   
   

6. Manually enter an email address, select from the drop-down list, or drag an element from the Sources tree. For this example, an email element is dragged from the Sources tree.
   You can provide an email address in the From field that is approved as the sender for service failure alerts, system status reports, and integration error reports. You configure the approval email address to use in the From field on the Notifications page that is accessible by selecting Settings, and then Notifications.

   Note:

   If you send emails with the notification action and the From address is not one of the approved senders configured on the Notifications page, the From address defaults to the approved sender address of no-reply@mail.integration.region.ocp.oraclecloud.com. For example, if your region is Ashburn, the address is no-reply@mail.integration.us-ashburn-1.ocp.oraclecloud.com. See Configure Notification Emails.

   See Send System Status Reports with Notification Emails.

7. Click the Subject field.
   This opens a second Subject field for editing immediately after the first field.
8. Manually enter a subject in plain text, select from the drop-down list, or build an expression from the Source or Functions tree. To drag a function, ensure that you first select Switch to Developer View .

   For this example, a concat function is selected for use from the Functions section.

   concat ( 'Hello', name )

9. Click the Body field.
   This opens a second Body field for editing immediately after the first field.
10. Enter a message using plain text and plain HTML formatting that you create in a separate HTML editing tool and paste into this field or parameters that you create in the table immediately after this field. After creating parameters, enter them inside { } brackets.

    <html>
    <body>
    <p>Hello <strong><span style="color: #2925BF;">{name},</span></strong></p>
    <p><span style="color: #298022;"><strong>Welcome to Oracle Integration!</strong></span></p>
    </body>
    </html>

11. Click + to add parameters.
12. Enter a parameter name and description or build an expression.
13. Click + to add attachments.
14. Select the attachments to add.
15. In the Attachments section, click + to open a page to select an attachment file.
    You can edit or delete attachments once added. Examples of attachments may include file reference attachments that are available for selection:

    • An attachment from a REST Adapter connection
    • A file reference from a stage file write operation
    • A file reference from an FTP Adapter download operation
16. When complete, the Configure Notification panel looks as follows for this example:
    
    

    

    
    
17. Click Save.

The wait action enables you to delay the processing of an integration for a specified period of time. Use this action in schedule integrations, asynchronous integrations, synchronous integrations, and fire-and-forget integrations. A typical use for this action is to invoke a specific operation at a certain time. You can specify literal values or build XPath expressions that you can configure with property values during runtime.