Products | Versions |
---|---|
TIBCO Cloud Integration - Connect ( Scribe ) | - |
Listed below is a summary of updates included in the hotfix. Refer to the associated readme document for any additional information.
================================================================================
Closed Issues in 1.11.1.19647 (This Release)
SCMSCRM-718
Corrected the issue with including new virtual objects in the recommended entity
list which caused failures in RS based solutions. Once support has confirmed
your organization has this hotfix in place, you will need to toggle the RS based
solution from "Recommended entities" to "All Entities" then back to
"Recommended entities" in order to reset the internal list of objects generated
to correct the issue.
================================================================================
Closed Issues in 1.11.1.19644
SCMSCDS-209
Corrected the issue with paging cookie errors when querying the searchtelemetry
object.
Corrected the issue with account creation when including a reference to a custom
parent lookup object.
If TIBCO Scribe Online Connector for Microsoft Dynamics 365 / CRM is also
installed, please also install TIBCO Scribe Online Connector 1.11.1 for
Microsoft Dynamics 365 / CRM Hotfix 7.
================================================================================
Closed Issues in 1.11.1.19642 (This Release)
SCMSCDS-205
Corrected the issue with paging cookie errors when querying the Audit Object.
If TIBCO Scribe Online Connector for Microsoft Dynamics 365 / CRM is also
installed, please also install TIBCO Scribe Online Connector 1.11.1 for
Microsoft Dynamics 365 / CRM Hotfix 5.
================================================================================
Closed Issues in 1.11.1.19640
SCMSCDS-204
Corrected the issue with the connector not using multiple threads during runtime
when in batch mode.
================================================================================
Closed Issues in 1.11.1.19639
SCMSCDS-201
Addressed the issue where the connector was not parsing the targeted
organization URL properly to get the organization name, which was preventing
a connection to the service.
================================================================================