EX Engage Connector Configuration Sync Service

This article provides details about all 100.0.x releases of EX Engage Connector Configuration Sync Service.

• July 28, 2023 (100.0.100.04)
• July 14, 2023 (100.0.100.03)
• Known Issues

July 28, 2023 (100.0.100.04)

Resolved Issues

• The Health API now returns a 200 OK response only when the dependent services are connected successfully; otherwise it returns a 503 response. Previously, the Health API would indicate a success even if dependent services like Config DB, Redis, and Genesys Cloud cannot be connected. (CCECS-499)

July 14, 2023 (100.0.100.03)

What's New

• This is the initial release of EX Engage Connector Configuration Sync Service (EXCS).

Known Issues

• If a User Name of an Engage Person is not in a valid email format, then this person is originally synchronized to GC using a valid email from either Employee ID or E-Mail fields but later EXCS sets a corresponding GC User into the Inactive state. (CCECS-509)
• EXCS doesn't re-create a mapped configuration object in the EX Org if this object is manually deleted. (CCECS-503)
• EXCS doesn't remove an ACD queue in the EX Org if a corresponding DN is deleted in the Engage configuration. Instead, EXCS only unlinks the existing mapped members from such ACD queue in the EX Org. (CCECS-463)