GDPR compatibility
Due to the GDPR, users should be made aware of which personal data or personalized settings are saved when using the application. In addition, the possibility should be given that these can be set individually (privacy settings).
In the BPC frontend, ExtJS components are affected that store their state (state).
These states are stored in a StateProvider (usually LocalStorage or CookieStorage).
Due to the GDPR, some states that are not absolutely necessary for the functioning of the application should only be saved if the user allows it.
In the following, we will only refer to cookies, even if other technologies such as local storage are used for storage.
|
In order for the user to be able to control the behavior, a cookie must be stored under Core Services |
A user can choose which cookie categories he allows. He can deselect all unnecessary categories.
Cookie Categories
Currently there are the categories
-
Necessary
-
Personalization (ID:
personalization)
If further categories (e.g. marketing) are required, please contact us. Marketing) are required, please contact support.
Assign components state to a category
A prefix in stateId can be used to define whether a component is assigned to a defined category.
To do this, the prefix must be the same as the ID of the desired category.
If this is not the case, it is always assumed that it belongs to the "Necessary" category.
The prefix is separated from the rest of the ID in stateId with the $ character.
stateId: "personalization$my_state_id"
Manual check of authorized categories
If the user selection needs to be checked from the cookie itself, this can be done as follows.
Ext.state.Manager.getProvider().get("optionalCookieSettings");{
"personalization": true
}This returns an object with all categories that the user has approved. Rejected categories do not have to be included in the object.
