Data flow between portal and X-ERP
Understand how portal actions in the central company database become an X-ERP process and how status changes return to the portal user.
The fascinating moment of a portal is the immediate effect: a time posting, message or order is not “received somewhere”, but part of the real process.
A simple moment for the user
The X-ERP portal pages work with the same central company database. This means that status and data can appear promptly - at the same time, authorizations, validation and business rules must be taken just as seriously as in internal X-ERP.
This is how the process works
- Name the portal action, target object, unique ID, status sequence, and responsible role.
- Record a test process in the portal and note the time and visible reference.
- Open the associated data record in X-ERP and check fields, creator and status.
- Edit the process in X-ERP and check the feedback in the portal.
- Test double-click, disconnection, invalid input and missing permission.
How you can recognize a good portal process
- Portal and X-ERP show the same technical status.
- Double action does not produce a second action.
- Error text explains the next step to the user.
- Support finds the process via secure reference.
When the path comes to a halt
- Status is only displayed in the portal and is not technically completed.
- Browser timeout causes re-creation.
- Notification contains more sensitive data than necessary.
This is what you take with you
Portal and X-ERP form a single, comprehensible process with two views tailored to the target group.
Related topics
- For portal users – Unlimited user licenses for portal apps › Portal access, roles and security
- For portal users – Unlimited user licenses for portal apps › X-ERP.ticketsystem – Automate customer service: This is how AI helps you
- For portal users – Unlimited user licenses for portal apps › X-ERP.webshop – Online shop & ERP: Finally a real unit
Frequently asked questions
**Is portal data immediately visible?**
The X-ERP product description emphasizes the central company database and real-time impact; the specific process depends on the app and process.
**What to do after a timeout?**
Don't send twice immediately. Use the reference or list to check whether the process has already been created.