Upgrading Custom Themes / Less Variables
Upgrading Custom Themes / Less Variables
This section applies to users that have customised their Evolve theme. You can skip this section if you are using the default Evolve theme and have not made any changes of your own.
Failure to Update – Theme Errors
Failure to update your custom theme with Evolve 4’s new LESS variables will result in an error.
Merging Changes Into Custom Theme
To ensure that Evolve 4.0’s pages appear as they should, you must copy the new variables into your custom theme files. These variables are listed on the next page.
New Variables in 4.0
The following variables are new to Evolve 4.0:
Global search
|
Variable |
Default Value |
|
@cwGlobalSearchFocusColor |
@cwMenuLeftMainNavigationBackgroundColorActive |
|
@cwGlobalSearchTextColor |
@cwMenuLeftMainNavigationTextColor |
|
@cwGlobalSearchBackgroundColor |
@cwMenuLeftMainNavigationBackgroundColor |
|
@cwGlobalSearchResultsTextColor |
@cwFontTextColor |
|
@cwGlobalSearchResultsBackgroundColor |
whitesmoke |
Top Bar
|
Variable |
Default Value |
|
@cwTopBarHeight |
40px |
|
@cwTopBarBackgroundColor |
#ECEFF1 |
|
@cwTopBarProfileLinkColor |
@cwColor2 |
|
@cwTopBarProfileLinkHoverColor |
@cwColor2Shade |
Login Page
|
Variable |
Default Value |
|
@cwLoginTextColor |
@cwTextColor |
|
@cwLoginLabelColor |
@cwColor2 |
|
@cwLoginTextBoxBorderColor |
#CFD8DC |
|
@cwLoginTextBoxFocusBorderColor |
@cwColor2 |
|
@cwSiteSelectionTextBackground |
@cwColor2 |
|
@cwLoadingIconColor |
@cwAccentColor |
Theme File Labelling Convention
Evolve’s LESS variables are named using camelCase whereby the first letter of each word is capitalized – except for the first letter of the whole string. Evolve version numbers are commented out next to any variables that relate to specific Evolve versions. I.e: //v4.0
Custom Logos
The dimensions of custom logos have been changed, they are now:
Image 1
logo.png
146 x 30 px
Image 2
logo-m.png
112 x 30px
Upgrading from Evolve 2.2, 2.3, 2.3.1, 3.0 or 3.1
Upgrading from Evolve 2.2, 2.3, 2.3.1, 3.0 or 3.1
There are no changed configuration options required for your upgrade, but you must still do the following:
•Run the Server Configurator to complete the upgrade.
•Upgrade Your Database so it works with the new version.
•Update each of your Sites so they work with the new version.
Evolve eModeler
Evolve 3.1 introduces eModeler. To ensure that this new feature is enabled for use across your Sites, see Enable BP modeler.
Upgrading from Evolve 2.1
If you are upgrading from Evolve 2.1, quite a lot has changed in terms of Site configuration and setup.
As such, there are a series of steps you should follow in order to complete the upgrade process.
Instructions for upgrading from Evolve 2.1
|
|
These instructions assume you have already upgraded the Evolve application on the web server in accordance with the Installation Guide. |
Upgrading your database to support CW Suite / Evolve 2016 and above
Upgrading your database to support CW Suite / Evolve 2016 and above
These instructions explain how to update your database for new releases of CWSuite and Evolve.
|
|
IIMPORTANT: Before beginning the upgrade process you must make sure that your database user has DBA permissions. |
Step 1 - Backup and Preparation
•It is recommended that you back up your database prior to following these steps.
Step 2 - Ensure you have installed your new version of CW Suite
•Follow the install guide for CW Suite until the step to upgrade your database.
Step 3 - Upgrade the Database
1.Run Command Prompt as an administrator and navigate to the 'bin' directory where CW Suite is installed.
2.Type the following: ValidateRepository.exe-connection:YourConnectionName -username:YourUserName password:YourPassword -upgradedb
3.The Validate Repository tool will do various checks and will display the results of these checks as well as a prompt to commence the upgrade.
If your user does not have DBA permissions, you will see the following message:
If you see this message, you should not proceed with the database upgrade.
Step 4 - Continue with you install instructions for Evolve as required
•Install Evolve following the information detailed in the installation guide.
Upgrading to Evolve 2.3 from Evolve 2.1
Upgrading to Evolve 2.3 from Evolve 2.1
If you are upgrading from Evolve 2.1 there are several steps you must follow to ensure your Sites are updated to run with the new version.
There are also some changes to file paths and the URLs your Sites can be accessed via that you should understand.
If you previously used Workflow in Evolve, please read this important message:
Important message for Workflow users
The mechanism for providing workflow capabilities within Evolve has changed completely in this release.
While any workflows you may have previously configured will still work in Evolve 2.3, all existing Tasks and Notifications will be lost.
If you need assistance preserving existing Tasks and Notifications, please contact the erwin Support Team.
Stepsfor Updating Sites
|
|
These instructions assume you have already upgraded the Evolve application on the web server machine in accordance with the Installation Guide. |
To ensure a smooth transition to the new version, follow the steps below:
1. Understand multiple Sites, the new URLs, file paths and directories
Learn about the URLs, file paths and directories used in Evolve 2.3.
2. Run the Server Configuration utility
Use the Server Configuration utility to ensure your Evolve IIS Site is configured correctly.
3. Update and publish existing Sites
For each existing Site you want to use in Evolve 2.3, ensure you follow the instructions for Updating an existing Site.
4. Learn how to create and configure a new Site
Now Evolve supports multiple Sites, learn how to Create a Site.