Run flows in parallel with a secondary NetSuite connection

The NetSuite secondary connection in the Amazon – NetSuite Integration App allows you to run flows in parallel. Think of the secondary connection as an additional “channel” that you can utilize to sync the data generated in your flows.

Ideally, the secondary connection will deal with flows that generate low-volume and high-priority data that is time-critical, or with flows that generate high-volume and low-priority data that are not time-critical. This eventually removes the bottleneck for your time-critical flows and helps you expedite the data sync.

Use your best judgment when assigning a secondary connection to your flows. As a rule of thumb, your high-priority and time-critical data must have a greater number of concurrency levels available for more quickly syncing high-priority, urgent data.

The following scenarios will clarify your options.

As demonstrated below, you can see that the secondary connection is dealing with flows that generate high volume, low priority, and not time-critical data, such as Settlement. The primary connection is dealing with flows that generate low-volume, high-priority, and time-critical data, such as Order.

Figure 1: Secondary connection dealing with flows that generate high-volume, low-priority, not time-critical data.

This arrangement enables your high priority data, such as Order, to get synced faster without getting stuck in the queue.

In the following image, you can see that the secondary connection is dealing with flows that generate high volume, lower priority, and not time-critical data, such as Settlement. The primary connection is set up for flows that generate high-volume, high-priority, time-critical data, such as Order and Fulfilment.

Figure 2: Secondary connection dealing with flows that generate high volume, low priority, and not time-critical data.

This arrangement enables you to have a greater number of concurrency levels available for your high priority data that is time critical and should get synced faster.

Before you begin assigning flows to the secondary NetSuite connection,

1. In integrator.io, go to the select Connections from the Tools & resources menu.
2. Search for Secondary NetSuite Connection (Amazon Integration App).
3. Enter the connection details in the Secondary NetSuite Connection (Amazon Integration App) connection window and then click Save. The connection should now appear online.
4. Under Advanced Settings, enter Concurrency Level for Secondary NetSuite Connection (Amazon Integration App) and NetSuite Connection (Amazon Integration App) and split the concurrency levels between these connections as needed.
5. In the Amazon – NetSuite Integration App, go to Settings > Connections. If NetSuite Connection (Amazon Integration App) is offline, edit the connection and enter appropriate credentials to get the connection online.

Note: Both NetSuite Connection (Amazon Integration App) and Secondary NetSuite Connection (Amazon Integration App) must be online before you assign flows to the secondary connection.

To assign the secondary NetSuite connection to flows:

1. In the Amazon – NetSuite integration app tile, click the Settings icon.
2. Under Settings > General > Select flows to allot secondary NetSuite connection, select one or more flows that you feel must utilize the secondary NetSuite connection.
3. Click Save. When the browser is refreshed, the secondary connection starts appearing in Settings > Connections of the Amazon Integration App.