Upgrading Silk UI
We encourage you to always upgrade to get the latest and greatest.
Silk UI has a specific team at OutSystems that is working to improve and evolve Silk UI, so periodically there will be new releases with bug fixes and new features.
We take special care in avoiding breaking changes at all costs, but be sure to review the version's history in Forge to validate how these could affect your applications.
To upgrade, follow the normal Silk UI installation process, but instead of an Install button, you will be prompted with an Upgrade button:
What qualifies as a Breaking Change in Silk UI
Anything that breaks references between modules (change of parameters, for instance) or CSS changes that affect the look and feel in an obvious way is considered a breaking change.
Checking the Version of Silk UI Installed
Mobile
To check the version of Silk UI Mobile, just change the server address accordingly and access the following URL:
https://[myserver]/MobilePatterns
Web
To check the version of Silk UI Web, just change the server address accordingly and access the following URL:
https://[myserver]/WebPatterns
Upgrading to OutSystems 10
With OutSystems 10, when you install Silk UI, it is no longer available from Service Studio, as it would happen in previous versions. This keeps our framework’s integrity and ensures that you continue getting the updates without any bumps in the road.
If you changed any of the original Templates, you should clone them in a separate application to avoid losing your work after an upgrade.
You can download or publish Silk UI and all Templates via Service Center.