EDI for Cloud v2 Notifications activity

Introduction

An EDI for Cloud v2 Notifications activity, using its EDI for Cloud v2 connection, retrieves system messages from Jitterbit EDI based on specified filter criteria. This activity is intended to be used as a source in an operation.

Create an EDI for Cloud v2 Notifications activity

An instance of an EDI for Cloud v2 Notifications activity is created from an EDI for Cloud v2 connection using its Notifications activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing EDI for Cloud v2 Notifications activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure an EDI for Cloud v2 Notifications activity

Follow these steps to configure an EDI for Cloud v2 Notifications activity:

• Step 1: Enter a name
  Provide a name for the activity.

• Step 2: Review the data schemas
  Any request or response schemas are displayed.

Step 1: Enter a name

In this step, provide a name for the activity. Each user interface element of this step is described below.

• Name: Enter a name to identify the activity. The name must be unique for each EDI for Cloud v2 Notifications activity and must not contain forward slashes (/) or colons (:).

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

• Data schema: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  The EDI for Cloud v2 connector uses a custom Jitterbit API.

  The request and response data schemas consist of these nodes and fields:

  • Request:

    Request schema node/field	Description
    Request	Request to retrieve system messages
    page	Integer specifying the page number for pagination
    pageSize	Integer specifying the number of results per page
    partnerName	Array of trading partner names to filter by (["partnerName1", "partnerName2"])
    #text	String value of the partner name
    status	String of the system log message status to filter by
    dateFrom	String specifying the start date for the system log message date range ("2025-08-11)
    dateTo	String specifying the end date for the system log message date range ("2025-08-20)

  • Response:

    Response schema node/field	Description
    Response	Response containing the list of system messages
    messages	Array of system messages matching the filter criteria
    item	Individual system log message
    docInfo	Integer of the internal document identifier
    company	String of the company name
    partnerName	String of the trading partner name
    date	String of the system log message date
    status	String of the system log message status
    message	String containing the system log message content
    statusCode	Integer representing the status code
    status	String of the overall response status
    message	String containing any response message

Next steps

After configuring an EDI for Cloud v2 Notifications activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

EDI for Cloud v2 Notifications activities can be used as a source with these operation patterns:

• Transformation pattern
• Two-target archive pattern (as the first source only)
• Two-target HTTP archive pattern (as the first source only)
• Two-transformation pattern (as the first or second source)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.