Modern software systems are no longer isolated solutions. Data exchange with other IT systems is not only necessary to ensure clean functionality. Networked systems are the basic prerequisite for automated, cross-domain processes, which are increasingly shaping the professional world of today. MD-Premium is no exception. The system exchanges information with a wide range of IT solutions. Warehouse data from barcode scanners, sales information from cash registers, time recording data from digital time clocks or data aggregations in BI or OLAP systems are just a few examples of how MD-Premium exchanges data with other systems.
With its REST API, the Webservice Application Framework (WSA) offers a modern and flexible way to connect electronic systems based on web services. The REST API allows controlled access to the entire business logic of MD-Premium. The possibilities of the WSA therefore go far beyond those of an ordinary data interface. In fact, the Multidata web client uses the REST interface to retrieve data and control the system. Together with the extensibility typical for MD-Premium, the WSA opens up almost endless possibilities for integration and data exchange.
Use the web client of MD-Premium and extend it with your own requirements, just as you are already used to with the Windows client. Connect external databases, analytics platforms, and electronic devices of all kinds to MD-Premium to ensure the necessary data exchange with the outside world. Integrate parts of the MD-Premium database and business logic into external web applications and mobile apps to enrich them with ERP functionality.
If data exchange and integration are a major concern for you, the REST API of the Web Service Application Framework provides you with all the options you need to integrate MD-Premium into your IT landscape and develop it into a valuable data hub for your company processes.
REST Interface
REST is a globally standardized paradigm for creating and implementing digital interfaces. The big advantage of REST is its simplicity, compared to other methods.
Since REST is recognized and used worldwide, there is not only an unmanageable number of software products and devices that master this standard. There also is no shortage of specialists with the necessary skills to carry out an integration based on this standard. And thanks to the simplicity and clarity, these integrations are quick to accomplish.
The REST interface of MD-Premium offers secure access, not only to the data in the system, but also to the entire business logic. The integration therefore does not take place at the data level, but at the application level, which opens up enormous possibilities for how MD-Premium can be embedded in your IT and process landscape.
Web client
Modern user concepts cannot avoid mobile scenarios. With the WSA, you implicitly get a complete, web-based user interface for working with MD-Premium. This web client is largely feature-compatible with the classic Windows client, and offers additional, mobile-centric features that cannot be implemented in the Windows client due to their mobile character.
The web client is based on the Angular framework and has been built according to the latest design standards. It can be run on all common platforms and on all common browsers. And in accordance with the ubiquitous "mobile first" doctrine, of course also on mobile devices such as tablets or smartphones.
By using so-called user and customer contexts, you can specify for each resource resp. function in MD-Premium whether it should only be visible to internal users, or whether it should also be displayed in the MD-Premium customer portal and accessible by customers.
B2B Webshop
eCommerce is one of the biggest growth drivers of the global economy and there is hardly a business entity left which does not have a website and a web shop to sell goods and services.
MD-Premium WSA is equipped with a full-fledged B2B web shop that leaves nothing to be desired in terms of an eCommerce platform. The big advantage of this solution is the direct integration of the shop into the ERP module. While conventional stand-alone solutions work with data synchronizations, the WSA web shop retrieves the data directly and in real time from the ERP database.
This ensures that all data displayed to the customer in the web shop is correct. It is ensured that all ancillary aspects resulting from the composition of an order (e.g. small quantity surcharge) are accurately taken into account. It is ensured that the information in the web shop and on the later invoice is congruent and that there are no unpleasant surprises.
And by using the WSA web shop, you eliminiate the need for an additional product that has to be integrated into your ERP system at great financial expense.
Other Features
Mobile functionalities
Mobile functionalities
Workflows specially tailored to mobile devices, such as reading article information via barcode, mobile inventory, warehouse picking and goods registration.
Customer portal
Customer portal
Comprehensive self-service portal to enter service tickets, register newsletters, attend training courses and view order history. The functionality of the portal can be individually extended by using the Customer Context.
Kanban
Kanban
The web client allows the use of Kanban boards to manage process flows. By default, Kanban boards are used in ticket management, but can also be used in other areas (e.g. production orders) if required.
Online-Doku
Online-Doku
Flexible online documentation tool for extensive product documentation of products and services you offer. Allows multilingualism, versioning and modularization. A built-in revision and approval process protects against manipulation.
Mobile functionalities
Mobile functionalities
Workflows specially tailored to mobile devices, such as reading article information via barcode, mobile inventory, warehouse picking and goods registration.
Customer portal
Customer portal
Comprehensive self-service portal to enter service tickets, register newsletters, attend training courses and view order history. The functionality of the portal can be individually extended by using the Customer Context.
Kanban
Kanban
The web client allows the use of Kanban boards to manage process flows. By default, Kanban boards are used in ticket management, but can also be used in other areas (e.g. production orders) if required.
Online-Doku
Online-Doku
Flexible online documentation tool for extensive product documentation of products and services you offer. Allows multilingualism, versioning and modularization. A built-in revision and approval process protects against manipulation.
The product matrix shows all MD Premium features and which module must be licensed in order to use the relevant functionality.
Your questions - our answers
The AFW is the functional basis of MD-Premium, where the entire business logic of the system is stored. The WSA provides a universal interface to other systems based on the REST standard.
The WSA is a standalone product and must be licensed separately
Yes, the web client is based on the WSA
Both, as well. The WSA is the basis for all web-based features of MD-Premium (web client, B2B webshop, WMS, customer portal), which are primarily used by end users and customers. At the same time, the WSA also offers a universal REST interface through which IT departments can establish integrations with other systems, and developers can integrate their own extensions to the system (e.g. as part of a white label project).
In principle, you can access all functions of MD-Premium via the REST API.
The REST interface makes it possible to use individually compiled authentication workflows that combine different methods (Webauthn, OTP, User/Password, Access Token...) to log in to the system. For dedicated API users (server-to-server), a secret procedure (very long password) is typically used.
No. The API documentation is not publicly available and is only made available to customers and partners.
Yes, the API basically allows any access to the system. It is up to the respective implementation or assignment of rights to decide which access is actually allowed and which is not.
In order to access the REST API, a corresponding user must be defined in the system, which then receives the necessary access rights via rights management.
No, such a mechanism is not currently planned. Since a customer usually does not make the REST API publicly available, but only uses it in clearly defined connections with previously known usage profiles, the enforcement of a fair use policy is typically not necessary.
The two clients are largely identical in their features. The biggest differences are in the appearance, in the operation, as well as due to a certain streamlining in the structure of the web client (different arrangement of functions, streamlining/merging of menu items).
However, due to the possibilities of implementing mobile applications via the web client, there are certain functions that cannot be displayed in the Windows client (WMS, mobile inventory, document signature). And in general, new developments are first implemented on the web client and only transferred to the Windows client when necessary.
The system supports all common browsers that properly implement the W3C standard. The operating system does not play any role in this.
The web client is based on Google's Angular framework.
Yes. The web client can be configured and extended via XML definition files in a similar way to the Windows client. However, to edit the XML resources, you need the repository explorer, which is currently only available for Windows clients.
Functions and masks that have been defined for the user Kontext run within the framework of the MD-Premium web client, i.e. they are intended for system users. The Customer-Kontext runs within the framework of the customer portal and is specifically intended for use cases from the customer's point of view.
The B2B webshop is directly integrated into the ERP database of MD-Premium. All data displayed in the webshop corresponds to the current data status of the system or is calculated using the same methodology as the ERP and is therefore congruent.
Yes, the webshop sees or calculates the same data as the ERP.
Yes, article variants are supported.
The order history can currently be viewed via the customer portal, not via the webshop itself.
The focus of the webshop is on B2B, where they want to provide existing customers with a fast method without frills to store orders in the system. For B2C uses, appropriate payment methods would have to be integrated, as well as a much greater focus on marketing measures within the webshop, which is not planned at the moment.
The design is free to customize and is typically determined in collaboration with our project team.
The following functions are available as standard: user profile (incl. newsletter management), customer master data, order history, service tickets, booking of training courses/events, document signature
Further functions can be activated on an individual basis via the Customer-Kontext, if desired.
Yes, this is one of the standard features of the customer portal
A separate access can be set up for each contact person that is stored in the system for a customer. In addition, it can be determined which actions this person is allowed to perform in the customer portal.
No, native apps are not planned at the moment.
The following workflows are supported in conjunction with an Android-based scanner: item information, warehouse transfer, goods transfer, warehouse picking, inventory.
There must be a connection to the MD-Premium Server. An offline mode is not available and is not being considered at the moment.
Any system that supports the REST standard can be connected via the WSA.
Yes, such scenarios are possible.
Customers and partners who wish to expand the REST interface on their own will receive comprehensive training in the topic from Multidata.
Customers receive a newsletter with the release notes for the current product version with every product update.
Authentication is carried out via freely selectable multi-factor methods (e.g. Webautn, OTP, Access Token, etc...). MD-Premium uses common transport encryption based on TLS. In addition, mechanisms have been built into the authentication layer that make man-in-the-middle attacks more difficult. A VPN can be used for even higher security, but this is an infrastructure measure that must be carried out outside of MD-Premium. MD-Premium itself does not offer end-to-end encryption.
The AFW framework itself does not allow restrictions based on IP addresses or networks. Such restrictions must be set up at the system level (e.g. firewall, IIS manager).
The system logs all authentication processes (login/failed login/logout) and stores them permanently in the system. Which actions are called via a specific API login is not logged by default. It is possible to activate complete logging at database level (e.g. for debugging, security analyses). However, for performance reasons, this measure should only be taken in urgent exceptional cases and in consultation with Multidata.