Fiori Deployment Part 3: Versioning, Caching and UI5 Version Management

📌 KEY POINTS
✅ Each app version should be identifiable via the manifest version and release notes.
✅ Cache busting ensures browsers load new files after deployment.
✅ On BTP, apps can specify the UI5 version they load; on ABAP, the system's UI5 version applies.
✅ UI5 versions have maintenance periods; long-term maintenance versions are preferred for stability.
⚠️ Custom apps on outdated UI5 versions break when the version goes out of maintenance or the system upgrades.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This final deployment part covers keeping apps working after go-live.

━━━━━━━━━━━━━━━━━━━━
▶ 1. VERSIONING APPS
Increase the app version in manifest.json with each release and keep release notes. Support can then see which version a user runs, and rollbacks are clearer. Pipelines can set versions automatically.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CACHE BUSTING
Browsers and intermediate caches may keep old files. Cache busting adds version tokens to resource URLs so a new deployment produces new URLs. On ABAP, cache buster tokens are maintained per app; on BTP, the HTML5 repository and approuter handle versioned content.

━━━━━━━━━━━━━━━━━━━━
▶ 3. UI5 VERSION ON BTP
Apps on BTP can bootstrap a specific UI5 version from the CDN, defined in the app or its configuration. Pinning to a version gives stability, but the version must be updated before it leaves maintenance.

━━━━━━━━━━━━━━━━━━━━
▶ 4. UI5 VERSION ON ABAP
On-premise front-end servers deliver a UI5 version with the system; all apps there use it. System upgrades bring newer UI5 versions, so custom apps must be tested and adjusted for deprecated APIs as part of upgrade projects.

━━━━━━━━━━━━━━━━━━━━
▶ 5. UPGRADE READINESS
Use the UI5 linter, follow deprecation notes, avoid private APIs and DOM manipulation, and keep automated tests. Track UI5 maintenance status and plan updates yearly. Apps built this way move to new versions with little effort.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Check the manifest version and release notes of one app.
2. Verify cache busting after a deployment.
3. Find which UI5 version the app runs on in each environment.
4. Run the UI5 linter and list deprecated usages.

✅ CHECKPOINT: each app has a visible version, users get updates reliably and UI5 version risk is known.

After an S/4HANA upgrade brought a newer UI5 version, three custom apps failed because they used private APIs and synchronous loading. Fixes took weeks. The team introduced the UI5 linter in the pipeline and a yearly UI5 health check for custom apps.

• No app versioning.
• Missing cache busting.
• Pinned UI5 versions left unmaintained.
• Private APIs in custom code.

• Automated versioning and release notes.
• Cache busting verified after deploy.
• Track UI5 maintenance.
• Linter and tests in CI.

Interviewers ask how you make sure users get new app versions, how UI5 versions are managed on ABAP vs BTP and how you prepare custom apps for upgrades.