Difference between revisions of "UCS/Current/UCSPEGuide/Planning"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
(Published)
Line 41: Line 41:
 
*GWS Environment Service
 
*GWS Environment Service
 
|GDPRStatus=No
 
|GDPRStatus=No
−
|GDPRText={{Notices|Notice=PEComingSoon}}
+
|GDPRText=As a part of GDPR compliance procedure, the customer would send a request to Care providing the information about the end user. Care would then open a ticket for Engineering team to follow up on the request.
 +
 
 +
The engineering team would process the request:
 +
===GDPR request: Export Data===
 +
 
 +
*Request to UCS to get contact by ID: identify contact (if there is email address or phone number), or <code>getContact</code> (if there is a direct contact ID).
 +
*Request to UCS-X to get list of interactions for contact found.
 +
*Perform CSV export and attach resulting file to the ticket.
 +
 
 +
===GDPR request: Forget me===
 +
 
 +
*Request to UCS-X to get contact by ID: identify contact (if there is email address or phone number), or <code>getContact</code> (if there is a direct contact ID).
 +
*Request to UCS-X to get list of interactions for contact found.
 +
*Delete all found interactions.
 +
*Re-check that all interactions for contact were removed.
 +
*Delete contact.
 +
*Re-check that contact was removed.
 +
*Update the ticket.
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
}}
 
}}

Revision as of 16:15, June 30, 2021

This topic is part of the manual Universal Contact Service Private Edition Guide for version Current of Universal Contact Service.

Find out what to do before deploying Universal Contact Service (UCS).

Limitations and assumptions

Currently, UCS:

  • supports a single-region model of deployment only
  • does not support SSL communication with ElasticSearch.
  • requires dedicated PostgreSQL deployment per customer.

Download the Helm charts

The UCS Helm Chart is available at:

For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: Downloading your Genesys Multicloud CX containers.


Third-party prerequisites

  • Kubernetes 1.17+
  • Helm 3.0
  • Postgres Database v10+
  • ElasticSearch v7.8+
Third-party services
Name Version Purpose Notes
Elasticsearch 7.x Used for text searching and indexing. Deployed per service that needs Elasticsearch during runtime.ElasticSearch: dedicated (one for UCS-X cluster) as all indices for all tenants are stored in it.
PostgreSQL 11.x Relational database.Dedicated for master DB and for each tenant DB due to high load.

Storage requirements

All data are stored in the PostgreSQL, ElasticSearch and Nexus Upload Service which are external to the UCS.


Genesys dependencies

UCS requires the following Genesys components:

  • Genesys Authentication Service
  • GWS Environment Service

GDPR support

As a part of GDPR compliance procedure, the customer would send a request to Care providing the information about the end user. Care would then open a ticket for Engineering team to follow up on the request.

The engineering team would process the request:

GDPR request: Export Data

  • Request to UCS to get contact by ID: identify contact (if there is email address or phone number), or getContact (if there is a direct contact ID).
  • Request to UCS-X to get list of interactions for contact found.
  • Perform CSV export and attach resulting file to the ticket.

GDPR request: Forget me

  • Request to UCS-X to get contact by ID: identify contact (if there is email address or phone number), or getContact (if there is a direct contact ID).
  • Request to UCS-X to get list of interactions for contact found.
  • Delete all found interactions.
  • Re-check that all interactions for contact were removed.
  • Delete contact.
  • Re-check that contact was removed.
  • Update the ticket.
Retrieved from "https://all.docs.genesys.com/UCS/Current/UCSPEGuide/Planning (2025-06-20 07:32:58)"
Comments or questions about this documentation? Contact us for support!