Simplified Updates, No More Upgrades
Customers running a modern Siebel CRM version can take advantage of the new Repository Update utility. This streamlines the adoption of monthly Siebel CRM Release Updates, allowing you to adopt new features while preserving your existing customizations with dramatically reduced effort and resources.
A bulky "Siebel Upgrade" is no longer required. No need to spend huge amounts of time resolving repository conflicts. With the modern Siebel CRM application, applying proudct updates and unlocking new innovation is a easy.
What is Siebel Repository Update?
With older Siebel CRM releases, to apply a Monthly Update from Oracle, there was a process known as “RepositoryUpgrade”, which updated the Siebel CRM environment to incorporate Repository changes, schema changes, seed data, and other modifications introduced by new features.
This utility delivered optional Repository changes made by the Oracle Siebel CRM development team. During execution, the RepositoryUpgrade utility imported data from the intervening releases since the last time it was run. If the Siebel CRM environment was not kept upto-date regularly with the latest Siebel CRM Monthly Updates, then the number of Repository changes that must be applied increased as well, leading to greater effort and cost involved with applying a Siebel CRM Monthly Update.
The old "RepositoryUpgrade" process has been replaced with the new “Repository Update”. This new process reduces the number of changes made by the utility, with an overall benefit of a smoother uptake of the content introduced in a Siebel Monthly Update, allowing customers to leverage new features more easily than before.
Update Siebel, Not Upgrade Siebel
01No more Upgrades
Starting Siebel CRM 26.1, the need to run "RepositoryUpgrade" to apply an Oracle Siebel CRM Release Update is now finished. Superceded by the new more efficient "Repository Update" process.
02Simplified Siebel Updates
Starting Siebel CRM 26.1, with the new "Repository Update" process you can experience almost zero repository conflicts when you apply a monthly Siebel CRM Release Update.
03Unlock New Innovation
Due to the lack of repository conflicts in the reduced Update package and the fact that new features tend to be additive to the standard repository, it is much easier and less risk for organizations to introduce new features and functionality.
04Reduced Testing
More focused repository changes help Developers to understand the minimal testing effort required.
Say Hello to almost zero conflicts
Starting with Siebel CRM 26.1 release, the new Process for distributing repository changes is called "Repository Update". This new process reduces the number of changes made by the utility, with an overall benefit of a smoother uptake of the content introduced in a Siebel Monthly Update, allowing customers to leverage new features more easily than before.
- The distrbuted package for our Monthly Releases now only includes the true delta from previous releases. Rather than ship entire objects, we ship only things that have specifically changed. Therefore the payloads are dramatically reduced, smaller packages, faster to install.
- In our Monthly Releases, any new features or repostiory updates now contain only attribute-level changes (as opposed to entire objects). As there are fewer conflicts to resolve this leads to a dramatically reduced effort.
- The more focused payload provides a clear focus for Developers to see exactly what changed. This leads to a reduction in testing time as they only need to focus on the changed areas that you are using.
Say Goodbye to Siebel Repository Upgrade
Previously, the "RepositoryUpgrade" process was used to apply Oracle-provided repository changes to the customer repository, typically to deliver configuration changes supporting application (end-user) features.
Given that one of the key differentiators with the Siebel CRM product is the almost unlimited ability to configure everything, many customers have highly configured repositories. This meant that when they performed the "RepositoryUpgrade" process there could be conflicts and overwrites causing corruption to the customized repository.
These issues need to be resolved manually, and as a result there could be a long “retrofit” and test cycles for resolution.
Starting from the Siebel CRM 26.1 Release Update, the "RepositoryUpgrade" process is no more. It is replaced with a new, much leaner and more efficient process for distributing repository changes called "Repository Update".
With "Repository Update" we expect to eliminate 99% of Monthly Update repository conflicts. This will saving organizations a lot of time and effort, allowing them to stay more current with the Siebel CRM application than ever before and introduce new features easily.