Emporix Orchestration Engine provides Hello World exercises designed to acquaint you with the realm of value streams and the OE environment. As a brief overview of OE , we can construct a value stream from the ground up, allowing you to grasp the concepts and familiarize yourself with the available tools.

Before starting with the trails, take a look at some basic information about how the processes in OE are built - see Value Stream Components guide.

Then, go through the trails in the following order:

1. Setting up a First Value Stream

2. Adding a Conditional Step in a Value Stream

As OE is closely integrated with Make (formerly Integromat), it's important to get to know the application. OE's value streams use Make scenarios to perform actions in other systems. It's essential to understand the way the scenarios behave and how they can be combined within a process.

To learn more about Make, you can check the following documentation:

• Make Scenarios

• Types of Modules

After receiving a provisioning request, Emporix prepares a OE tenant for you. When the tenant is ready, you'll receive an email notification to activate your account. Then, you can access the Emporix Management Dashboard and Developer Portal.

• Management Dashboard is where you access OE.

• Developer Portal is where you manage your account, tenant or API Keys.

The configuration of your OE tenant is related to setting up relevant access controls and connections. This can be done in the Admin section of OE.

To access the Admin section, log in to Management Dashboard, go to OE -> Admin.

In the Admin section, you can find your Make settings, Tenant ID and configuration tabs related to Datasources and KPIs & Analytics.

For details how to manage and use the configurations of the Admin section, take a look at:

When you create or edit a value stream, you have two possibilities as the next actions: test or publish.

• Test - allows you to test the draft version of the process, which means all the triggers and steps that you constructed in the value stream can be checked before you publish them

• Publish - creates a production version of the value stream

To test the value stream before publishing, choose the Test button.

You can test the value stream in two ways:

You can clone a scenario prepared in Make to use it in your OE value stream. Go to the Make application and choose the Clone action for the selected scenario. You can copy all types of scenarios, either the ones that are used as triggers, or the ones that are prepared for the other process steps.

When you clone a scenario in Make, a Clone pop-up window is displayed where you should specify the name for the scenario's copy and select, or create, a new webhook to trigger the copy of the scenario.

Each Make scenario that’s invoked by the OE process engine, starts with a cloud event that is set as a trigger. This requires a unique webhook so the value stream engine routes the request to the proper scenario. When you add the scenario to the value stream, it sends requests to this webhook and not to the one of the original cloned scenario. This way the new cloned scenario gets invoked.

• How am I proactively alerted to problems?

• Why my Make scenario is not valid in OE?

• What are best practices for handling errors in Make scenarios?

• Why is my value stream invalid?

OE is available from the Emporix Management Dashboard. The dashboard is where you perform your administration and configuration tasks. It’s also where you check your data and statistics.

As a customer, you receive your tenant details with credentials to log in to Emporix Management Dashboard when the provisioning process is complete.

To access OE:

1. Use the link provided to you in the account activation email and log in to the dashboard with your email address and password.

1. After you log in to Emporix Management Dashboard, you can see the welcome page. Go to Orchestration using the navigation menu on the left side of the application. If you are an Emporix Commerce Engine (CE) customer as well, you can see all the CE modules in the navigation menu as well. If you use OE alone, the CE modules are not visible and you have access only to the Orchestration and Administration modules, depending on your assigned role.

Let’s take a look at some examples for wholesale, distribution and discrete manufacturers. Remember, Emporix OE is focused on enhancing both business outcomes and customer experience. The main use cases that you might use OE for are:

• Payment assistance: Customer payment options are auto-restricted for buyers with a poor payment track record, encouraging the customer to pay on time while protecting the seller.

• Stock assistance: Overstocked products are automatically promoted to ensure working capital efficiency.

• Order assistance: Customers are proactively provided with recommended substitutions for products which cannot be fulfilled on time.

• Sales assistance: Sales reps are supported with intelligent recommendations for alternative products or suppliers to meet the promise of on-time delivery.

There are many more use cases for particular situations:

External events work as triggers for value stream to run or wake up sleeping processes. These events, such as notifications regarding stock levels, quote requests, and many others, are transmitted as authenticated webhooks to a pre-configured Orchestration Engine event-receiver endpoint. When receiving these notifications, the system interprets them and initiates, or wakes, relevant value stream accordingly. This approach enables real-time adaptation and decision-making, allowing businesses to efficiently manage resources and respond to changing conditions in their operational environment, creating business agility.

OE is schema-less, it utilizes the Cloud Event specification for both receiving and sending events. This framework enables OE to seamlessly gather event information from designated endpoints responsible for transmitting such data. By adhering to this specification, OE ensures efficient and standardized communication, facilitating seamless integration with various systems and endpoints.

For details about events in OE, check the following documentation:

Emporix related:

• Events Registry

Emporix Orchestration Engine is the digitalization layer to the Emporix Commerce Orchestration Platform. It empowers businesses to monitor real-time events across systems, make data-driven decisions, and automate business processes dynamically — without heavy development. By letting you define workflows triggered by events - like inventory shortfalls, customer behavior, or supplier signals — you can orchestrate actions (such as email, pricing changes, stock adjustments, etc.) across your stack immediately. OE gives you real agility as it bridges the gap between what’s happening in operations and how the front office (sales, marketing, service) responds. Orchestration Engine enables rapid response to real business conditions, reduced manual labor, more efficient operations, and a more adaptive way to run commerce end-to-end.

Our OE can gather data retrieved from Celonis and use value streams to improve business processes, which are reflected in Key Performance Indicators. Data retrieved from Celonis is visible in the KPIs and Analytics dashboard.

To configure the connection with Celonis, you need the environment URL and Celonis token.

Environment URL

You can get the URL from Celonis EMS application.

1. Copy the URL from your Celonis account.

2. In OE, go to Management Dashboard -> OE -> Admin.

3. In the Settings tab -> Celonis section paste the URL.

4. Save your changes.

Token

1. In your Celonis account, go to Admin & Settings -> Applications and choose Add New Application -> Application Key.

2. Enter the key name, to be able to identify the key in future.

3. Copy the token.

1. In OE, go to Management Dashboard -> OE -> Admin.

2. In the Settings tab -> Celonis section paste the token.

3. Save your changes.

Having the URL and token settings done, you can configure your KPIs and Analytics dashboard. See the documentation.

By default there is always one team created for every Make Organization. All users initially belong to this default team. However, you can create additional teams to logically separate Make Scenarios and users according to the needs of the business. You can configure OE to point to any Make Team you want.

To set the Make Team for a tenant:

1. Go to OE → Admin → Settings.

2. Add the name of your Make team.

To join Make and be a member of the Make Team, the users have to be assigned to the user group that gives permissions to access Make.

The Import and Export feature is useful when you want to move your processes from one tenant to another for example, from your test environment to production.

To export a value stream:

1. Go to the Management Dashboard, and choose the three dots icon next to the value stream you want to export.

2. Choose Export Process. The value stream gets automatically exported and downloaded as a .json file.

To import a value stream:

1. Go to the Management Dashboard and choose the Import button at the top right, above the list of processes.

2. Upload the .json file containing your value stream. You can either drag and drop the file or select it using the standard file browser. If you selected the wrong file, choose Cancel to choose another one. To abandon the entire operation, choose Discard.

3. To start the import, choose Import Process. The value stream gets automatically added to your dashboard list, with the Last published date showing the import date.

The value streams are imported along with:

• Events - the events that you use in your value stream are imported and added to events registry in the tenant

• Make scenarios - all the scenarios that are used in your process are imported in the same configurations

• Subflows - when you have subflows configured in your process, the linked value stream is imported as well

• Conditions - the process is imported together with conditions applied at the steps levels

Current things that can't be exported/imported with a value stream:

• Cloud function connectors - this is going through an improvement process and will be updated.

If you use dots in event names, for example tenant.created, you need to correctly reference such event types to ensure seamless integration between Emporix Orchestration Engine and Make or other third-party platforms.

You may need to reference such event types it in the following situations:

• When using the OE API process run search endpoint.

• When using the search process run module in Make.

• In other places in Make, when referencing the event type as an attribute of a payload.

To reference an event type with a dot in its name, enclose the event type name in backticks (backquotes) ``:

Usage examples

OE API Execution Run Search Endpoint

When using the OE API process run search endpoint, ensure that you enclose the event type name in backticks.

For example:

Make integration

When working with Make, enclose the event type name in backticks when using the search process run module or referencing the event type as an attribute of a payload.

For example:

• In the search process run module:

• When referencing the event type as an attribute of a payload:

Using backticks to enclose event type names with dots, ensures compatibility with Make and other third-party platforms. By following this convention when referencing these event types, you can maintain seamless integration and prevent potential issues during the processing of your workflows.

Introduction

Emporix Orchestration Engine (OE) enables companies to dynamically optimize their business processes based on real-time, end-to-end process intelligence. It is revolutionary as it orchestrates people and systems across the business and even outside of it, based on the process intelligence, enabling the first process-context-aware solution in the commerce space. This means that whenever you receive signals from your business, or when you receive insights about customers', or suppliers' behavior, you can react immediately to improve your business operations.

Emporix OE helps to close a gap between the operations of your business and the sales, marketing and communication channels that extend them out to the customer in the front office. It covers the need to obtain information, work with it and use it for business improvements. It makes it possible to create data-driven operations, with real-time business agility.

How does OE work?

Emporix OE orchestrates actions for systems to optimize key outcomes for the business, based on events occurring across your organization. OE is a framework that enables orchestration, planning and running of actions combined in value stream. They typically are a combination of:

• a trigger event that makes the value stream start

• a series of steps that are performed after the trigger

Emporix OE also provides a User Interface (Management Dashboard UI) that allows you to design and manage the value stream easily and quickly. It enables business analysts working in-house, at consultancies or at solution providers to build them without the need of development expertise or resources.

Signals from your business to Emporix OE trigger automations and optimization for various business scenarios, such as:

• anticipating stockouts

• reducing return rates

• controlling advertising spend

It triggers an almost instantaneous response to events defined by business rules, proposing optimizations to the line of business, and automatically orchestrating changes with the underlying tools (such as email, marketing, commerce and orders), significantly reducing time to action and manual labor.

Moreover, OE is integrated with CE to support a wide range of commerce-driven business processes.

The versioning of value stream is based on the roll-forward approach. It means that with every change a new version of the process is created. If you want to get back to a previous version, you can do so, but it actually creates the next version of the process.

When you trigger a value stream and it starts to run, you have an instance of that process. If the process is at version 1, that instance is an instance of version 1. Supposing you have 200 running instances at version 1 and you modify your process and save it as version 2, the next instance of that process that you run is a version 2 instance. This does not change the 200 running instances at version 1.

It is possible to have many instances of many different versions all running at the same time. When a new version is created, it doesn't stop the previous ones from running.

Additionally, using the Show Versions function, you can check what is the current value stream version, when it was modified and by whom. You can also select the previous version of the value stream and get back to it.

Event Registry is a list of all the events that were configured in your tenant for your OE value stream. The events are the triggers that initiate the processes and make them run.

Events are utilized by the ce-type attribute, which indicates that the event has occurred. By aligning the Event Name (eg. order.created) configured in OE with the ce-type name, you ensure that a value stream accurately receives and processes the event information.

To create a new event:

1. In OE, go to Events -> Event Registry.

2. Choose Create New Event.

3. Specify the Display and Event names.

Display name - it's the name that is visible in the UI when you create a value stream, for example: Order Created.

Event name - it's the name of the registered event, for example: emporix/ce/order.created.

OE's value stream together with Make scenarios allow for seamless interaction with Celonis' knowledge models and their Intelligence API. You can use the data and signals received from Celonis as triggers for your business value streams. Then, when the processes finish, you can send back a response to Celonis using action feedback.

To configure the data flow between OE and Celonis see the topics:

• Retrieving Data from Celonis

• Sending Data from OE to Celonis

If a scenario that you prepared in Make is not valid for your value stream in OE, check if you have the following settings done:

• Start trigger must end with a Start New Orchestration module. Check Events as Triggers.

• Mid trigger must have a notification event - Completion Event module. Check Setting a Trigger to Wake Up a Paused Value Stream.

• Scenario in a process step must start with Trigger Event and have the Completion Event module. Check .

If you created a new value stream but the validation shows that the process is invalid, check the following possible reasons:

• Proper configuration and reference to Make scenarios

• JSON document syntax errors

Errors in referencing to Make scenario

It's possible that you have a wrong reference to a Make scenario that was either deleted or modified.

Reference to a deleted Make scenario

Check if your value stream does not reference a scenario that had been deleted. If it does, you should see a red error with a Scenario deleted notification message at the location (value stream step) where the scenario was used.

To resolve this error, remove the reference to the deleted scenario from your value stream step.

Reference to a modified Make scenario

If a Make scenario was modified, it may no longer meet the requirements of its intended context. In such a situation, the OE UI doesn't show it in the list scenarios available for your value stream. You're not able to use the scenario in your process' steps.

This occurs when:

• The scenario no longer sends output event information through the Start New Orchestration module

• The scenario no longer sends output event information through the Completion Event module

• The scenario no longer receives incoming calls through the Trigger Event Make module

To resolve the errors, make sure the modified Make scenario meets the requirements of the intented context and check if all the input and output modules are configured properly, with correct events setup.

JSON syntax

As the value streams are designed using OE UI, it doesn't usally happen that any syntactic errors occur. However, if it turns out that your value stream doesn't work, and you checked all the OE and Make settings but the errors still occur, you may need to review the JSON document to ensure it adheres to proper structure and formatting.

The value stream that have already started, may need to wait for an intermediate event before continuing with next steps. While waiting, a value stream goes into a dormant or sleeping state.

Instance ID as a wake up trigger

To wake up a sleeping process instance, you need to post an event with a ce-instanceid (Instance ID) header and the ce-type header that matches the event type that had been configured for the process as a trigger.

• ce-instanceid routes to the correct instance

• ce-type routes to the trigger

The Instance ID is the ID of a running instance of a value stream. Every time a trigger event is received for an OE value stream, OE generates a new instance with an Instance ID. If the value stream is triggered 100 times, OE creates 100 unique Instances, each with their own ID.

1. To find the Instance ID header in Make, go to your scenario and check the completion summary of the process that was already run. In the Emporix Orchestration window you can check the Instance ID and copy the value.
2. Enter the copied value for the ce-instanceid header in your request.

   If you send the request with the ce-instanceid and ce-type headers, OE saves the payload and then passes it through to the next Make scenarios that are configured as next steps in your OE value stream. The event type is used as a key. The payload grows with every event that is generated.

Notification module in Make as a wake up trigger

It is also possible to wake up a value stream with a Make scenario that ends with a "completion event" module that is configured to send notifications about completed scenario to OE. If such a Make scenario is a part of your value stream steps, it causes the process to wake up and move to the next process steps.

You can configure your Make organization to receive different kinds of notifications related to your scenarios: warnings, errors or deactivations. You can either receive the notifications by email or check them inside the Make application under Notifications.

Email notification options

To set up your Make email preferences:

1. Log in to your organization in Make.

2. Go to My Team -> Team -> Notification Options.

3. Choose the notification that you want to receive by email.

Why do I receive emails about failed processes but not about incomplete ones?

There's no distinction between a failed process and incomplete process when it comes to notifications sent from Make. This is because an incomplete process run is a failed process scenario with errors or warnings. What is different between the two is that a scenario is not shut down immediately. The state is saved when the process fails.

We recommend to enable all the notifications in Make, to be sure not to miss any issues.

If everything is correct but you still don't receive the emails, check your spam folder or contact your administrator to check if the messages are not blocked on your side.

Emporix Orchestration Engine orchestrates business behaviour for systems to optimize key outcomes based on events. They consist of a trigger that makes the process start and of steps that need to be performed after the trigger takes place.

All value streams are executed top-down and run independently from each other.

Value streams listing

To access the page, in the navigation menu go to OE → Value Stream.

What you can see in the page is a list of all the value streams that are created in your tenant. You can manage the value streams by creating new ones or deleting those which are no longer needed, activating or inactivating the ones which already exist.

Make modules are components that are used for creating scenarios in Make.

The connection between OE (Orchestration) and the modules in Make is normally created automatically. However, if it happens that you add the module in Make when creating a scenario, and the connection is not established, you can configure it manually:

1. Add an Orchestration module in Make, for example a Trigger Event. An Emporix Orchestration

After the value stream is published, what you see after clicking on the value stream is the latest version that was released. To open the draft mode for a published value stream, you have two options:

• Choose the Draft icon in the dashboard, this displays a window with basic information about the person who edited the draft and the date when the last changes were made. Go to draft opens the latest version of the draft.
• Open the selected value stream and then choose the Edit button.

Make scenario settings

Make's scenario settings provide different options for handling errors and scenarios data storage.

Allow storing of incomplete processes

Introduction

The KPIs & Analytics dashboard gathers high level business information using KPIs from Celonis and business outcomes of your running value streams.

The dashboard is divided into two sections:

• KPIs - data showing KPIs retrieved from Celonis EMS.

• Value Stream Effectiveness - graphs showing the business outcomes of your running value stream.

Prerequisite

To start with the configuration of the KPIs and Analytics dashboard, configure your connection with Celonis. See the documentation.

Configuring the KPIs & Analytics dashboard

The KPIs & Analytics dashboard can be configured to your needs and the data that is most important for you to see and monitor. To start the configuration of the dashboard, go to OE -> Admin -> KPIs & Analytics.

Business KPIs

To configure business KPIs:

1. In the Business KPIs section, you can configure up to 4 KPI tiles that display your selected data.
2. To set up a specific KPI, open its edit mode by choosing the edit icon.
3. Enter the Display name for the data that should be displayed in the tile.

Process effectiveness

To configure the process effectiveness visualizations:

1. In the Process Effectiveness section, you can configure up to 4 graphs that can be used in the KPIs & Analytics dashboard to view the results of the running executions and their effect on business outcomes.

1. Enter the Display name for the data graph.

2. Choose the related value stream.

3. Complete the following KPI data sources configuration:

   • Celonis Knowledge Model

Many value streams require an interaction with an internal user or an external party, such as Supplier or Customer. This is often referred to as Human-in-the-loop. For example, in one step of a value stream you send a form to your supplier asking for some information, and in another step you use and process the information provided by the supplier's form submission, or pass it to an internal user to review and approve.

In the first step, a workflow task is created for the supplier and assigned to a magic link. To consolidate all the tasks assigned to a single recipient and also aggregate email notifications related to different value stream, you can point the external party to their Task Inbox that lists all the tasks assigned to them. You can achieve that by generating an access link that you are able to share with a relevant person.

Internally, employees using the Management Dashboard can easily access their Task Inbox, which is integrated within the dashboard, promoting easier access and increased efficiency.

Accessing an internal task inbox

For internal users, the Task Inbox is conveniently integrated within the Management Dashboard, allowing employees to access their tasks more easily and work more efficiently. By eliminating the need to switch to external systems, users can manage all their tasks directly from one centralized location. The Task Inbox is accessible via the top panel, providing a seamless experience within the dashboard.

Accessing an external task inbox

The Task Inbox is also available externally for users who do not have access to the Management Dashboard. The external users can access their Task Inbox with access links generated for them in Management Dashboard.

To generate an access link:

1. Go to the Admin module, and open the Access links tab.

2. Choose the Create access link.

3. Select the recipient from the list and pick the link expiry date.

4. Choose Save to create an individual link. The link ID number appears after successful creation.

The Task Inbox is available outside the Management Dashboard so you can share the link with external user. Each user gets a unique access link that allows them to view their Inbox without authenticating or logging in to the Management Dashboard first.

Revoking access

For each access link, you can assign an expiry date upon creation. But for security reasons, you might want to withdraw access earlier, for instance if a user leaves the company.

1. Go to the Admin module, and open the Access links tab.

2. Pick a user's email you want to revoke the Task Inbox access and choose the Trash icon.

From this point on, the person is not able to access their external Task Inbox and you can see the status revoked.

OE uses the Cloud Event specification when responding to, or sending out events. OE uses this to receive information about an event from the related endpoint that is responsible for passing the event information.

OE uses CloudEvents specifically with HTTP Protocol Binding and Binary Content Mode, where currently we support application/json only as a content-type for the data payload.

To set up OE to work with cloud events:

1. Make sure the authentication works properly and the relationship between the endpoint you use for receiving events and OE is correctly established.

To create the relationship you should provide source and secret values that are configured for your event-receiver endpoint and used as a signature in every request that is sent.

1. To run a value stream, start a trigger that is specifically configured to set off the process. The trigger for the first step must specify values of the following headers, which are cloud event specifications adopted by OE:

   • ce-source - source of the environment sending the cloud event, you can enter any source here but it should clearly identify the application that is sending the event

   • ce-type - type of the cloud event

If you have a ce-instanceid header defined, the start trigger ignores it as the header is used only for restarting an existing value stream instance. Moreover, ce-instanceid is bound to one value stream, you cannot have the same id defined and used in triggers for another value stream.

1. Running the OE value stream allows orchestration of multiple Make scenarios. Every Make scenario is combined of various modules that gather data one after another. The first module is always an input for the second module that creates output for the next one and further. While a process instance is running, it can be configured to wait for another event before moving to the next step. In that case, the process goes to a sleeping state and waits for the next event type.

1. To wake up a paused process with an event, and make it move to the next step, you need to send an event that wakes up the trigger. You have to have a unique ID (ce-id) for the event and the ce-instanceid (OE instance ID) defined. OE instance ID routes the event to the proper sleeping process instance that is waiting. You can send many events using this field and they are all be routed back to the proper value stream instance.

Event logs are records that track important actions and incidents in a system or network, like errors or user activities. They help to monitor the system by providing details on when, where, and what happened.

In the OE Event Log main view, you can check records of all the events that were received for your value stream. You can search the results with the Request ID for which the event occurred. You can also see when the data was received and whether the call was successful.

Request ID - it's an identifier of the signal sent to OE to start a value stream, for example: req_NkMdGRM1paSsrootCUhf. You can find the Request ID in the debug mode in the Webhook logs of the trigger:

To see more detailed logs, select the event you're interested in.

Then you can see a popup window with details including:

• ID - it's the ce-id that is sent in a request, it represents the unique identifier for the event instance.

• Source - information about where the event occurred, for example: emporix/oe.

• Type - event name, it can be checked in the , for example: order.stock.checked.

Logs details also allow to get all of the event information in a CURL format, use the Copy as CURL for that.

Introduction

The Emporix Orchestration Engine orchestrates business behaviour for systems to optimize key outcomes based on events. OE provides a framework that enables the orchestration and execution of actions combined in Value Streams.

The value streams consist of an event that makes the process start, and of the next steps that need to be performed after the event takes place. Emporix OE provides a user interface, the Management Dashboard, that allows you to design and manage value streams with ease.

To start working with the value streams, make sure you have all the prerequisites and configurations completed as described in the following sections of our documentation:

Value Streams View in Management Dashboard

To open the value stream view in Management Dashboard, simply click on the selected value stream that you wish to open.

The view shows every step of the value stream, starting with a trigger and then proceeding with the subsequent process steps or mid-triggers. This is where you can begin working on your new value stream or edit an existing one. In each value stream you view, you can also perform the following actions:

• Edit - opens the draft mode of a value stream

• Show versions - you can view all the versions of your value stream and switch to the previous one. To see how versioning of the value stream works in detail, see .

• Go to Debugger - this allows you to move directly to the debug mode to check all the logs of your value stream instances. For debugger details, see .

This document functions as a guide to our organizational Data Retention Policy, outlining the Time to Live (TTL) of data within the systems we use.

Orchestration Engine data limitations and storage

Make data limitations and storage

In case of UI issues, you can contact Emporix Orchestration Engine support team at [email protected]. The team may ask you to provide a HAR (HTTP Archive format) file with logs generated from your browser. Generating a HAR file helps us to identify the issues. The HAR file is stored in JSON format and contains information about the web browser's interactions with a web server.

You can generate a HAR file from any browser, here are some examples.

Google Chrome

To create a HAR file in Google Chrome:

1. Open the Google Chrome browser and go to the page which you want to record.

2. To open the debug pane, press the F12 button on your keyboard, or chose the three-dots icon on the right of the toolbar and go to More tools -> Developer tools.

3. Choose the Network tab.

4. Ensure that Chrome is recording, you should see a confirmation message in the tab and a red button indicating that a recording is already in progress. If not, choose the

Safari

To create a HAR file in Safari:

1. Open the Safari browser and go to the page which you want to record.

2. In the Develop menu, choose Show Web Inspector. If you don't see the the Develop menu, you can enable it in your browser's advanced settings.

3. Go to the Network tab.

4. Reproduce the issue on the page where it occurred.

Microsoft Edge

To create a HAR file in Microsoft Edge:

1. Open the Microsoft Edge browser and go to the page which you want to record.

2. To open the debug pane, press the F12 button on your keyboard, or go to Tools -> Developer Options -> Network.

3. Clear the session history by pressing the button indicated by three lines and a red "X".

4. Ensure that Edge is recording, you should see a confirmation message in the tab and a red button indicating that a recording is already in progress. If not, choose the

Firefox

To create a HAR file in Firefox:

1. Open the Firefox browser and go to the page which you want to record.

2. To open the debug pane, press the F12 button on your keyboard, or go to Tools -> Developer.

3. Go to the Network tab and choose Persist Logs. You can find the Persist Logs option under the gear icon - Network Settings.

If you are experiencing any access issues when using Orchestration Engine, make sure your network is not blocking http traffic to the following Emporix, Celonis and Make domains and subdomains:

Emporix

• Emporix: emporix.io

• Emporix API:

• Emporix Developer Portal:

• Emporix Management Dashboard :

• Emporix Forms UI :

• Emporix SSO:

• Emporix Documentation:

• Emporix Inbound Webhooks:

• Emporix Outbound Events: - required for DCP customers only

• Emporix Corporate Website:

Celonis

• Celonis:

Make

• Emporix Make Environment:

• Make:

• Integromat: - additional access is needed for any Make Apps using OIDC Authorization Protocol

To allowlist the connection to and from Make from your internal IT system firewalls, use also these IP addresses:

• Outgoing = 63.176.242.240, 35.159.75.87, 3.72.162.92

• Incoming = 63.176.80.5, 3.73.150.249

Introduction

The Rulestore is a repository for creating and managing static business rules to be used in value stream. They are not active until referenced by a value stream. The business rules can be reused multiple times, in different value stream. Business rules can be changed without changing the value stream that references it, they are completely independent. Business rules can be created by users with the OE Rule Editor and OE Admin roles.

You can filter the rules by the ID and name. Additionally, you ca also see which value stream are actively referencing each rule.

If you choose the Go to Value Stream button, it opens the value stream in a separate tab. Business rules cannot be deleted if there's any value stream using the rule.

Emporix OE leverages EMS insights around the Order Management Process and orchestrates and triggers actions other systems across your business. You can immediately begin to improve your experience with your customers and directly impact your revenue. OE delivers real-time responses to signals from the back office, resulting in faster time to action for the business and the ability to positively affect the experience for the customer and the business at just the right moment.

What is the customer problem we solve?

In commerce, optimizing outcomes for these two priorities is challenging given the commerce process’ highly dynamic and decentralized nature. Front-office problem solving for customer satisfaction and customer experience doesn't typically take into account back office processes and problems; the two are typically separated, creating unnecessary friction.

Secondly, it is impossible for organizations to react to all developments with the intelligence, speed and scale required in order to maximize both revenue and the quality of customer experience.

The Orchestration Engine value streams are made up of a combination of triggers and process steps. It is required to have at least a trigger in a value stream.

Triggers

Triggers are used to start new instances of a process, or resume an existing one that was paused. There are two types of triggers: events and scenarios.

For every trigger and step of your value stream, you can add a condition that would be used by the process context to decide whether a particular action should be processed or not. You can set up a filter or a rule that serves as conditional logic for the step. All of the conditions are evaluated by the Decision Engine to affect the process.

Whenever you have conditional logic applied to a trigger or a step, you can check the condition in the and evaluate the outcome of its execution or non-execution.

The process context is an important part of the Orchestration Engine system as it holds all the external information regarding the processing of a specific value stream instance.

A process context is a JSON object that consists of three primary sections:

• Context: contains all the event-types received during the value stream run, their associated payloads (if any), and the initial payload when the value stream is started.

• Metadata: provides additional information about the process context, such as the tenant identifier.

You can use datastore for use cases like listing active users, managing workspace settings, lookup tables and others. Data from a datastore can be fetched using its name space by a specialist Make module or through API. The key specifications for datastore interaction include:

• authentication through Magic Links

• support for CSV data files

• supported text search

The steps below demonstrate an example how to use the datastore functionality and test it with the end-to-end flow:

Introduction

The Shift High Stock Product value stream was created for demonstration purposes. In this example, Orchestration Engine uses the Emporix Commerce Engine API to perform some of the actions, but it can work with any other systems. There's no dependency between Emporix OE and Emporix CE platforms.

The value stream is an example designed to meet the demand for maintaining optimal stock levels. It is prepared to identify and prioritize products with a high stock level, ensuring their successful promotion and preventing any issues with overstock.

The value stream consists of a trigger and subsequent process steps that end in promoting a product and sending a post action feedback to Celonis.

Introduction

The Value Streams Debugger was created to help you find problems when you're running value stream. You can:

• See the status and metadata for running instances of a version of a value stream.

Introduction

Using Form.io, OE allows you to build highly customizable forms. The platform offers extensive customization options, makes it possible to control various aspects of the form's appearance and behavior. You can streamline the data collection processes by creating forms that perfectly align with your specific needs and guidelines.

The forms page is available in the Management Dashboard, under OE. On this page you can:

• see all the forms that were created in your tenant

• create a new form

• create a form link

• duplicate a form

• remove a form

• import and export multiple forms

Moreover, you can filter the forms by name, ID, or the language in which they were prepared.

Prerequisites

To start working with the forms builder, you should get familiar with the basic features and the components that are used there. To learn about the solution, see the documentation.

Creating a new form

To create a new form:

1. Go to Management Dashboard -> OE -> Forms.

2. In the forms page, choose the Create Form button.

3. Add the name for your new form.

4. Choose the components that you want to have in the form. You can select among the , , and

Add the components by using the drag and drop feature, which allows for putting the components at any place, before or after other components.

For every component that you add, there's a detailed view with the configuration settings for this specific field in the form. You can customize your component with different values, data or conditions.

For more details, see the documentation.

1. To preview the form after you've added all the components, choose the Preview Form button.

1. When your form is ready and you want to save it, choose the Save Form button. The form will appear in the forms page list.

Dynamic data in Forms

Forms can be customized to incorporate dynamic data, allowing for the creation of personalized forms tailored to specific recipients. See the Coffee Preferences example below, to learn how to set up such a form.

1. Go to Forms and choose to create a new form.

2. Add a dropdown menu component and call it, for example, Coffee Preferences.

3. In the Coffee Preferences component, go to the Data tab select Custom as a Data Source Type.

4. Add Custom Values, they are needed to return the value options. For example, values = data._magicLinkCustomAttributes.coffeeType[0].options

1. Add Text Field components that will also work as additional custom attributes to choose in a form. For example, milk_type and sugar_amount.

2. In the milk_type component go to Data tab and add a JavaScript code under Custom Default Value. For example, value = data._magicLinkCustomAttributes.defaults[0].milkType.

3. Save the form.

After creating the components, you can check the preview of the created form:

Editing an existing form

To edit an existing form, click on it in the forms list. The edit mode is opened straight away and you can apply your changes.

If you want to reorder or edit the selected components, you use the inline components settings and adjust the component to your needs.

For more details, see the documentation.

Duplicating a form

To duplicate an existing form, choose the Duplicate icon.

After you duplicate the form, it's added to the forms list and displayed with the suffix "copy" in the name. You can then rename the form.

Deleting a form

To delete a form, choose the Delete icon for the selected form. You have to confirm the deletion of the form by entering its name in the confirmation window.

Multiple forms import and export

The import/export feature makes it easy to move multiple forms from one tenant to another.

To export multiple forms from your tenant:

1. Go to OE -> Forms and choose Import/Export button.

2. Select the forms that you want to export and choose Download. This downloads separate files in a JSON format with all the selected forms.

1. Go to the tenant where you wish to import the forms. In OE -> Forms choose Import/Export button.

2. Choose import and add the previously downloaded JSON file.

3. Choose Upload. This imports all the forms that were previously exported. When the process completes, you get a notification message about successful upload.

Forms localization

Forms localization makes it possible to translate your forms from the base language to other languages. You can create forms with multiple languages, with the same structure as in the original language but with corresponding fields translated.

1. Go to OE -> Forms.

2. Open the form that you want to translate.

3. To start the translation, choose the current language that you use and then click on the Download button. This downloads myData.json file with the names of the fields. you can also use Download Template, which downloads a .json file without the selected language. For example:

1. Open the downloaded .json file and enter the translated text.

Example of an English to German translation:

1. Save the file.

2. Choose Upload Translations to upload the translated .json file back to the form in Management Dashboard.

3. Choose the translation language and add the .json file.

1. Choose Save.

Result: Your form is now available in two languages: English (in this case it's the default) and German. Both of the versions are visible in the form preview.

When the form is translated, there's a relevant lang parameter visible in the URL of the form. The parameter can also be used in configuration of a mail module in a Make scenario responsible for sending the forms.

Orchestration Engine uses CloudEvents specifically with HTTP Protocol Binding and Binary Content Mode, where currently we support application/json only as a content-type for the data payload.

The CloudEvents should be used if you want third party systems to send trigger events to OE. If you want to use triggers directly from Celonis, see the documentation.

CloudEvents is a specification for describing event data in a common way. It provides a structured format for event data and includes essential metadata such as the event type, source, and timestamp. HTTP Protocol Binding in CloudEvents defines how to use HTTP for transporting event data, and Binary Content Mode specifies how to encode the event in a binary format within the HTTP message.

To prepare the users to work with OE and Make, you need to configure their accounts and set the correct authorizations. The users have to be added to the tenant and assigned to proper user groups with sets of access rights for the roles they will perform.

To achieve this, open the Users and Groups dashboard, which allows you to manage the users’ data in general, both for Commerce Engine (CE) and for Orchestration Engine (OE). Using the dashboard, you can add, edit and delete users' data. You can also manage users by filtering or sorting by users’ first name, last name, e-mail address, department, or status.

The status types are:

• Green - the user is active

• Grey - the user account is locked

The Celonis signals and events can be used as triggers for value streams. To retrieve data from Celonis in your value stream, you can use Make scenarios as triggers, with included Start New Orchestration module or the Celonis Intelligence API modules.

The modules below should be used only if you want to have Celonis signals as triggers for your value streams. If you want third party systems to send trigger events to OE, use the CloudEvents described in documentation.

Start New Orchestration

The Start New Orchestration module is available both as part of but also can be used from your Celonis EMS Action Flows. In the later case, you can trigger value streams as part of your EMS process mining setup. For example, you can use this module to start a value stream based on certain triggered signals.

Introduction

Creating a value stream happens in the edit mode. When working in edit mode, you have a possibility to work on one draft version of the value stream, it's not possible to save multiple draft versions.

Whenever you work on the draft and do some changes, they are autosaved overwriting the previous draft.

The draft of each value stream is visible together with the active value stream in the dashboard. Whenever you click on a value stream that was not published yet, it opens in the edit mode for the process. In this case, when a process was not published yet, the Last Published date refers to the time when it was created and autosaved for the first time.

Creating a value stream

To start with a value stream:

1. In the Management Dashboard, go to OE -> Value Streams and choose Create Value Stream.

2. Enter a name for the new value stream and choose Create. Without entering the name, you cannot move to the next steps. There are no restrictions on using special characters in names, and you can create separate value streams with the same name.

Triggers

Select the trigger that you want to use in the process. You can choose between an event and a Make scenario:

Events

Choose an from the list of events that are created in your tenant. If you have a large number of events, you can narrow the list down by the event’s name using the search field.

Scenario

To set up a Make scenario as a trigger, you can use the following options:

• Choose an existing scenario directly from the list of available scenarios. To edit the scenario, you can use the Edit Scenario action and move directly to the edit mode of the specific scenario in Make.

• Choose Go to Scenarios to create a new triggering scenario in Make.

  To learn about Make's scenarios, check out the documentation.

• Choose Go to Templates to use a Make template that is already available publicly or for the team.

  To learn about Make's scenarios templates, check out the

The scenario / process must have at least one occurrence of the Start New Orchestration module, otherwise it is filtered out from a list of available scenarios / processes, or disabled if it’s not configured properly. The module is required because every trigger starts a new OE instance. If the module has not been added, OE doesn’t receive any notifications about the new triggers.

Timer Event

You can use a timer event for setting up a trigger that starts a value stream on a specified schedule, and for setting up how long the process should be paused before it wakes up again.

You can set up the timer trigger in three ways, as a context variable, single event, or a repeating event.

• Use Context Variable: you can use it for the mid triggers, the timer uses a variable that is stored in a process context of a value stream, the trigger works when a Make scenario, or a Cloud Function, provide a point in time when a value stream should wake up.

The variable should be configured in a .<event_name>.<content_variable_name> format, for example: .sleeping_until.until, where the wake up trigger is the until property in the sleeping_until event. It has to be a cron expression or an ISO 8601 compliant date.

The context variable can reference to a time during which a process context should be paused, this can be configured together with a Make scenario. For example:

The context variable is referenced as .sleeping_until.sleep_until using the <event_name>.<content_variable_name> expression format, where:

• sleeping_until is the event name, selected as Event Type in the Completion Event Make module

• and sleep_until is the content variable name, referenced to by a JSON String in the Completion Event Make module

To set the variable in Make, you can use the Set Variable module.

• Single Event: choose a specific date and time when an event should trigger a value stream

• Repeating Event: define recurring schedules using precise timing rules, such as every Tuesday, every 30 minutes or every month at specified time.

When you select a trigger, you can see that the user interface provides confirmation that the selection was saved. You can collapse the section using the caret icon in the step's heading line, or simply go to the next step by choosing the plus icon.

Process steps

After choosing the trigger, select the process step that you want to perform. Each process step can use a single or multiple Make scenarios, call a child value stream, or call a Cloud Function.

• To add a process step with Make scenarios, go to the Scenarios tab.

• To add a process step with another value stream included, go to the Subflows tab.

• To add a Cloud Function as a process step go to the Cloud Functions tab.

Scenario as a process step

You can choose a Make scenario that is already created in Make and visible in the list in the process step. If you don't want to select an existing scenario, choose Create New Scenario to create a new process step scenario, or Go to Scenarios to check for scenarios that are prepared to be used publicly or available for your team only. The Create New Scenarios and Go to Value Streams actions open a new tab with the Make application.

After going to Make, ensure you are working in the right organization. The name should reflect your tenant name in OE. To check if the organization is the correct one, it's enough to hover over the Make's sidebar, the name is visible at the top. Then, you can either click directly on the template to start working with it, or choose the Start guided setup option to continue. Every Make scenario used in a process step must start with a Trigger Event and have the Completion Event module.

Additionally, ensure that the scenario is active. The scenario toggle should be switched from OFF to ON. To learn about Make's scenarios, check out the documentation.

Each process step can be made of multiple Make scenarios that can be rearranged at any time using the drag and drop functionality (hamburger icon).

Value stream as a process step

In the Subflows tab, you can choose a value stream that you'd like to include in your parent value stream. By default, value streams are all separate processes, but they can also work together in a parent-child relationship. This is useful if you want to create a more complex process to address a larger business use case. In such a situation, you can embed processes within one another, without the need to run them separately.

Cloud Function as a process step

In the Cloud Functions tab, you can choose one of the already enabled Cloud Functions or create a connection to a new one.

To start creating a connection to a Cloud Function choose New Cloud Function, this opens a window where you can create Cloud Functions groups and structure them in parent-child relationship. To create a single Cloud Function connection, first create a group. When you have the group created you can then move to the Definition tab, where you can specify the Cloud Function configuration.

You can create multiple Cloud Function connections within a group. Groups allow aggregation of multiple Cloud Function connections under a single set of authentication credentials.

In the Definitions tab, provide the following setup for a Cloud Function connection:

• Display Name - Cloud Function name

• HTTP Method - GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS

• Invocation URL - it's a URL that is used to call a Cloud Function which is created in Azure, AWS or GCP.

• Cloud Provider - choose between predefined providers - Azure, AWS or GCP. The providers offer the infrastructure and services that enable the function to execute in response to specific events or requests. It's necessary to select one of them, to have the relevant authentication options.

Cloud Functions allow for dynamic, context-aware processing where the body of the function call is determined by applying a JQ filter to the context. The result of this filtering extracts the key body, which becomes the function's payload. Other keys in the result are mapped to replacement variables and can replace placeholders in the CF definition.

Replacement variables are defined in the CF's URL using the syntax {{.varName}}. When the JQ filter is applied, any value under the key varName is substituted into the corresponding placeholder in the URL. This system enables flexible customization of both the function payload and its endpoint through context-specific values.

After you create the connection to the Cloud Function and add it to the process step you can check the edit mode of the step with three input texts:

• Run Context - loads the last run context

• JQ Expression

• Curl to the Cloud Function

  For a value stream that had already run, you can see the context data included, for example:

The three text fields are visible only in the edit mode, when you check a value stream in view mode, you can see the Input field only.

When you select a process step, the user interface confirms that your selection has been successfully saved, just as it does for triggers. You can then collapse the section, proceed to the next step, or complete the scenario creation using these two steps.

The value streams can be created using many combinations, for example:

• A trigger with one process step

• A trigger with many process steps

• A trigger followed by a process step, another trigger and more steps

Ending the value stream

1. When your value stream is ready, choose Publish to save your configuration.

1. To activate the value stream, use the toggle that changes the inactive state to active. You can do that straight away in the edit mode, or from the processes list.

When your value stream is ready, it runs every time the specified trigger event is received. Each run of a value stream creates a new instance.

You can check your value stream instances in the . The debugger helps in troubleshooting and reviewing the whole process flow, as well as single process steps.

You can manage retrieving data from Emporix OE to track which forms were sent to suppliers or contacts using the Magic Links extractor. The extractor allows for precise data retrieval or comprehensive tracking of all sent forms. This ensures accurate visibility into communication history with your suppliers and contacts.

Prerequisite

To extract the data from OE to Celonis, you have to create a Data Pool in your Celonis account. Celonis uses Data Pools to collect and cluster data information to set up an integration flow. To learn about the details, see the documentation.

The OE value streams are created out of Make scenarios, which are made of modules performing different actions. The modules are used to link apps and services together.

Emporix has different types of Make modules prepared for OE.

Value streams capture information in events throughout their lifecycle. The information captured in the events can be imported into Celonis using a Data Extraction job. To send the data, you need an extractor that brings data from Orchestration Engine to Celonis. For OE, you can customize the extractor so that it shares the data that you want to send to the Celonis system.

Prerequisite

To extract the data from OE to Celonis, you have to create a Data Pool in your Celonis account. Celonis uses Data Pools to collect and cluster data information to set up an integration flow. To learn about the details, see the documentation.