...
Table of Contents | ||||
---|---|---|---|---|
|
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Comparison of the Viewer versions
|
Section |
---|
CustomizationDue the new layout of the viewer it also affects the customization of it (e.g. there is only one logo anymore required). We integrated a automatic migration of the customization, nevertheless, it is recommended to test the customization before upgrading the system. Moreover, if you are using a custom.css, please verify the customization before upgrading your system (private SaaS or on premise). Shared SaaS customer is recommended to test their customization on our demo plattform, before the shared SaaS instance gets upgraded. Contact your Namirial consultant or our support for more details. |
Section |
---|
Testing of the new ViewerJust create a demo organizaton on our demo platform. |
Section |
---|
Changes in the CustomizationThe following list should be used for a better understanding of
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section |
---|
Automatic Migration LogicThe customization gets automatically migrated to the new viewer during the upgrade by the following rules:
|
Section |
---|
How to change customizations after updateWhen the new eSignAnyWhere 3.5 (with subcomponent SSP 4.20) will be installed on a server, the migration will be performed and most of the values should already fit to the old design behaviour. Nevertheless, if there are still customizations, that do not fit to the new SignAnyWhere Viewer design, there are two possibilites: 1) Recommended: Using new 3.5 (SSP 4.20) Customization.zipGo to the eSAW organisation and download the current design. By doing this, you are getting a 4.20 Customization.zip including all new keys including the above described migrations. You just need to find the new keys and adapt the values as you want. 2) Alternative: Using old 3.4 (SSP to 4.19) Customization .zipIf you are using an old Customization.zip file what was generated from <= 4.19 SSP, then you have the old keys inside the Customization.zip file. If you want to change values in the old Customization.zip, you need to change the value of the old key! |
...