Overcome Compliance Challenges with Nintex

The European Union’s (EU) General Data Protection Regulation (GPDR) decision has been a hot topic in the news recently.  The other hot topic has been Germany’s new law against hate speech, known as NetzDG.  These laws will not only have an impact on EU based businesses, but any company that does business there.

A quick summary about what GPDR is designed to do.  The law is designed to put personal user data back in the individual’s control.  This includes, but not limited to, companies having to ensure proper safekeeping of personal data, the individual’s “right to be forgotten”, and the right to access data about them.

What is NetzDG?  This law was enacted to ensure that social media companies and others that host third-party data maintain procedures for handling complaints about potentially harmful content.  That content must be removed or access blocked within 24 hours from the time of the complaint. Fines for failure to do so can be substantial, up to 50 million Euros.

So, you may be asking by now “How can Nintex ensure my company’s compliance?”

Process automation is the key to ensuring compliance and risk management.  With Nintex, the solution is not a costly and lengthy process to put in place.

Consider this NetzDG example.  You have an open discussion in SharePoint about future changes to site.  As tends to happen at times, the discussion can get heated and some comments are said that may not be legal.  In a small community, posts can be handled by a moderator, but for larger communities this can become a full time job.  This is where Nintex comes to the rescue. A Nintex workflow can take the place of a moderator and automate the content approval.

Here is how the content moderation would work.  Once a user provides their input and hits submit, a process in the Nintex Workflow Cloud is triggered.

• The content is sent to the Content Moderator API.  This step is achieved by either the “Call a Web Service” action or by building a connector using the Nintex Xtensions Framework
• The results are queried and checked for any unlawful words
• If any content is to be moderated, the workflow will alert the discussion moderator(s)
• If the content is good to go, it will be posted to the community.

  
As you can see, this is simple and straightforward to implement.  I used a simple example to demonstrate how the Content Moderator API and Nintex can be used, but this solution can be applied to any content that may require moderation.  A simple solution to ensure compliance and ease of mind.