Hi Mike O! Thanks for your questions about GDPR. I should probably put a notice up in the GDPR space that it was intentional to make the space view only. Due to legal sensitivity we want customers to direct all questions about GDPR to their account managers who are equipped to get you the accurate information you need. Please reach out to your account manager (let me know if you aren't sure who that is) regarding these questions.
Hope this helps!
2 people found this helpful
Dear Sarah -- thank you for your note.
I raised mine both publicly and as a private case since this general question, the answer and its awareness should be seen by my fellow ECMs as they make their own preparations. I believe this consideration was the driving factor behind the two buttons presented as I start to open a support case : (1) create a public discussion, or (2) start a private case.
These datasets do seem to qualify for protection under GDPR and so far have not been addressed in other communication from Aurea.
In case the answer involves my taking a peek at more sensitive information, such as the "secret sauce" that drives the internal algorithms and how they work, then indeed I agree a private conversation is warranted.
However, I do hope to receive an official answer to this general question here in this public forum. Unless otherwise instructed, I plan to post here any generic answer I receive in my support case. --Mike O.
1 person found this helpful
Agreed. A lot of this is not private & should (IMO) be public to help everyone work together on this & gain some reassurance that everything will be covered when we upgrade to 9.0.4.
In the absence of anything in the UI so far, or any documentation on new APIs that are in 9.0.4, I've been putting together some pages as a contingency plan. One covers data portability and gives the user this page;
It relies on the Jive REST API & documentation including everything they'd need to meet the portability requirement.
Sorry for the delay I was chatting with our legal team. It was decided to keep the GDPR space and answers private, so we would appreciate your cooperation with that decision. Legal also wanted you to be aware that the confidentiality agreement is between you and Jive, not between one Jive customer and another Jive customer.
I personally don't see a problem with publicly listing questions that other customers may find helpful to ask themselves, but relaying answers to all customers that were passed specifically to you and your account is playing a game of telephone that could cause issues and misunderstandings. I've already put in the recommendation to have an FAQ based on common customer questions created, but the final decision on that front is not up to me.
I absolutely appreciate your dedication to share information that can help out fellow customers (because that's what Jive is for!), but in this case we want to make sure everything goes smoothly and we are prepared to answer these questions individually.
Hi Sarah - thank you for your note and your work behind the scenes. please could you clarify what constitutes content which can be shared between customers? Is GDPR to be the exception, or the rule?
With the recent leakage of fellow ECMs' frustration with support into public forums especially as regards outages, degradations etc., there is considerable precedent here where folks have copy/pasted or summarized answers from their support cases. -Mike.
2 people found this helpful
I am specifically referring to GDPR as the exception since it is a new EU law that needs to be handled with care. We absolutely encourage collaboration in AureaWorks (sharing is caring ) regarding other less sensitive topics.
You do bring up a great point regarding recent frustrations. While we are indeed concerned that community members are probably copying content directly from their cases without permission from their company (we have the private support channel for a reason), that is a separate concern from this specific thread.
Hope this clarifies things a bit. These are great questions, thanks for asking them!