You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

No Automated Upgrade Path Between Versions for DCS RI Template

in Digital Customer Service

There is no automated migration or upgrade path when moving a customized DCS application to a newer Reference Implementation Template version. The only available option is to create a new application from the latest template and manually re-apply all customizations from scratch.

Scenario:We started our implementation using the 26A Reference Implementation Template with significant customization effort invested. The 26B template introduces new Chat / Embedded Service features that are required for our project. Adopting 26B means recreating the entire application and reapplying all changes manually.

Consider a real-world scenario where a customer created and deployed a fully customized DCS application to production last year. The application is live and actively used. Now the customer wants to make use of new features introduced in the 26B Reference Implementation Template. There is no clear or supported path to adopt these new features without rebuilding the application from scratch — which is a significant risk and effort for a live production environment.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!