Sitecore tips and tricks and community news !

Post Top Ad

Post Top Ad

Thursday, August 30, 2018

xCommerce - GDPR approaching

We are developers, so we like coding, making something that work and make it possible to say - "It's alive!". But last days, we are also has to be aware of other life parts that have an influance on our work. Especially the most often case is - Law.

Why Law? My old friend said few years ago:

"You cannot drive own business without a lawyer."

What means that if you want to have a company, you have to make it according to the law rules. Hence, we as a developers mostly, work on projects that solves issues for our clients that have own business. So we as a developers must endeavour to deal with law constraints.

Going ahead with introduction above we come to the topic of GDPR.



In my current project where we use awesome technology stack like: Sitecore 9.0.2 + SXA 1.7 + xCommerce in the newest version we also struggling with GDPR constraints.

Of course everybody knows that Sitecore 9 provides functionality to anonymize (I hope this word exists in English 😉) users data. But what about xCommerce?

Well, in general xCommerce by default is not removing users from DB, but making "soft delete". It means that is selecting this user as an inactive guy.
It's done in particular purpose. To keep possibility for returns, guaranty rules and so on. But if somebody is still wants to get ride of users that ask about this possibility basing on GDPR, what we can do?

We can change standard xCommerce behavior and make possible "hard delete" users. To do that we can change the settings. In:
CommerceAuthoring_Sc9\wwwroot\data\Environments\PlugIn.Habitat.CommerceAuthoring-1.0.0.json we have:


Since the "ForgetCustomer" setting is set to true, the removing action in the UI removes the user completely, making "hard delete".  Propagation will take about 5 minutes for minion which will update the index, and you will see the changes.  

This is it, I hope it will help for someone!

No comments:

Post a Comment