Introduction to SyncMyOrders

SyncMyOrders is a no-code business process automation platform targeted at distribution and wholesale companies.

It allows moving data between different systems, handling human interactions, and enhancing business processes with AI without writing any code. Instead a visual drag-and-drop editor is used to design automations:

Business processes (we call them scenarios) created in SyncMyOrders can be either started manually, or triggered by various events like incoming emails, API calls, events in other applications (e.g. order created in Microsoft Business Central).

SyncMyOrders supports a wide range of data formats (CSV, XML, JSON, EDI, Excel) and communication protocols (HTTPS, SFTP, FTP, Email, MQTT, and other).

Here is an example of the case we can handle:

Defining scenario

Now, let’s dissect the current workflow and translate it into possible scenario on the SMO side. Our assumptions in this example:

• Customer system of record is Microsoft Dynamics Business Central (MSDBC)
• 3PL system of record is Extensiv WMS
• Our goal is to push orders from MSDBC to Extensiv, and back without any manual actions.

To do so, a Scenario should be defined on the SyncMyOrders side. Scenario consists of the following components:

• Trigger - an event which will cause the scenario to be launched. In our case, scenario will be invoked based on * order created event*. Right now, we support only this type of trigger, thus it’s not configurable yet on the platform.
• Execution graph - a set of configured steps, and transitions between those steps which should happen during the scenario invocation.
• Input/output mapping - configuration of data which will be supplied as an input to the whole scenario, along with mapping of output. Output mapping determines what would be considered as the result of scenario execution. Right now, inputs are considered to be empty, and output will be the last succesful step result without any transformations.

Once trigger event occurs (i.e MSDBC order was created), a scenario invocation begins. For this, a Scenario Instance is being created. Think about Scenario as a workflow template, while Scenario Instance is a particular invocation of the given template. In other words, Scenario determines what should be done, and Scenario Instance describes what has actually happened.