On July 13, 2018, an update was made to Cvent’s SOAP API calls which may require you to download the newest version of Cvent’s WSDL file. This update was made to comply with GPDR “right to be forgotten”. Cvent will perform obfuscation to anonymize a person’s record when a GDPR “right to be forgotten” request is submitted. When a request is received, Cvent will mask the contact’s information and flag them as obfuscated.
What is changing and why?
Now contacts/invitees and guests can be obfuscated from Cvent’s Address Book. This update will add a new “is_obfuscated” flag to the Contact and Guest objects and the field will be read only and searchable.
What calls will be affected?
- Create Contact: No change. The value for “is_obfuscated” field will not impact the contact creation. Any new contact created will be saved with this value as false.
- Update Contact/Upsert Contact: This will not let users update the contacts that have already been obfuscated. If a user tries, the output will return an error message, “Obfuscated contacts cannot be updated. New error code for this: CV40127.”
- UpdateGuestInfo: This will not let users update any guests that have already been obfuscated.
- Retrieve: This will return the value for contact fields based on whether the contact is obfuscated or not.
- Describecvobject: This will return the object with the field type for the “is_obfuscated” field.
Note: Updates will require changes to Cvent’s WSDL file.
The “is_obfuscated” flag will be “true” for any record that has been anonymized as a result of a “right to be forgotten” request and “false” for all other contacts/invitees and guests. As part of “right to be forgotten,” clients/planners can request Cvent to forget any of their invitees from Cvent.