Refactoring limits¶
This page explains what cannot be automatically rebuilt during refactoring and how to handle these gaps.
How it works¶
Refactoring rebuilds your services based on what is visible and documented. If an operation happens "behind the scenes" without leaving traces, the system cannot guess it.
For example: if in your old system an order of 50 euros automatically triggers a 10% discount but this rule is not written in any manual and does not appear on any screen, the new service will not know it has to do it.
What you need to do¶
- Analyze the processes you use every day and mark those that happen automatically without you having to click anything.
- Report to glacom® every integration with external software that is not visible in the user interface.
- Verify the data in the old system: if there are incomplete records or errors, you must clean them before [migrazione-dati.md].
- Test the functions carefully during the [periodo-parallelo.md] to find forgotten logics.
What glacom® does¶
It analyzes the screens and flows provided to rebuild the structure. If a missing function emerges during testing, it intervenes to add it following the [../errori-e-correzioni/aggiungere-quello-che-manca.md] procedure.
Limits¶
Refactoring cannot rebuild: - Hidden logics: calculation rules or automations that were never documented and are not visible in the interfaces. - Closed integrations: connections with third party systems that cannot be accessed or that do not expose data. - Corrupt data: if the information in the old system is wrong or incomplete, the new service will inherit the error.
Frequent problems¶
- A function that was there before is missing? → It was probably a hidden logic: report it immediately via a [../supporto/ticket.md].
- The new system gives errors on some data? → Check if the original data was correct or if it is corrupt at the source.
- An external software is no longer communicating? → Check if the integration was based on undocumented access.
From the app
Not available from the app: the management of refactoring limits happens exclusively through direct coordination with the project team.