Mobile processes, BE-Mobile Fusion, and legacy MDE

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how mobile scanning processes should be classified from a business and technical perspective in Automotive. It connects today’s target architecture around Reactor Mobile or BE-Mobile Fusion with the legacy MDE scenario. This helps project leads, key users, and technical setup roles decide which mobile operating model fits a process and how to set it up reliably.

When each mobile path makes sense

Situation	Recommended path	Why it matters
New implementation or current project	use Reactor Mobile or BE-Mobile Fusion	This is the intended path for current mobile warehouse, production, and inventory processes.
Existing legacy customer with historical MDE	continue the existing legacy MDE in a controlled way	The old solution grew customer-specifically and should not be introduced as a new standard.
Transition phase with hybrid operation	define process boundaries clearly	Without clean separation, double postings, unclear menus, and conflicting operating paths appear quickly.
Pure detail questions about the Reactor app	use the dedicated Mobile Solutions documentation	Those pages already describe current app functions per module.

Mobile processes are real execution, not just a convenience UI

In Automotive, mobile processes are not just an additional screen. A scan on the device controls real warehouse, package, and production movements. Errors in barcode logic, endpoint setup, bin handling, or mandatory fields therefore have immediate operational impact.

Electronic Sales Labels (ESL)

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how Electronic Sales Labels (ESL) should be classified from a business and technical perspective in a Automotive project. The older knowledge base describes the solution as an existing demo or integration function between Business Central and an external ESL platform. For current projects, that means ESL is not a self-running feature but a deliberately planned integration scenario with hardware, network, platform, and clear operating rules.

Important classification

Statement	Meaning for the project
ESL is an integration scenario with an external platform	In addition to Business Central, the label platform, access points, and radio coverage must work reliably.
The legacy documentation describes a demo function	Availability and scope must be confirmed actively in the project. Not every environment has the same delivered behavior.
Data is not maintained directly on the label	The leading data source is Business Central or an agreed source application. The label only displays the released state.
Changes have operational impact	Wrong texts, prices, item assignments, or status values become visible immediately in the store, warehouse, or shop floor.

Typical end-to-end flow

An approved process changes relevant item, price, stock, or status data in Business Central.
The integration prepares a data package for the target label.
The data is sent by HTTP and JSON to the external ESL platform.
Based on its configuration, the platform maps the fields to the correct label and layout.
Access point and radio infrastructure distribute the change to the physical label.
The business area verifies on site that the displayed content, update timing, and assignment are correct.

graph LR;

%% Nodes
A["Change in Business Central"]
B["Approved ESL process"]
C["HTTP/JSON data package"]
D["External ESL platform"]
E["Access point / radio network"]
F["Electronic label"]
G["Visual and plausibility check"]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E
E ==> F
F ==> G

%% Classes
class A btProcessTitle
class B,C,D,E,F,G btProcessActive

Which content typically appears on ESL

The exact display is project-specific. Typical content includes:

Labels and mobile processes on Product Documentation

Mobile processes, BE-Mobile Fusion, and legacy MDE

Purpose

When each mobile path makes sense

Mobile processes are real execution, not just a convenience UI

Electronic Sales Labels (ESL)

Purpose

Important classification

Typical end-to-end flow

Which content typically appears on ESL