The following items are the defects that were fixed in Scribe online connector.
Release 1.7.1.2
Defect | Description |
---|---|
D-23429 |
We have fixed an error message display defect where the system would display an Acoustic Exchange Authentication error instead of an Acoustic Campaign Pod authentication error. |
D-23809 |
We have changed the RECIPIENT_ID datatype from Integer32 to String to accommodate larger values in the recipient ID field. |
D-23562 |
Added support for Contact Lists in folders. |
Release 1.6.0.7
Defect | Description |
---|---|
D-21910 |
The scribe connection failure displays the following error message Failed to open one or more connections: Verify that the Acoustic Campaign Pod is correct and that you can connect to the same Pod from the system running the Scribe Online Agent. The following error occurred: The request was aborted: Could not create SSL/TLS secure channel.
With this fix, the connection retries the call three times, and only in case of three consecutive connection failures, the error message is displayed. |
Release 1.6.0.6
Defect | Description |
---|---|
D-21770 |
The Microsoft 365 Connector displays the following exception message The authentication endpoint Username was not found on the configured Secure Token Service. The exception message was due to a conflict with the security protocols between the Scribe online connector and the Microsoft 365 Connector. The Scribe online connector is updated to eliminate the conflict. |
Release 1.6.0.5
Defect | Description |
---|---|
D-21603 |
The scribe connection failure displays the following error message The Request was aborted: Could not create SSL/TLS secure channel.
With this fix, the connection retries the call three times, and only in case of three consecutive connection failures, the error message is displayed. |
D-21651 |
The scribe connector displays the following error message This field is required Parameter name: REPORT_ID when the users try to sync email statistics. This is because the connector does not have access to the exact date and time of the report. To resolve the issue, the connector estimates a date range wide enough to retrieve the proper report information. |
Release 1.6.0.3
Defect | Description |
---|---|
D-21560 |
If there existed an error in the SMS phone number field, the application flagged the record as a fatal error and stopped the synchronization. With the defect fix, the severity of the error is reduced and the error only fails the record and not the entire process. |
Release 1.6
Defect | Description |
---|---|
D-20515 |
An error is displayed when the |
D-20863 |
The Scribe connector is updated to handle non-English characters and successfully synchronize with the Acoustic Campaign database without any error. |