• Desc: This page is used to configure the detailed steps of how files are received or pulled from connections, and how they are sent to other connections.

  • Overview:

image.png

1. Trigger: (The first step in flow) Configuration that allows the system to receive files from a connection.

When selecting an action, there will be 2 types: Pull Action and Receive Action.

1.1 Pull Action:

Simplify will actively pull files from the connection (such as files in folders on FTP, SFTP, or Azure Storage) based on the configured frequency.

For pull actions, there are several common configurations:

  • Trigger Frequency: Defines how often the system will pull files from the connection.

  • Document Type: Specifies the type of files that the action will pull and process.

  • Connection: Selects the connection that has been set up in the Connection page.

In addition, each action type may include specific configurations depending on its functionality.

image.png

1.2 Receive Action:

Receive files from the connection via webhook.
This means whenever there is a change or update on the connection, the connection will send a webhook call to Simplify, allowing Simplify to handle the received files or update related data (such as lookup tables) within the system.

For receive actions, there are several common configurations:

  • Document Type: Specifies the type of files that the action will pull and process.

  • Connection: Selects the connection that has been set up in the Connection page.

In addition, each action type may include specific configurations depending on its functionality.

image.png

1.3 Condition Setup:

Define the condition(s) that determine whether this step will be executed.

Overview:

image.png

image.png

Configuration:

When setting up conditions, you can define one or multiple conditions with different criteria and link them using individual AND/OR operators or group them into a condition group.
Condition groups can also be linked together using AND/OR operators.

Condition Configuration

For each condition, you can configure the following options:

  • Left Expression: Select an XPath from the document to retrieve a value used in the condition.

  • Operator: Choose an operator to compare the left and right expressions.

  • Right Expression: Select an XPath from the document to get a value, or manually enter a constant value to be compared with the left expression.

Additionally, the Right Expression behavior may vary depending on the selected Operator:

  • When the operator is "Check Document Existed", the Left Expression will be ignored.

image.png

  • When the operator is "Lookup Table""Not In Lookup Table""All In Lookup Table", or "All Not In Lookup Table", the Right Expression will become a dropdown list allowing you to select an existing Lookup Table in the system for validation.

image.png

1.4 Setup Partners:

Select partners configured in the Connected Partners page.

You can configure Partners to be added by navigating to Advance Config → Connected Partners or by clicking the "Go to the Partners page" link.

Note: When the "Partner Required" checkbox is checked, it means that this flow must match the partners added. If the files do not match the configured partner(s), the flow will not run.

- Overview:

image.png

1.5 Setup Acknowledgments:

The Setup Acknowledgments tab allows you to configure settings for acknowledgment files that are sent out.

Use this section to define how acknowledgment files (such as 997 or other response documents) are generated and transmitted.

You can also choose to skip sending acknowledgments

Currently, Setup Acknowledgments only supports document types of EDI and Pull/Receive actions under the following integrations: ECGridFTPSFTP, and Azure Storage.

- Overview:

image.png

2. Send/Execute Action(s):

Configuration that allows the system to send or execute files.

2.1 Select Action:

There are two types of actions: Send and Execute.

  • Send Action: Sends the processed file from the system to the connection configured in the action step.

  • Execute Action: Processes the file within the system without sending it externally.

- Overview:

Send Action:

image.png

For Send Action, there is a special case called Windows Service Send Documents.

This action works together with a Windows Service provided by Simplify, which can be downloaded to your local machine when creating a Connection.

After the file is processed in this action, it will be marked as WaitingForDownload.
The file status will change to Completed once the Windows Service successfully downloads it from the system.

Execute Action:

image.png

2.2 Setup Condition:

Define the condition(s) that determine whether this step will be executed.

Overview:

The Condition Setup works similarly to a trigger, but it includes an additional option called Previous Step Response.

image.png

Previous Step Response represents the output returned from the previous step. When selecting Previous Step Response, the Left Expression can be set to one of the following:

  • Status

  • Integration Status

  • Response Status Code

  • Response Content

Status: the system status of the previous step.
Integration Status: the system integration status of the previous step.
Response Status Code: the HTTP status code returned after sending the file externally via API/App.
Response Content: the response body returned after sending the file externally via API/App.

When Left Expression = Status or Integration Status:

  • Operator options: Equals or Not Equals

  • Right Expression: a combo box to select values based on the corresponding Status or Integration Status.

When Left Expression = Response Status Code:

  • Right Expression: a numeric input (default).
    If an operator from the lookup table group is selected, the Right Expression becomes a combo box to select a lookup table value.

When Left Expression = Response Content:

  • Right Expression: a string input (default).
    If an operator from the lookup table group is selected, the Right Expression becomes a combo box to select a lookup table value.

2.3 Setup Acknowledgments:

The Setup Acknowledgments tab allows you to configure how acknowledgments are received after sending EDI documents.

At present, the Setup Acknowledgments feature supports only EDI document types and Send actions for the following integrations: FTPSFTP, and Azure Storage.

- Overview:

image.png

3. Some warning/alert icons to be aware of:

  • When multiple flows have identical Trigger configurations (FTP/SFTP)

image.png

  • When the connection webhook is lost or has not been registered

image.png

  • When the map between two steps has not been compiled

image.png

image.png

  • When no map exists between the two steps

image.png

image.png