You can use HTML Dialog overrides to customize the UI or specific parts of it. This generally works well, but in some cases, the override doesn't take effect, and the uncustomized view is displayed instead.
Since the introduction of this feature, we've supported a mechanism called case override, which attempts to automatically determine the correct project that provides the customized UI. However, if you're experiencing issues, we strongly recommend using strict overriding by explicitly specifying the OverrideProject in your app.yaml file. This ensures that the engine uses the correct project for the customized UI components. You can find more information here:
https://dev.axonivy.com/doc/12.0/engine-guide/configuration/files/app-yaml.html
Despite this, users have occasionally reported that the uncustomized view still appears. This behavior was difficult to reproduce for a long time, but we’ve possibly recently identified the root cause. It appears only under very specific conditions:
- When the Axon Ivy Engine has just been started, or
- Immediately after deploying projects,
- And if the first request occurs outside of a task context.
In such cases, the uncustomized view is loaded and cached. Unfortunately, once this happens, the system continues to serve the cached version. The only way to recover is to restart the Axon Ivy Engine, redeploy the project, or stop and start the application again.
Seems to be fixed now for the next releases: 10.0.30, 12.0.8 and 13.2.0
