Cargo query

Showing below up to 100 results in range #101 to #200.

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)

Page	ThirdPartyItem	Notes	Variation
Draft:PEC-REP/Current/PulsePEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283
Draft:PEC-REP/Current/PulsePEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Note: Pulse does not currently support Redis Cluster; use Redis in stand-alone mode.
Draft:PEC-REP/Current/PulsePEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1
Draft:PEC-REP/Current/PulsePEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86		No
Draft:PrivateEdition/Current/TenantPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	NOTE: Starting with version 100.0.100.0041, Tenant Service supports PostgreSQL 11.x. Before deploying Tenant Service, you must provision a PostgreSQL database for Tenant Service using one of the following methods: Create a PostgreSQL database specifically for use by Tenant Service. Use the shared PostgreSQL database, which is recommended in the OpenShift platform. Deploy a PostgreSQL database using the following commands:?'"`UNIQ--source-0000004B-QINU`"'?During deployment, you require the database information, including credentials. For the list of database parameters that you override in the Tenant Helm chart values.yaml file, see Backend parameters in Override Helm chart values.
Draft:PrivateEdition/Current/TenantPEGuide/Planning	2afd763e-337c-47eb-8428-3bafcc89dbca	Starting with version 100.0.100.0041, Tenant Service supports Consul 1.10.
Draft:PrivateEdition/Current/TenantPEGuide/Planning	2f69518e-33af-4c0f-adcc-a98e5427e5e0
Draft:PrivateEdition/Current/TenantPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd
Draft:PrivateEdition/Current/TenantPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
Draft:STRMS/Current/STRMSPEGuide/Planning	2936260e-26af-4170-a54f-30ce99564b4b
Draft:STRMS/Current/STRMSPEGuide/Planning	2f69518e-33af-4c0f-adcc-a98e5427e5e0		No
Draft:STRMS/Current/STRMSPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	This Redis instance must be a dedicated & non-clustered Redis instance. Support for clustered Redis is planned for a future iteration of Event Stream.
Draft:UCS/Current/UCSPEGuide/Planning	0d238336-2626-4954-8be3-2f1e16fdd0ce	Dedicated (one for UCS cluster) as all indices for all tenants are stored in it. UCS does not support SSL communication with Elasticsearch.
Draft:UCS/Current/UCSPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	Dedicated for master DB and for each tenant DB due to high load. DB users must have super user privileges or the following PostgreSQL extensions must be installed before deploying UCS-X service: pg_prewarm intarray
Draft:UCS/Current/UCSPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1	You can use any Docker OCI compliant registry.	No
Draft:UCS/Current/UCSPEGuide/Planning	bc90a902-fc45-4546-b05b-bba8f567dba2	If UCS is accessed from outside of a K8s cluster, it is recommended to deploy/configure an ingress controller (for example, NGINX), if not already available.	No
Draft:UCS/Current/UCSPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86	For UCS, a single regional Google external network LB will be setup as part of the platform setup.	No
Draft:VM/Current/VMPEGuide/Planning	2afd763e-337c-47eb-8428-3bafcc89dbca	For additional information, see Voice services configuration in Consul.
Draft:VM/Current/VMPEGuide/Planning	2f69518e-33af-4c0f-adcc-a98e5427e5e0
Draft:VM/Current/VMPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd
Draft:VM/Current/VMPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
Draft:VM/Current/VMPEGuide/Planning	f006784a-0bf7-42b7-9838-033f4acb61fe	Required for Voice Voicemail Service if you integrate voicemails with email.	No
Draft:WebRTC/Current/WebRTCPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
Draft:WebRTC/Current/WebRTCPEGuide/Planning	45f198e3-934c-4b6f-848a-393bd81773fe	KEDA can be enabled or disabled for WebRTC. But, WebRTC cannot be configured to use HPA instead of KEDA.	No
Draft:WebRTC/Current/WebRTCPEGuide/Planning	9196f7d6-6782-467f-a664-627a2c293000		No
Draft:WebRTC/Current/WebRTCPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86		No
GVP/Current/GVPPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	The GVP Configuration Server is separate from the Tenant Configuration Server and requires its own database.	No
GVP/Current/GVPPEGuide/Planning	2936260e-26af-4170-a54f-30ce99564b4b	The following features must be enabled in Consul: Service Discovery – to register MCP service for auto discovery of MCP pods by RM	No
GVP/Current/GVPPEGuide/Planning	29577a1d-7351-4c78-8369-62f84d696d05		No
GVP/Current/GVPPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
GWS/Current/GWSPEGuide/Planning	0ce020f7-57d0-430e-bd82-27bef7d7834c
GWS/Current/GWSPEGuide/Planning	0d238336-2626-4954-8be3-2f1e16fdd0ce	GWS requires Elasticsearch 7.17+. You must configure additional options for Elasticsearch to support the Data Collector Service.?'"`UNIQ--syntaxhighlight-00000016-QINU`"'? You can set up Elasticsearch as a shared or dedicated service.	Yes
GWS/Current/GWSPEGuide/Planning	17ed8d61-7149-43bb-8f0e-199f7d206ec8
GWS/Current/GWSPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	GWS supports PostgreSQL 12.x. You can set up PostgreSQL as a shared or dedicated service.	No
GWS/Current/GWSPEGuide/Planning	2afd763e-337c-47eb-8428-3bafcc89dbca	GWS supports Consul 1.8. Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent.	Yes
GWS/Current/GWSPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	The Redis server must run in cluster mode. You can set up Redis as a shared or dedicated service.	No
GWS/Current/GWSPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
GWS/Current/GWSPEGuide/Planning	9196f7d6-6782-467f-a664-627a2c293000		No
GWS/Current/GWSPEGuide/Planning	bc90a902-fc45-4546-b05b-bba8f567dba2
GWS/Current/GWSPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86
IXN/Current/IXNPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283		No
IXN/Current/IXNPEGuide/Planning	2936260e-26af-4170-a54f-30ce99564b4b		No
IXN/Current/IXNPEGuide/Planning	2f69518e-33af-4c0f-adcc-a98e5427e5e0	Kafka is required to deliver IXN reporting events to Genesys Info Mart (GIM). It is the same Kafka for GIM and IXN Server.	No
IXN/Current/IXNPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Redis is required for communication between Orchestration Server (ORS) and IXN Server. It is the same Redis for ORS and IXN Server.	No
IXN/Current/IXNPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
PEC-CAB/Current/CABPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	Before you deploy Genesys Engagement Service (GES), a table and user with database owner (DBO) permissions must be deployed and ready for use by GES. You require the following information for GES deployment: Database name Database port Database hostname Database user
PEC-CAB/Current/CABPEGuide/Planning	2afd763e-337c-47eb-8428-3bafcc89dbca
PEC-CAB/Current/CABPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	You require the following information for GES deployment: Redis hostname Redis password (only required if you use a password) Redis port You require access to the Voice Microservices deployment Redis as well (specifically the Voice Orchestration Service Redis stream). You require the following information about the Voice Microservices Redis for your GES deployment: Redis hostname Redis password (only required if you use a password) Redis port
PEC-DC/Current/DCPEGuide/Planning	0ce020f7-57d0-430e-bd82-27bef7d7834c
PEC-DC/Current/DCPEGuide/Planning	17ed8d61-7149-43bb-8f0e-199f7d206ec8
PEC-DC/Current/DCPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	No support for enforced SSL.
PEC-DC/Current/DCPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Digital Channels supports Redis deployed in either cluster (TLS) or non-cluster (non-TLS) mode.
PEC-DC/Current/DCPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
PEC-DC/Current/DCPEGuide/Planning	9196f7d6-6782-467f-a664-627a2c293000		No
PEC-DC/Current/DCPEGuide/Planning	bc90a902-fc45-4546-b05b-bba8f567dba2
PEC-DC/Current/DCPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86
PEC-DC/Current/DCPEGuide/PlanningAIConnector	0ce020f7-57d0-430e-bd82-27bef7d7834c
PEC-DC/Current/DCPEGuide/PlanningAIConnector	17ed8d61-7149-43bb-8f0e-199f7d206ec8
PEC-DC/Current/DCPEGuide/PlanningAIConnector	1a407778-58fe-4acd-8ca7-5af8eac31283	No support for enforced SSL.
PEC-DC/Current/DCPEGuide/PlanningAIConnector	3aee73ed-68e0-4c70-8693-2421c68b86cd	AI Connector supports Redis deployed in either cluster (TLS) or non-cluster (non-TLS) mode.
PEC-DC/Current/DCPEGuide/PlanningAIConnector	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
PEC-DC/Current/DCPEGuide/PlanningAIConnector	9196f7d6-6782-467f-a664-627a2c293000		No
PEC-DC/Current/DCPEGuide/PlanningAIConnector	bc90a902-fc45-4546-b05b-bba8f567dba2
PEC-DC/Current/DCPEGuide/PlanningAIConnector	f1d380bf-42b1-4b67-9d27-d574bad90c86
PEC-Email/Current/EmailPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Dedicated - one per deployment of Email
PEC-Email/Current/EmailPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
PEC-IWD/Current/IWDDMPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283
PEC-IWD/Current/IWDDMPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-IWD/Current/IWDPEGuide/Planning	0d238336-2626-4954-8be3-2f1e16fdd0ce	Dedicated - one per deployment of IWD
PEC-IWD/Current/IWDPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	Dedicated instance for each tenant (recommended). In case of low load, one instance can host multiple DBs for multiple tenants (supported)
PEC-IWD/Current/IWDPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Dedicated - one per deployment of IWD
PEC-IWD/Current/IWDPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-IWD/Current/IWDPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86
PEC-OU/Current/CXCPEGuide/Planning	0d238336-2626-4954-8be3-2f1e16fdd0ce	CX Contact supports Elasticsearch 6.3 and later releases.
PEC-OU/Current/CXCPEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283	Relational database.
PEC-OU/Current/CXCPEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	CX Contact supports Redis 4.0 (5.0 and later releases recommended), clustered with persistence in Production.
PEC-OU/Current/CXCPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1		No
PEC-OU/Current/CXCPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86
PEC-REP/Current/GCXIPEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-REP/Current/GCXIPEGuide/Planning	b3fefe0d-5c3b-432d-b937-c05abfd6001d	Version 12 is required.
PEC-REP/Current/GCXIPEGuide/Planning	cc3b4e10-5020-44dd-ac17-70da284645a8
PEC-REP/Current/GCXIPEGuide/Planning	f006784a-0bf7-42b7-9838-033f4acb61fe		No
PEC-REP/Current/GCXIPEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86		No
PEC-REP/Current/GIMPEGuide/PlanningGCA	2f69518e-33af-4c0f-adcc-a98e5427e5e0	GCA publishes configuration data to the `gca-cfg` topic, which GSP consumes. The topic must exist in your Kafka configuration.
PEC-REP/Current/GIMPEGuide/PlanningGCA	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-REP/Current/GIMPEGuide/PlanningGCA	9196f7d6-6782-467f-a664-627a2c293000		No
PEC-REP/Current/GIMPEGuide/PlanningGCA	9ae24d71-5263-4a2e-8d1b-f65660f1cdc0	Both GCA and GSP require object storage to store data during processing. You can use the same storage account for both services.
PEC-REP/Current/GIMPEGuide/PlanningGIM	1a407778-58fe-4acd-8ca7-5af8eac31283	You must create the Info Mart database (see Before you begin GIM deployment).
PEC-REP/Current/GIMPEGuide/PlanningGIM	2f69518e-33af-4c0f-adcc-a98e5427e5e0	The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see GSP Kafka topics.
PEC-REP/Current/GIMPEGuide/PlanningGIM	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-REP/Current/GIMPEGuide/PlanningGIM	9196f7d6-6782-467f-a664-627a2c293000		No
PEC-REP/Current/GIMPEGuide/PlanningGIM	9ae24d71-5263-4a2e-8d1b-f65660f1cdc0	(Optional) For the Data Export feature, GIM uses object storage to store the exported data. Alternatively, you can elect to store the exported data in a directory on a local machine.
PEC-REP/Current/GIMPEGuide/PlanningGSP	2f69518e-33af-4c0f-adcc-a98e5427e5e0	The Kafka topics that GSP will consume and produce must exist in the Kafka configuration. See more details below.
PEC-REP/Current/GIMPEGuide/PlanningGSP	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-REP/Current/GIMPEGuide/PlanningGSP	9196f7d6-6782-467f-a664-627a2c293000		No
PEC-REP/Current/GIMPEGuide/PlanningGSP	9ae24d71-5263-4a2e-8d1b-f65660f1cdc0	Both GSP and GCA require persistent storage to store data during processing. You can use the same storage account for both services.
PEC-REP/Current/PulsePEGuide/Planning	1a407778-58fe-4acd-8ca7-5af8eac31283
PEC-REP/Current/PulsePEGuide/Planning	3aee73ed-68e0-4c70-8693-2421c68b86cd	Note: Pulse does not currently support Redis Cluster; use Redis in stand-alone mode.
PEC-REP/Current/PulsePEGuide/Planning	3e732261-b78e-4921-b6a6-08ee0a322ca1
PEC-REP/Current/PulsePEGuide/Planning	f1d380bf-42b1-4b67-9d27-d574bad90c86		No

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)

Modify query

Table(s):
Field(s):
Where:
Join on:
Group by:
Having:
Order by:




Limit:
Offset:
Format: