Overview:
-
How can I tell if a Major, Minor or Patch Change has occurred in my SettingsID?
- Do you need further help?
When is the banner displayed again?
The banner is displayed in the Admin Interface depending on the configuration of the CMP. You set the preferences in the Configuration section, selecting CMP Settings and scrolling down to Resurface CMP.Please note: The information of your specific CMP setup is saved in the cache of the visitor’s browser. It’ll be deleted and refreshed after 30 minutes – that’s the duration of a session. Therefore, if users still have active sessions, new CMP information will not be taken into account. That’ll happen once the active session has expired.What happens if auto-update is selected?
In that case, if the Data Processing Service is marked for auto-update, it still depends on the selection:
-
Which kind of update has been triggered by the auto-update? and
-
Which options (major /minor /patch) have you selected in the Admin Interface?
Settings-ID → Service Settings → Data Processing Services → select DPS in question → see Version (DPS Details)
If I change the settings for major/ minor/ patch updates, will this affect visitors who already have seen my CMP?
Yes, for example, the admin goes to the Admin Interface and selects major update. The visitor goes to the website and gives their consent. Since it is configured to show the banner on each major update, the visitor will see it again if a major update happens.
How can I tell if a Major, Minor or Patch Change has occurred in my Settings-ID?
This section gives an overview/ introduction about how to notice any change related to the 3 types of patches. We will mainly rely on the Admin Interface to investigate the changes in detail.
Please note: Changes within the Configuration and changes of a DPS can trigger major, minor or patch update(s).
Patch change history
You can check this using the versioning in the Usercentrics Admin Interface with CMP Version 2 under Implementation → Script Tag → Live Version → Version History. Major, Minor and patch changes are encoded in the patch version.Example: Version 6.2.43
- If the first number (6) changes, a major change has occurred.
- If the second number (2) changes, a minor change has occurred.
- If the third number (43) changes, a patch update has occurred.
Major changes
Configuration changes:
-
Add or remove DPS
-
Change Data Controller
DPS changes:
-
Change Data Purposes
-
Change Third Countries
-
Change Recipients
Minor changes
Configuration Changes:
-
Create new category
-
Make category essential
-
Hide essential category
DPS Changes:
-
Change DPS Description
-
Change Cookie Policy
-
Change Privacy Policy
Patch changes
Configuration Changes:
-
Add new language
-
Change layout
-
Change button colors
DPS Changes:
- Change Storage Information
- Change Non-Cookie Storage
- Change max. duration of cookie storage
Connection between updates of Data Processing Services and the Settings Version
Whenever you run a major, minor or patch update (see list above) on a data processing service (DPS), this will also add one count up in the Settings Version.
Example: Your Settings Version is 5.3.7 and you have a DPS in version 2.6.1. You now run a minor update on that DPS. This will result in the Settings Version being changed to 5.4.7 and the version of the DPS being changed to 2.7.1.
Do you need further help?
How can I get help with technical questions?
Comments
0 comments
Please sign in to leave a comment.