Ana Bahr

What's New TIBCO Cloud? Integration Configure secrets that store an SSL Keystore, truststore, or certificate file for TIBCO BusinessWorks appsConfigure alerts and notifications for TIBCO BusinessWorks and TIBCO Flogo appsAdded support for the Microsoft Dataverse connector TIBCO Cloud Integration API The following methods have been added to configure secrets that store an SSL Keystore, truststore or certificate file for you to secure communications between SSL enabled systems and your TIBCO BusinessWorks apps. (IPAS-20681) GET /v1/subscriptions/{subscriptionLocator}/secretsGET /v1/subscriptions/{subscriptionLocator}/apps/appId/secretsPOST /v1/subscriptions/{subscriptionLocator}/secretsPUT /v1/subscriptions/{subscriptionLocator}/secrets The following methods have been added for configuring Alerts and Notifications rules for TIBCO BusinessWorks and TIBCO Flogo® Apps. Alerts and notifications configured for TIBCO Flogo and TIBCO BusinessWorks apps let you know when an app has met or exceeded selected criteria, such as CPU or memory thresholds. (IPAS-21748) GET /v1/subscriptions/{subscriptionLocator}GET /v1/subscriptions/{subscriptionLocator}/alertsPOST ?/v1?/subscriptions?/{subscriptionLocator}?/rules/{rulesId}DELETE ?/v1?/subscriptions?/{subscriptionLocator}?/rules/{rulesId} Develop / TIBCO Flogo Added support for creating TIBCO Flogo apps directly from the TIBCO Cloud Integration - API Modeler user interface. (IPAS-21642)You can now copy an unpushed Flogo app. (FLOGO-9847)Users can now consume TCAM Mock endpoints in the Flogo Apps via TIBCO Cloud Mesh. (FLOGO-10147)Added support for re-running a flow instance on TIBCO Cloud Integration Execution History. (FLOGO-9851)You can now link activities on the main branch or any other branch from the conditional branch. (FLOGO-1554)The Flogo app created using the TIBCO Cloud? Integration - API Modeler platform is now updated when the specifications are modified. The updates in the app are reflected after clicking the Refresh icon. (FLOGO- 660)The flow designer is revamped to provide enhanced flexibility and new advanced features, such as branch merging. (FLOGO-8394) Develop/TIBCO Flogo® Connectors TIBCO Flogo® Connector for Amazon Elastic File System Added support for the Assume Role. (WIAMEF-26)Added support for using an AWS session key. (WIAMEF-50) TIBCO Flogo® Connector for Amazon Glacier Added support for using an AWS session key. (WIAMGL-47) TIBCO Flogo® Connector for Apache Pulsar Added support for running TIBCO Flogo apps as an Apache Pulsar function. (FGPUL-240) TIBCO Flogo® Connector for Google Cloud Storage There are no new features in this release. TIBCO Flogo® Connector for Microsoft Dataverse Added support for the Microsoft Dataverse connector in TIBCO Cloud Integration. TIBCO Flogo® Connector for MQTT Added support for AWS IoT that is compliant with MQTT 3.1.1 standards. (WIMQTT-116)Added Client Id field in the MQTT Connection Details section. (WIMQTT-116) TIBCO Flogo® Connector for PostgreSQL Enabled SQL syntax highlighting in the editor when using a PostgreSQL connection. (WIPGRS-577) TIBCO Flogo® Connector for TIBCO® Data Virtualization The Connector now supports the following: Stored procedures (FGTDV-70)One-way SSL (FGTDV-89)Call Procedure activity (FGTDV-98)Added SessionTimeout and RequestTimeout connection parameters. (FGTDV-90)Updated the ODBC driver to version 8.5.5. (FGTDV-100)Query input parameters are no longer mandatory. (FGTDV-66) Integrate/TIBCO BusinessWorks? Support of Smart Engine for HTTP-based transport You can now generate various HTML reports for the engine data collected for different performance use cases with applications using HTTP-based transport. The Smart Engine also analyzes the engine data collected and provides recommendations to improve the performance of your application. For more information, see the "Smart Engine" section in TIBCO ActiveMatrix BusinessWorks? Administration. (AMBW-47836) Integrate/TIBCO BusinessWorks? Plug-ins TIBCO ActiveMatrix BusinessWorks? Plug-in for AMQP Session Support Provided Session support for the Microsoft Azure Service Bus broker for the AMQPSendMessage and AMQPReceiveMessage activities. (AMQP-887) Client ID Support Provided support for setting a fixed client ID in the AMQP connection for the following brokers: (AMQP-999) Qpid-1-0AMQ-1-0ActiveMQ-1-0 TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Kafka OpenTelemetry Predefined Tags The plug-in now supports OpenTelemetry predefined tags. You can use these predefined tags to get more information about the current job by running any activity in the palette. TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Pulsar Added support for the Apache Pulsar plug-in in TIBCO Cloud Integration. TIBCO ActiveMatrix BusinessWorks? Plug-in for Database Support for Native Drivers The plug-in supports native drivers for all the supported databases. Support for Geometric and UUID Data Types for PostgreSQL Database The plug-in supports geometric data types (geometry, line, lseg, box, path, polygon, circle) and UUID data type for PostgreSQL database. TIBCO ActiveMatrix BusinessWorks? Plug-in for Google BigQuery There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM Get Context Information The Get Context Information feature is added on the General tab of the Entity Event Source activity to fetch and display the context information on the Output tab. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData Added support for OAuth 2.0 on OData Connection Shared Resource. An Oauth Configuration checkbox is added on the Security tab of the OData Connection shared resource to use OAuth authentication. (BWOD-677)Added support for the Query Operation in OData Batch Activity. In this release, the OData plug-in supports batch requests with QUERY operation as a client to external OData V4 services through the OData Batch activity in OData Palette. (BWOD-710) TIBCO ActiveMatrix BusinessWorks? Plug-in for PeopleSoft Support for New Activities IBRequest: The plug-in receives messages from the TIBCO environment and sends the message data to a PeopleSoft database using the Integration Broker.CIEventReceiver: This activity uses PeopleCode embedded in a TIBCO page to persist data entered by PeopleSoft users into a queue table. At runtime, the CIEventReceiver activity polls that queue table. If an unprocessed event is found, it sends the message out to the TIBCO environment and stamps the queue entry as processed. Addition of Support for Migration of New Activities TIBCO ActiveMatrix BusinessWorks? Plug-in for PeopleSoft now supports the migration from the Adapter Subscriber activity and CI Publication Service to the CIEventReceiver activity and from Publish to Adapter Activity and Message Subscription Service to the IBRequest activity. Hot Update This feature is to update the module properties for the PeopleSoft Connection Shared resource for the Invoke activity only without restarting the application. It is supported with BWCE. For more information, see the Hot Update of Shared Resource topic in the TIBCO ActiveMatrix BusinessWorks? Plug-in for PeopleSoft User Guide. Open Telemetry Open Telemetry is added as of version 7.3.0 of the plug-in. It is supported with TIBCO ActiveMatrix BusinessWorks? and TIBCO BusinessWorks? Container Edition. For more information, see the "Open Telemetry Tracing for TIBCO ActiveMatrix® Adapter for PeopleSoft Palette" topic in the TIBCO ActiveMatrix BusinessWorks? Plug-in for PeopleSoft User Guide. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData Services for SAP S/4HANA There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for SmartMapper Visual Diff The plug-in now supports comparison of two revisions of a process, two revisions of a shared resource and their artifacts side by side visually in TIBCO Business Studio? for BusinessWorks?. It highlights changes in newer revisions such as addition or removal of activities, changes in an activity, and shared resource configuration. The activities and shared resource are as follows: Add to Relationship InstanceBulkExtractBulkLoadCreate Relationship InstanceCreate Entity InstanceDelete Relationship InstanceDelete Entity InstanceDynamic DeleteDynamic LookupGenerate KeyLookupUpdate Entity InstanceSmartMapper WizardSmartMapper ER Model Shared Resource Support for module property that enables output validation The following module property is implemented to enable the output validation: com.tibco.bw.palette.smartmapper.enableOutputValidation. The plug-in doesn't take any action, if the module property is undefined or set to false. Support for OpenTelemetry (Open Tracing) TIBCO ActiveMatrix BusinessWorks? Plug-in for SmartMapper now supports Open Telemetry (Open Tracing) predefined tags. You can use these predefined tags to get more information about the current job being run by any activity in the palette. TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO Cloud AuditSafe Supports SSO Authentication ActiveMatrix BusinessWorks? Plug-in for TIBCO Auditsafe supports the SSO (Single Sign-on) login method for design time. Changes in Functionality Integrate/TIBCO BusinessWorks? AMBW-47731 The default TIBCO BusinessWorks engine log level is changed from ROOT=WARN to ROOT=ERROR. This results in fewer entries being generated in the engine logs when a BusinessWorks app is started. If you want additional details, you can update the BW_LOGGER_OVERRIDES engine variable value to ROOT=WARN. Develop/TIBCO Flogo® FLOGO-10164 The default TIBCO Flogo log level is changed from ROOT=WARN to ROOT=ERROR. This results in fewer entries being generated in the engine logs when a Flogo app is started. If you want additional details, you can update the FLOGO_LOG_LEVEL variable value to ROOT=WARN. FLOGO-10511 The validation error count for non-connected activity is changed. Hence, you see mismatch in error counts in the flow list and flow design pages. FLOGO-9982 The branching order of execution is changed. The new order is: Success with condition/Success with no matching condition/Error(if any)Success If there are multiple success branches then execution is in the reverse order of addition. FLOGO-10490 The way the app properties are configured has now been changed. The save option is not enabled until the configuration of all app properties is completed. FLOGO-9864 The Start activity is now present on the canvas after which you can add and connect the other activities. Integrate/TIBCO BusinessWorks? Plug-ins When a new version of a TIBCO BusinessWorks Plug-in is released and that plug-in supports Supplements, you must upload the Supplements for the plug-in again in TIBCO Cloud Integration. If you deploy a new app or redeploy an existing app and the associated Supplements have not been reuploaded, the app deploy fails. For this release the updated plug-ins that require you to reupload supplements include: TIBCO ActiveMatrix BusinessWorks? Plug-in for OData BWOD-780 We have made a change in the formation of the OData URI. Now the filter expressions in the OData URI of OData Query/Batch activity will be enclosed in braces for Collection properties with the $filter query option : /People?$filter=Friends/any(x: ( x/UserName eq @uname)) Migration and Compatibility TIBCO Cloud? Integration TIBCO Cloud Integration only supports the most recent version of the Hybrid Agent and one version back. The most recent version of the Hybrid Agent is version 1.7.0, and the prior Hybrid Agent was version 1.6.0. If you have a Hybrid Agent installed that is older than version 1.6.0, you should install Hybrid Agent version 1.7.0 to ensure the best performance. Deprecating and End of Support IPAS-20590 In a future release, the option to select a Custom Access Key when enabling Flogo DB Services will be deprecated both in the user interface and the TIBCO Cloud Integration Platform API. When the DB Services option is enabled, a system key will be created instead. If you already have Flogo DB Services enabled with a Custom Access Key, that configuration will continue to work, however the drop-down used to select the Custom Access Key will no longer be visible. If you disable Flogo DB Services and later enable them again, the new configuration will use a system access key. Closed Issues Develop/TIBCO Flogo® FLOGO-10241 Mapper activity fails at runtime if the schema used has an Anonymous array. FLOGO-9510 If you rename an activity field, assertion configuration on such activities does not adjust automatically and also does not throw any validation error in the assertion file. When executing a unit test in such cases, the assertion fails. FLOGO-9369 No validations are displayed if the user enters an invalid assertion expression or performs incorrect mappings in flow inputs. FGDPBX-28 The dropbox token expires in about 4 hours. TIBCO Flogo® Connector for Apache Pulsar FGPUL-268 ProducerBusy error is displayed for Apache Pulsar Publish activity. FGPUL-244 When the Apache Pulsar Producer Activity is present in a running app, topics are created when the activity executes and a message is published, not when the app starts. TIBCO Flogo® Connector for TIBCO® Data Virtualization FGTDV-68 TIBCO Flogo Connector for TIBCO Data Virtualization Connector failed due to TIBCO Data Virtualization session timeout. FGTDV-66 Prepared Query input parameters are mandatory for TIBCO Data Virtualization Query activity. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData BWOD-770 The system Query Options configured on the OData Service binding for Query operation are not reflected at runtime on invoking the service. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData Services for SAP S/4HANA BWSH-731 When the SAP S/4HANA connection shared resource is configured for On-Premises / Private Cloud and the authentication type is set to Basic Authentication, the request URL does not connect to the appropriate SAP client if multiple SAP clients are configured in the SAP S/4HANA system. This issue is fixed. Note: To connect to the correct SAP S/4HANA client, the com.tibco.bw.palette.s4hana.sapclient Java property must be specified in the TIBCO BusinessWorks runtime application. The value of this Java property is a string, i.e. "200". To confirm that the Java property is being used, the DEBUG loglevel can be turned on for the package com.tibco.bw.palette.s4hana.runtime. Below is an example of a DEBUG trace message. In this example, sap-client is set to 400. 16:13:13.016 DEBUG [bws4hanacloud-threadpool-thread-1] com.tibco.bw.palette.s4hana. runtime.odata.ODataHandlerV2 - TIBCO-BW-PALETTE-S4HANACLOUD-200004: Generate HTTP Request URL: [https://vhcals4hci.dummy.nodomain:44300/sap/opu/odata/sap/API_PRODUCT_SRV/ $metadata?sap-client=400], Activity Name=[ConsumeODataService], Process=[tests4h.Read_XXX], Module=[TestS4H], DeploymentUnit=[TestS4H.application:1.0]. TIBCO ActiveMatrix BusinessWorks? Plug-in for SmartMapper SM-3104 New projects that use JDBC storage fail when created with TIBCO Business Studio? for BusinessWorks? version 6.9.0.

What's New TIBCO Cloud? Integration For Integrate/TIBCO BusinessWorks apps, now you can dynamically update app and module properties if configured via Configuration or Credential Management Service provider using the new Refresh App Properties button on the App Details > Environment Controls > Engine Variables tab. (IPAS-14581) TIBCO Cloud Integration API Uploading SSL certificates when enabling Execution History for TIBCO Flogo apps is supported by uploading the certificate as a base64 encoded string in the POST /v1/subscriptions/{subscriptionLocator}/exechist request. (IPAS-20849)The following methods have been updated to support the Pin, Unpin app feature for TIBCO BusinessWorks apps. Using a pin you can go back to a previous version of an app if necessary. (IPAS-21228) POST /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pinDELETE /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pinPUT /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pinGET /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Develop / TIBCO Flogo In Flogo applications, if TLS is enabled for Opentelemetry protocol receiver, you can Encrypt base64 encoded certificate values by using either TIBCO Cloud Integration platform API or by using an app executable and set it the environment variable with the prefix ?SECRET:?.AWS connection now supports Default AWS Credentials Provider Chain with authentication type as 'Default credentials'.Using the Run all test suites button, you can run all the enabled test suites in the unit testing feature. Also, you can use the Run all test cases to run all the enabled test cases. (FLOGO-9683, FLOGO-9681)In unit testing, you can mock the data for an activity as part of a test case. (FLOGO-7641)The LogMessage activity?s LogLevel attribute can be assigned from a flow variable. (FLOGO-9810) Develop/TIBCO Flogo® Connectors AWS connection now supports Default AWS Credentials Provider Chain with authentication type as 'Default credentials'. This enhancement affects the following TIBCO Flogo Connectors: (FLOGO-9803) Amazon DynamoDBAmazon EC2Amazon KinesisAmazon SNSAmazon SQSAmazon S3 TIBCO Flogo® Connector for DocuSign Added support for JWT Grant as an authentication type. (FGDUSN-42)Added support for multiple files in an envelope. (FGDUSN-43) Added support for all document types supported by DocuSign.New activity DocuSignListDocument added to fetch details for single or multiple documents from an envelope. (FGDUSN-41) TIBCO Flogo® Connector for Oracle Database TIBCO Flogo® Connector for Oracle Database has a new activity that allows calling stored procedures from Oracle database. (WIORA-299) TIBCO Flogo® Connector for Apache Pulsar The No Acknowledgement (NOACK) activity has been added to send a negative ack to the Pulsar broker. (FGPUL-199) Integrate/TIBCO BusinessWorks? Users can now upgrade TIBCO Business Studio? BusinessWorks? from an existing installation using the new Upgrade Manager. To access the Upgrade Manager navigate to Help > BW Upgrade Manager. (AMBW-45217) Integrate/TIBCO BusinessWorks? Plugins TIBCO ActiveMatrix BusinessWorks? Plug-in for Azure Cloud Services (Azure Data Lake Storage Gen2) The Azure Cloud Services (Azure Data Lake Storage Gen2) plug-in is supported for TIBCO Cloud Integration. The following features have been added in this release. (BWAZCS-7) Create Activity The plug-in provides a Create activity to perform Create File System, Create Directory, Upload Files, and Acquire Lease operations. Update Activity The plug-in provides an Update activity to perform the Update ACL and Update File operations. Read Activity The plug-in provides a Read activity to perform List File Systems, List Directories, Get Properties, and Download File operations. Delete Activity The plug-in provides a Delete activity to perform Delete File Systems, Delete Directory, and Break Lease operations. TIBCO ActiveMatrix BusinessWorks? Plug-in for BusinessConnect Added support for the BusinessConnect plug-in in TIBCO Cloud Integration. TIBCO ActiveMatrix BusinessWorks? Plug-in for Google BigQuery Support for Bulk loading of data Loads data to BigQuery table from Google Cloud Storage with different file types such as AVRO, CSV, JSON, ORC, and PARQUET sheets that are stored in the drive. (BWGBQ-344) Support for authentication with OAuth 2.0 You can now connect to Google BigQuery with the OAuth 2.0 authentication method. (BWGBQ-348) Support for merge operation in Data Updater Activity Merges updated or new records from the source table to the Target Table in Google BigQuery using the merge SQL operation. (BWGBQ-272) Support for delete operation in Data Updater Activity Deletes the records from the source table in Google BigQuery. (BWGBQ-331) TIBCO ActiveMatrix BusinessWorks? Plug-in for Google Cloud Pub/Sub There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint The Microsoft SharePoint plug-in now supports Basic Proxy Authentication with the help of Proxy Configuration and Identity Provider. (SPBW-1752) TIBCO ActiveMatrix BusinessWorks? Plug-in for OData In this release, the OData plug-in supports batch requests with UPDATE and DELETE operations as a client to external OData V4 services via the OData Batch activity in OData Palette. (BWOD-661) TIBCO ActiveMatrix BusinessWorks? Plug-in for Oracle Fusion Cloud Applications Suite New Plugin TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Applications Suite allows TIBCO ActiveMatrix BusinessWorks? customers to consume REST services and perform Create, Read, Update, Delete operations for the ERP and HCM modules in Oracle Fusion Cloud, including support for batch processing. ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Apps Connection Shared Resource With this feature, you can connect to the Oracle Fusion Cloud Applications Suite using either Basic Authentication or OAuth2.0 Authentication. (BWOCE-25) ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Apps Palette The palette supports the Consume Oracle Fusion Cloud Apps Service Activity. This activity consumes the Oracle Fusion Cloud Service that is selected and downloaded. The activity supports DELETE, GET, PATCH and POST operations through the downloaded service. (BWOCE-26) TIBCO ActiveMatrix BusinessWorks? Plug-in for SMPP Support has been added to provide the ServiceType value from the Input tab of the SendShortMessage activity. (BWSMPP-146) Changes in Functionality Develop/TIBCO Flogo® FLOGO-9048 Errors for the ReceiveHTTPMessage trigger are now shown at the Info log level. FLOGO-10022 If the path parameter has a number or boolean data type in the API spec and it is mapped with a string type value then it shows design time validation error after upgrade. You need to manually update the mappings to match the data type of the path parameter. Migration and Compatibility TIBCO Cloud? Integration After transitioning from a Trial Organization to a Production Organization, you must log out and log back into TIBCO Cloud? Integration. (IPAS-21524) TIBCO Cloud Integration only supports the most recent version of the Hybrid Agent and one version back. The most recent version of the Hybrid Agent is version 1.7.0, and the prior Hybrid Agent was version 1.6.0. If you have a Hybrid Agent installed that is older than version 1.6.0, you should install Hybrid Agent version 1.7.0. Deprecating and End of Support TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint The SharePoint SOAP palette has been removed from the TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint in the SharePoint 6.4.0 release. (SPBW-1938) Closed Issues TIBCO Cloud? Integration IPAS-19746 The name of the TIBCO Cloud Mesh service is not getting updated in the Service registry when the app is pushed from the TIBCO Command Line Interface with a modified name. TIBCO Cloud? Integration - Connect IPAS-19835 After installing a new TIBCO Scribe Online Connector from the Marketplace the new connector does not display in the "Create a connection" dialog. Develop/TIBCO Flogo® FLOGO-8147 After editing an activity name, the branching label from source to destination activity does not show the updated activity name. It shows the default activity name instead. FLOGO-8774 When an app is pushed from the TIBCO Cloud Command Line Interface (CLI) with a modified name, the name of the TIBCO Cloud Mesh service is not updated in the service registry. FLOGO-8897 Path parameter of type number is converted to type string when the ReceiveHTTPMessage trigger is configured with an OpenAPI spec. FLOGO-9430 String, number, and boolean types are supported in the ReceiveHTTPMessage trigger when configured with an OpenAPI spec. FLOGO-9807 For unit testing, reconfiguring an activity in a flow that depends on a specific method, such as GET, can cause unit tests to fail if the unit test depends on the output of the selected method. For example, if you use the shared data activity configured with the GET method, then under the Unit Testing tab you add assertions and run the test, the test runs successfully. If you later change the configured method to SET, the test fails because it depends on the output generated by the GET method. FLOGO-9818 After importing an app with a primitive object array, the mapping for the array is lost and it is converted into array.ForEach. FLOGO-10054 A Base64 encoded SSL certificate can be encrypted using either the TIBCO Cloud Integration API or an app binary and then passed as Engine variable: FLOGO_OTEL_TLS_SERVER_CERT=SECRET:<encrypted_base64_encoded_cert_value> To encrypt a base64 encoded value using an app executable see: https://integration.cloud.tibco.com/docs/index.html#Subsystems/flogo/flogo-all/encrypting-password-.html To encrypt a base64 encoded value using the TIBCO Cloud Integration API see: https://integration.cloud.tibco.com/docs/Subsystems/tci-api/utils/encrypt-values-fe.html FLOGO-10269 In TIBCO Flogo flows, if OSS extensions, such as counter or error, are added from the Recently Used section, some activity tiles show as blank and the user interface becomes unresponsive. FLOGO-10427 TIBCO Flogo apps that connect to Prometheus continue to use deprecated metrics, which consumes all available memory causing the app to stop running. Note: After the upgrade, you must regenerate app executables for any apps that connect to Prometheus to resolve the issue. TIBCO Flogo® Connector for Amazon Kinesis FGAZKS-64 Added support to access Amazon Kinesis services privately through a Custom VPC endpoint. TIBCO Flogo® Connector for Amazon S3 FGAZS3-149 Added support to access Amazon S3 services privately through a Custom VPC endpoint. TIBCO Flogo® Connector for Amazon SNS FGSNS-39 Added support to access Amazon SNS services privately through a Custom VPC endpoint. TIBCO Flogo® Connector for Amazon SQS FGSQS-70 Added support to access Amazon SQS services privately through a Custom VPC endpoint. TIBCO Flogo® Connector for Microsoft Azure Service Bus WIAZSB-278 When the connection and link are active but no calls (idle state) are made using the link for 10 minutes, the link is closed and cannot publish a message. TIBCO Flogo® Connector for Salesforce FGASFC-350 When a user imports an app (app that is created on Salesforce version older than 1.3.2) in Salesforce version 1.3.3 and uses imported connection in the app, then the Update and Delete activities generate the following error: "The requested resource does not exist". TIBCO ActiveMatrix BusinessWorks? Plug-in for Google Cloud Pub/Sub BWGCPS-152 SubscriptionActivity can now receive messages after the network has recovered from a failure.

For additional information see: TIBCO Cloud Integration - Connect Release Notes TIBCO Cloud Integration - Connect Known Issues TIBCO Scribe Online Connector Release Notes New And Noteworthy SCCORE-3742 The palette of colors used for the blocks in TIBCO Cloud Integration - Connect flows has been upgraded to a brighter and more distinctive set of colors to help users differentiate one connection from another during the flow design process. SCCORE-8662 Added a new Wait Block to the Control Blocks section of the Flow designer. This block allows you to pause the flow for up to 600,000 milliseconds (10 minutes). Note that if you stop a running app with a flow that contains a Wait Block, the app does not stop until the Wait Duration has completely elapsed. To use the Wait Block, you must run the latest version of the Agent. TIBCO Cloud Integration Connect - API SCCORE-8430 Upgraded the Swagger user interface to the latest version. As a result of this upgrade, the Try it out button on the interface is enabled by default and does not display. You can execute commands without having to select Try it out first. SCCORE-8662 Added API support for the new Wait Block. This block allows you to pause a flow for up to 600,000 milliseconds (10 minutes). To use the Wait Block, you must run the latest version of the Agent. Migration And Compatibility Agent If you plan to use the new Wait Block in a flow, your On-Premise Agent must be upgraded to the latest version. If the Agent is not upgraded, you cannot save changes to any flows. (SCCORE-8464) Closed Issues SCCORE-7947 Attempting to install an Agent on an unsupported operating system now fails with an error message instead of allowing the installation to continue. (Case # 02088715) SCCORE-8122 On the Query Block Net Change tab, the Most Recent Record Processed date time value displays as null null if the value contains microseconds. If you attempt to edit the value, "NaN/NaN/NaN NaN:0NaN:0NaN.NaN AM" displays. (Case # 02091445) SCCORE-8403 In some cases, Agents were not able to synchronize Solution execution data to the Cloud causing Execution History Detail records to be missing. Failed records could not be retrieved for reprocessing. (Case # 02089362, 02112572, 02114366, 02118156, 02118195, 02118592, 02119664, 02121244, 02124813, 02133531) SCCORE-8418 Internal Agent database tables that exceeded one million records caused performance issues and generated errors in the logs. (Case # 02118235, 02122387, 02129217) SCCORE-8982 Agents could not retrieve metadata for Microsoft Dynamics GP Connections nor could they load cached metadata. Errors similar to the following were generated: (Case # 02157831, 02157842, 02158348, 02158358, 02158359, 02158363, 02158366, 02158672) Error loading cached metadata unexpected end of file.

What?s New TIBCO Cloud? Integration The updated TIBCO Cloud Integration Hybrid Agent allows you to manage remote apps from the TIBCO Cloud Integration user interface. Remote apps are auto-discovered by the agent and can be monitored, scaled up or down, stopped or started, and environment variables can be updated. Note that to use this new functionality, the latest version of the agent must be downloaded and run in a Kubernetes Cluster. Existing Hybrid Agents used for Hybrid Connectivity to establish tunnel connections to on-premises resources can continue to run and do not need to be upgraded at this time. (IPAS-20577)You can now download TIBCO BusinessWorks app templates from the TIBCO Cloud Integration Marketplace and import those templates into TIBCO Business Studio for BusinessWorks . (IPAS-20471)A new --logStreamPort option has been added to the start command for the Hybrid Agent. In cases where there are two agents on the same machine, you can specify the port to be used for streaming logs using this command: tibagent start agent --logStream --logStreamPort <port number> <agentName> (IPAS-18585) TIBCO Cloud Integration API We have added the following API methods in this release: GET ?/v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/testsuite/export Use this method to export TIBCO Flogo Test Suites. Test Suites are a collection of unit tests for the flows in a Flogo app. (IPAS-20552) PUT ?/v1?/subscriptions/{subscriptionLocator}/apps/{appId}/endpoints/{endpointId} Use this method to update the service name and description of an app endpoint. (IPAS-19959) POST /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to pin a Flogo app. Using a pin you can go back to a previous version of an app if necessary. (IPAS-20655) DELETE /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to delete a pin from a Flogo app. PUT /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to restore a pinned Flogo app. GET /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to get the pin associated with an app ID. Develop / TIBCO Flogo Unit Testing You can now create, design and run unit tests for your Flogo flows using the integrated Unit Testing feature at any phase of the development cycle to verify whether activities in the flow are working as expected. Create Array in Mapper In the mapper, you can create a new primitive or object array of size N. Improved Group Management in App Properties The user experience of App Properties is enhanced to allow you to drag the groups from one location to another. Environment Variable for Session Token in AWS AppConfig feature If you are using temporary credentials to connect to AWS AppConfig services, a new optional environment variable is available for configuring a session token. Optional Session Token field An optional Session Token field on the AWS Connection dialog has been added to support passing an AWS Session token with the AWS access key ID and secret. (FLOGO-9459) Develop/TIBCO Flogo® Connectors TIBCO Flogo Connector for Amazon DynamoDB There are no new features in this release. TIBCO Flogo Connector for Amazon EC2 There are no new features in this release. TIBCO Flogo Connector for Amazon Kinesis There are no new features in this release. TIBCO Flogo Connector for Amazon S3 There are no new features in this release. TIBCO Flogo Connector for Amazon SNS There are no new features in this release. TIBCO Flogo Connector for Amazon SQS There are no new features in this release. TIBCO Flogo® Connector for Apache Pulsar A new client authentication method, "OAuth2", has been added in the Apache Pulsar connection. (FGPUL-139)Flogo® Connector for Apache Pulsar now supports Open Telemetry. For more information, see the Tracing Apps by Using OpenTelemetry Collector topic: Tracing with OpenTelemetry Collector. (FGPUL-140)The name of the created producer/consumer now has an operationally useful format that can be seen by using the Pulsar Admin REST API. TIBCO Flogo Connector for Azure Data Factory Added support to trigger pipeline with parameters from Flogo. TIBCO Flogo Connector for HTTP Added support for a Data mode as a processing mode where the user has more control over input parameters such as path, query, headers, and request schema. OpenTracing is also supported in Data mode. TIBCO Flogo Connector for HubSpot There are no new features in this release. TIBCO Flogo Connector for IBM MQ This connector has been certified for use with TIBCO Cloud Integration. (FGIBMQ-42)Added support for MQ Client Channel Definition Table (CCDT) files. (FGIBMQ-45) TIBCO Flogo Connector for MongoDB Seed lists specified using SRV records DNS are now supported.Added support for the authentication source to specify the database created in the MongoDB database on which the user has to be authenticated.Added support for retry on error for MongoDB activities. TIBCO Flogo Connector for SAP S/4HANA The Flogo Connector for SAP S/4HANA now supports OData V2 and OData V4 APIs.An On-premises connection is supported in this release. TIBCO Flogo Connector for Snowflake Supports configuring metadata of SQL statements manually. This feature allows the use of separate queries to acquire the metadata associated with the field. The user can manually configure the metadata by setting the Manually Configure Metadata option to True. Integrate/TIBCO BusinessWorks OAS 3.0 enhancements include support for multiple response features. Support has been added to create a top-down REST service with an OAS 3.0 JSON file having multiple response content-types.Support for oneOf/anyOf constructs. You can now generate XSD and create a top-down service or reference binding using an existing OAS 3.0 JSON file with anyOf or oneOf keywords for request and response schemas.Support for inline schema at request and response. An OAS 3.0 JSON file with inline schema in request and response is now parsed when creating a top-down REST service or reference binding.OAUTH 2.0 authentication in ReceiveMail activity. OAuth 2.0 Authentication is now supported for Receive Mail Activity IMAP protocol in the Mail palette.Support has been added for HotUpdate for JDBC Shared Resources.The TIBCO Cloud API Modeler (TCAM) APIs are now available on the TIBCO Cloud APIs website. TIBCO BusinessStudio for BusinessWorks can leverage these to make the API specs from TCAM discoverable in the API explorer. Integrate/TIBCO BusinessWorks? Plugins TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon Redshift Creating and Configuring the Redshift Connection Resource This feature establishes a connection with Amazon Redshift to perform data load and data polling operations. The ActiveMatrix BusinessWorks? Plug-in for Amazon Redshift supports the following types of authentication methods: (BWAR-8) Username/PasswordFederated Authentication and SSO Bulk Load Activity The Bulk Load activity performs data loading from a source relational database or other sources to a target Amazon Redshift. The data can also be loaded into the Amazon Redshift table by staging data files in the Amazon S3 bucket. This is done with the help of the appropriate S3 bucket URI and file format. (BWAR-3) Data Change Poller Activity The Data Change Poller activity tracks new and updated records in a given source table. The new or updated record is copied to a reference table for future use. After each polling interval, the changed records are returned as the output. (BWAR-24) TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon S3 The Amazon Connection can now retrieve the java client object in inline subprocesses. (BWAS-567)Users can now configure custom VPC endpoints for Amazon S3 activities using a system property. (BWAS-573) TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS Users can now configure a custom Virtual Private Cloud (VPC) endpoint for Amazon SQS and SNS activities using a system property. (AWSM-610) TIBCO ActiveMatrix BusinessWorks? Plug-in for AMQP The AMQPReceiveMessage activity now provides an ?Any? option in the Message Type field. You can receive text and byte type messages using the Any message type. This field is available when Qpid-1-0 is selected from the Broker Type list of the AMQP Connection shared Resource used. (AMQP-851) TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Kafka Smart Engine TIBCO ActiveMatrix BusinessWorks? collects engine data on an AppNode. This plug-in uses the data to provide analysis and recommendations for improving your application performance. (BDKF-938) TIBCO ActiveMatrix BusinessWorks? Plug-in for AWS Common Services Container Credentials with Assume Role In AWS Common Services, along with AWS Credentials, the Container Credentials also support the Assume role. (BWAWSC-193) Cross Account Credentials in the GetConnection Activity In AWS Common Services, users can configure Cross Account Credentials from the input schema of the GetConnection activity. (BWAWSC-198) TIBCO ActiveMatrix BusinessWorks? Plug-in for Facebook Graph API v13.0 Support for Graph API v13.0 has been added in this release. (BWFB-1676) TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for NetSuite There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData In this release, the OData plug-in supports batch requests as a client to external OData V4 services via the new OData Batch activity in the OData Palette. (BWOD-593) Note: The OData Batch request supports only the Create operation in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP S/4HANA Receive Business Events Activity The new Receive Business Events activity can be used to receive business events from the SAP S/4HANA system. When the business event is sent from SAP S/4HANA, only key information is provided. To get the changed data from SAP S/4HANA, the key information stored in the Business Event is used with the Consume OData Service activity. Note: The Receive Business Events activity supports only SAP S/4 HANA Public Cloud Connection. Support for OData V4 APIs The Consume OData Service activity can now be used to invoke OData V4 APIs in the SAP S/4HANA system. This includes SAP S/4HANA on-premises/private cloud and SAP S/4HANA public cloud. Note: OData V4 APIs are supported only for Production tenant. SAP S/4HANA On-Premises/Private Cloud This release supports versions 2020 and 2021 of SAP S/4HANA that are available as an On-Premises or Private Cloud installation. TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP SuccessFactors Support for Batch Processing The plug-in now supports batch processing for OData V2 APIs and supported operations. This allows multiple instances of the same operation in one request. You must configure the number of instances per request at design-time. (BWSS-353 / BWSS-225) Support for Visual Diff You can now use the plug-in to compare two revisions of a process or two revisions of a shared resource, and their artifacts side-by-side visually in TIBCO Business Studio? for BusinessWorks?. In the newer versions, the plug-in highlights changes such as the addition or removal of activities, changes in an activity, and shared resource configuration. The activity and shared resource are as follows: (BWSS-354 / BWSS-297) ConsumeSAPSuccessFactorsODataService ActivitySaP SaaS Connection shared resource TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL® The TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL® now supports OpenTelemetry predefined tags. You can use these predefined tags to get more information about the current job being run by any activity in the palette. (BFTL-181) Changes in Functionality Develop / TIBCO Flogo Create array in Mapper On importing an app with in-line array mappings, the array elements are wrapped into the item object.Elements under existing array mapping which has array foreach without source are wrapped in an item object.On adding empty array.foreach, input mapper turns to non editable. Changes in Documentation To streamline the TIBCO Cloud Integration documentation, we are merging smaller topics together and removing duplicate information, as follows: This Hybrid Agent Overview page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/overview.html The information has been merged with the Using the TIBCO Cloud Integration - Hybrid Agent page: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/index.html This Hybrid Proxy Connections page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-proxy/index.html The information has been merged with the Proxy Connection Overview information into this page: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-proxy/tunnel-overview.html The Monitoring Hybrid Apps page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-monitoring/index.html The information has been merged with the Monitoring and Managing Hybrid Apps page: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-monitoring/monitoring-overview.html Closed Issues TIBCO Cloud? Integration IPAS-13301 If you copy or replace an app from the App Details History tab, the content on the History tab is not updated automatically with new information. IPAS-20941 Whitelisted open source libraries for Node.js apps were not listed in the TIBCO Cloud Integration documentation. Automate / TIBCO Cloud Live Apps CBPM-22676 An HTTP-400 error is generated when accessing TIBCO Cloud Live Apps Administrator -> Process Administrator from the TIBCO Cloud Integration Environment & Tools page. Develop / TIBCO Flogo FLOGO-9426 / FLOGO-9486 When you add a property or group in an app having a large number of flows and nested app properties (for example, 80 flows and more than 100 nested app properties), the API call for the Save button takes time to add properties and groups. FLOGO-9427 If you move a property from the root level or from one group to another group in the app properties (using the drag-and-drop feature), at an activity level, existing mappings are not updated in the input data or mapper text field. FLOGO-9434 If you remove a property and add the same property under another group or root level, the mappings are not updated in the input data or mapper text field. The changes are visible at the activity level but the input data or mapper text field displays the following error: Property 'Property_name' does not exist in '$Property' If you move a property from the root level or from one group to another group in the app properties (using the drag-and-drop feature), at an activity level, existing mappings are not updated in the input data or map?$Prop?$Property?ext field. FLOGO-9444 Search in app property does not return a match if that app property does not have any value. FLOGO-9742 When using access credentials and a session token generated from the AWS portal, the Queue URL is not shown in the SQS SendSQSMessage activity and SQS ReceiveSQSMessage trigger. TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP SuccessFactors BWSS-205 When using the Tenant Type as Production in the SAP SaaS Connection resource, the HTTP response code 403 error message is displayed.

What?s New Develop/TIBCO Flogo® Connectors TIBCO Flogo Connector for Oracle Database Added support for connections to Oracle Database using Service Name. (WIORA-220)Added support for Oracle 19c RAC. (WIORA-246) Integrate/TIBCO BusinessWorks? Plugins TIBCO ActiveMatrix BusinessWorks? Plug-in for LDAP Support for Visual Diff Two revisions of a process and its artifacts can now be compared side-by-side visually in TIBCO Business Studio? for BusinessWorks?. It highlights changes in newer revisions such as the addition or removal of activities, and changes in an activity configuration. You can also compare shared resources. Connection Timeout Field The LDAP Connection Shared resource supports the Connection timeout field. Connection object timeout can be configured using this field. Support for New Active Directory Servers This release adds support for the following Active Directory servers: Server --> Version Microsoft Active Directory Lightweight Directory Services--> 2019, 2022Microsoft Active Directory Domain Services --> 2019, 2022Red Hat Directory Server --> 11.xOpenLDAP--> 2.5.x, 2.6.x TIBCO ActiveMatrix BusinessWorks? Plug-in for SmartMapper Upgraded third-party libraries TIBCO ActiveMatrix BusinessWorks? Plug-in for SWIFT Support for CBPR+ messages In this release, the plug-in supports for SWIFT CBPR+ messages and it only supports MX Schema validation. To view the complete CBPR+ messages, you can refer to the Supported CBPR+ Messages section in the TIBCO ActiveMatrix BusinessWorks? Plug-in for SWIFT User Guide. Support for SWIFT MT Standard Release 2022 In this release, the plug-in supports the SWIFT MT Standard Release 2022. Support for part of SWIFT MX Standard Release 2022 In this release, the plug-in supports part of SWIFT MX Standard Release 2022. Support for new SWIFT MX message In this release, the plug-in supports secl.010.001.03, camt.050.001.06, and pacs.009.001.10 SWIFT MX Standard Release 2022. Changes in Functionality Develop/TIBCO Flogo® Connectors TIBCO Flogo Connector for Oracle Database The SID field is now changed to the Database Instance value field. (WIORA-255) Deprecating and End of Support TIBCO Flogo Connector for Oracle Database no longer supports Oracle Database 12C and Oracle Database 18C RDS. (WIORA-239) Closed Issues IPAS-20787 TIBCO® Cloud Integration fails to send images through SendHTTPRequest activity.

What?s New TIBCO Cloud? Integration Added two new API methods used to build a TIBCO Flogo® app executable from an application JSON file and then download that executable based on a build ID. The methods are as follows: (IPAS-20260) POST /v1?/subscriptions?/{subscriptionLocator}?/app?/build?/flogoGET /v1?/subscriptions?/{subscriptionLocator}?/app?/build?/flogo?/{buildId} Added two new command options to the Hybrid Agent start command in the Command Line Interface: (IPAS-20193) data-chunk-size - Sets the maximum size of data for a single read-write operation. Default is 32KBdata-ack-mode - Specifies the data ack mode. Defaults to true if not specified. Added support for registering the Hybrid Agent as a Windows Service, which improves reliability. If the Windows server hosting the Hybrid Agent is shut down, the Hybrid Agent service is restarted when the server is restarted. (IPAS-17712) Develop / TIBCO Flogo® Support for AWS AppConfig - You can now use AWS AppConfig along with a Flogo app. You can use AWS AppConfig to configure, manage, and quickly deploy Flogo app configurations.Support for object type as a query parameter - The InvokeRESTService activity now supports the object type as a dynamic query parameter. Only a simple JSON object type is supported.UI revamp of app properties - The revamped app properties User Interface provides an improved user experience while working with app properties.HTTP Client Authorization Connection - If you select OAuth2 as the authorization type, you can now specify a unique identifier of the audience for an issued token. The audience value is an app client ID for an ID token or the API that is being called for an access token.Integration with TIBCO Cloud? API Modeler - Flogo can now be used with TIBCO Cloud? API Modeler, a new version of the API Modeler. This version is an easy and powerful web-based tool that allows you to create and model APIs graphically.Execution History for Flogo Apps - You can now use the TIBCO Cloud? Integration Execution History service to publish, store, and retrieve execution statistics generated by Flogo apps. The execution history data is stored in an on-premises database or a database hosted on the cloud. The execution history data is displayed on the Execution History tab of the App Details page for a specific app. Develop/TIBCO Flogo® Connectors TIBCO Flogo® Connector for Amazon S3 New activity added to support Amazon S3 select. The Amazon S3 Select Object Content activity scans the Amazon S3 objects and filters the data in the buckets. (FGAZS3-120) TIBCO Flogo® Connector for TIBCO Cloud? Messaging TIBCO Cloud Messaging (eFTL) connector now supports tracing applications using the OpenTelemetry collector. For more details see, 'Tracing Apps by Using OpenTelemetry Collector' in the user guide. https://integration.cloud.tibco.com/docs/index.html#Subsystems/flogo/flogo-all/telemetry.html (FGTCM-192) TIBCO Flogo® Connector for TIBCO® Data Virtualization - New! Added a new connector that supports query to TIBCO® Data Virtualization. (FGTDV-19) TIBCO Flogo® Connector for Microsoft SQL Server Added support for Azure SQL Server. (WIMSSS-449) TIBCO Flogo® Connector for Salesforce Supports regenerate JSON Web Token when using OAuth 2.0 JWT Bearer Flow authorization type. (FGASFC-359) TIBCO Flogo® Connector for Stripe There are no new features in this release. Integrate/TIBCO BusinessWorks? Plugins TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Cassandra Added support for DataStax Enterprise 6.8. (BWAC-422) TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM Added support for using DynamicFetchXML in Query REST Entities. (DCRM-1945) TIBCO ActiveMatrix BusinessWorks? Plug-in for OSISoft Pi There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake The following features have been added in this release of the TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake. For more information on these features, see TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake User's Guide. https://au.integration.cloud.tibco.com/docs/index.html#Subsystems/bwpluginsnowflake/users-guide/plugin-overview.html Snowflake Bulk Load Activity (BWFL-342) - Snowflake Bulk Load is a new activity that enables the loading of mass data into Snowflake using the JDBC copy command via stage or Amazon S3. For more information, see Snowflake Bulk Load Activity in the TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake User's Guide. The Snowflake Bulk Load Activity provides support for data compression by default. https://au.integration.cloud.tibco.com/docs/index.html#Subsystems/bwpluginsnowflake/users-guide/the-snowflakebulkload-activity.htmlSupport for New Authentication Types (BWFL-350, BWFL-354) - The Snowflake JDBC Connection shared resource now supports the following authentication types. Federated authentication and SSO with OktaExternal OAuth with OktaSnowflake OAuthSupport for Merge Operation (BWFL-464) - The Merge operation is now supported for Snowflake Insert, Snowflake Update, and Snowflake Delete activities.Support for Automatic Table and Column Creation for Snowflake Bulk Load and Snowflake Insert activities (BWFL-502) - The plug-in runtime now supports automatic creation of the Snowflake table if it does not exist and automatic creation of columns if it does not exist in the Snowflake table.Support for Table Name Module Property when using External Schema (BWFL-513) - The plug-in runtime now supports the module property for table name when an external schema is used. Changes in Functionality Develop / TIBCO Flogo® If you are entitled to TIBCO Flogo Enterprise and you would like to get access to TIBCO Cloud Integration to design your TIBCO Flogo apps, you can send a Support Request here by using a template to provide the required Cloud contact details for us to provision Cloud access. See the template here: /s/article/Request-access-to-TIBCO-Flogo-Enterprise-on-TIBCO-Cloud-IntegrationIn support of moving TIBCO Flogo Enterprise to a cloud-first design experience, entitled customers shall have access to the latest versions of TIBCO Flogo Connectors with TIBCO Cloud Integration - Develop (Flogo). No new releases will be provided on edelivery.tibco.com for the TIBCO Flogo Connectors compatible with TIBCO Flogo Enterprise Web UI. For more information, see the TIBCO Flogo Connectors and deprecation of TIBCO Flogo Enterprise Web UI article in the Support Community. https://support.tibco.com/s/article/TIBCO-Flogo-Connectors-and-deprecation-of-TIBCO-Flogo-Enterprise-Web-UISSL certificates generated using Subject Alternative Names (SAN) (FLOGO-9210) - If a client app fails due to a missing SAN field in the certificate, you must configure the certificate with a valid SAN and repush the app.Validation rules at design time (FLOGO-9436) - Validation rules for a string type and primitive expression at design time have changed. The validation of an expression that expects a string now allows you to return a primitive data type such as boolean and number. For example, if the following expression is used in an activity that expects a string message, an error message is not displayed for the returning number types: $flow.body.Customer[1 + 1].ID == 1 ? $flow.body.Customer[1 + 1].ID * 2 : $flow.body.Customer[1 + 1].ID + 10 TIBCO Flogo® Connector for Stripe We have updated the Connector for Stripe to support the latest version of the Stripe API (2022-08-01). This change includes any breaking changes referenced in the Stripe API documentation after the 2019-12-03 version. Update any applications using the Stripe connector to address these breaking changes. See the API Versions section of the Stripe API Upgrades page for a list of breaking changes. https://stripe.com/docs/upgrades#api-versions (WISTRP-324) Integrate/TIBCO BusinessWorks? Plugins When a new version of a TIBCO BusinessWorks Plug-in is released and that plug-in supports Supplements, you must upload the Supplements for the plug-in again in TIBCO Cloud Integration. If you deploy a new app or redeploy an existing app and the associated Supplements have not been reuploaded, the app deploy fails. For this release the updated plug-ins that require you to reupload supplements include: TIBCO ActiveMatrix BusinessWorks? Plug-in for OSISoft Pi Closed Issues TIBCO Cloud? Integration IPAS-19961 TIBCO Cloud Integration - Connect App Status counts are not included in the total App Status Filter counts in the left pane of the TIBCO Cloud Integration Apps page. IPAS-19294 Apps created by using the TIBCO Cloud Integration - Connect POST /v1/orgs/{orgId}/solutions/{solutionId}/cloneAsync API method with the byReference parameter enabled (true) share resources with the source App. Source Apps and target Apps that share resources cannot be edited. In the TIBCO Cloud Integration - Connect User Interface, you can open those Apps and the Flows they contain, but attempting to edit them generates an error and the changes cannot be saved. The User Interface currently does not block access. IPAS-19746 The name of the TIBCO Cloud Mesh service is not getting updated in the Service registry when the app is pushed from the TIBCO Command Line Interface with a modified name. IPAS-19521 When scheduling a TIBCO Cloud Integration - Connect app, on the User Interface the time zone defaults to the International date line west (UTC-12:00). Internally the time zone defaults to UTC, causing the app to run at the wrong time. IPAS-18542 The Hybrid Agent system requirements documentation does not include Minimum CPU and Memory requirements. The minimum CPU is 1. The minimum Memory is 512 MB RAM. Note that CPU and RAM usage increases as the workload on the agent increases. IPAS-18162 Occasionally, HTTP Status 504 Gateway timeout errors are generated when attempting to upload a supplement for TIBCO BusinessWorks plug-ins. IPAS-13644 When switching between the Apps List and the App Details for an app, the app instance number displayed sometimes does not match. Develop/TIBCO Flogo FLOGO-8732 The Flogo app that is deployed using TIBCO Cloud Integration API does not display on the User Interface because the FLOGO extension is not uploaded. FLOGO-8041 When a Flogo app is deleted using the Delete app API, the Connection usage count is not updated. Develop / TIBCO Flogo Connectors TIBCO Flogo® Connector for Microsoft SQL Server WIMSSS-445 Added retry logic in case of Broken-pipe error. TIBCO Flogo® Connector for TIBCO Cloud? Messaging FGTCM-191 The TIBCO Cloud Messaging publisher fails to publish a message if InvokeRest activity output having an array is mapped in the message field.

April 23, 2024 Closed Issue Change in Functionality Able to add/select a subdomain value while creating new API Definition using Import URI or Import file options. April 2, 2024 Closed Issue WA-13161 - The V3 call gives null response for endpoint "updated"&"created". EIN-10108 - Resolved the issue where Mesh-based transformation causes Intemittent 500s+NPEs. Change in Functionality Have an API to pull the response filters used on a given plan and all of its methods. March 12, 2024 Closed Issue WA-13520 - Resolved the issue for misconfigured attributes for the developer page. February 20, 2024 Change in Functionality Able to set PackageKey expiry on the Plan level. The SAML certificate is updated in the Prod Environment. The SAML certificate is updated in non-prod Environment. January 23, 2024 Closed Issue WA-13375 - Resolved the issue for the outdated links on CAPIM Control Center / Additional Help section. WA-13102 - Resolved the issue where the incorrect curl is generated via APIM swagger. WA-13508 - Resolved the issue where the TIBCO Event Trigger Notification Calls to KLM failed with 403. WA-13084 - Resolved the issue where the save buttons were not working when you try to create new interactive documentation. WA-13249 - Resolved the issue where the multiple servers in the OAS are not working as variable. November 14, 2023 Closed Issue WA-13333 - Resolved the issue where the endpoints with path parameters conflict with themselves when the parameters are renamed. EIN-11502 - Resolved the issue where a valid request for a deleted path returned 596. Change in Functionality Able to set empty value to "Your Public Traffic Manager Domain" for new endpoints. Able to get the hourly usage data for the package key using v3 API. November 7, 2023 Closed Issue WA-13312 - Resolved an intermittent issue where JavaScript in Content Pages was not working. WA-12628 - Streamlined notification process for whitelisting client domains for improved turnaround time. Change in functionality Added ability to disable the developer email notification for new package key creation. Resolved an issue where an error occurred while calling private endpoints with multiple paths. October 31, 2023 Closed Issues WA-13201 - Resolved the issue where the page 4 of the package keys page were not loading data. WA-12751 - Resolved the issue where the unexpected additional route occurred in Load Balancing when creating new endpoint. October 17, 2023 Closed Issues Change WA-13155 - Resolved the issue where the Mashery v3 API content-type response header is incorrect for error conditions. WA-12832 - Resolved the issue where the notifications are not enabled during V3 Package create event when notifyAdminEmails are set. WA-13306 - Resolved the issue where the Terms of Service and Privacy Policy links were incorrect on the member registration page. WA-7049 - Resolved the issue where the External Oauth server invocation for access token fails form I/O docs. Change in Functionality Implemented improved user logging and tracking in Control Center. October 10, 2023 Closed Issues EIN-11518 - Resolved an issue where the Interactive documentation upload gave 'A system error has occurred while processing your request'. September 12, 2023 Closed Issues WA-12932 - Resolved an issue where XSS can execute following Application registration when specific payloads are provided. WA-12867 - Resolved an issue where a call to return Package Keys responds with an Integer-Id instead of an UUID. EIN-11410 - Resolved an error handling issue where a request for a deleted endpoint is accepted rather than rejected. Change in Functionality Change to updated Package Key search to display packages in alphabetical order August 22, 2023 Closed Issues WA-13137- Resolved an issue in the service mesh where PostService was not able to set a PublicEndpointPath. August 8, 2023 Closed Issues WA-13805 - Audit History logs now provide more granular detail regarding changes to a specific plan.. EIN-10724 - Resolved an issue where a deleted/disabled key continues to work while using HTTP Basic Authentication Connector for SAAS. August 1, 2023 Closed Issues WA-13185 - Resolved an issue where a user could not re-enable a package key previously disabled. WA-13186 - Resolved an issue where audit logs did not record disabled member status. July 25, 2023 Change in Functionality Templates for Control Center and Developer Portal notifications for new member registration are now consistent. July 4, 2023 Closed Issues WA-13139 - Resolved the issue where V3 API call fails when Mesh endpoint is in a different region. Change in Functionality Clients can now create trial API/MAPI keys that automatically expire after a defined period of time. June 27, 2023 Closed Issues EIN-10655- Resolved an error handling issue where a request for a deleted endpoint is accepted rather than rejected. EIN-11057 - Resolved an error handling issue where a request for a deleted endpoint is accepted rather than rejected. June 20, 2023 Change in Functionality Resolved the issue where V3 API call fails when Mesh endpoint is in a different region. May 30, 2023 Closed Issues EIN-10861 -Resolved the issue where the backend slowness was resulting in socket exhaustion across the EU SNI Stack. Change in Functionality Package keys that automatically expire are automatically deleted, and Traffic Manager will return a 403 Developer Inactive message May 23, 2023 Change in Functionality Added ability to allow values less than 60 seconds for Cache TTL. Added the provision to communicate SSL certificate expiry through Admin Dashboard. May 16, 2023 Closed Issues WA-12772 - Resolved the encoding issue of the feedback form. WA-12964 - Resolved the issue related to LABEL_EXPIRES field explanation. Change in Functionality Areas can now optionally implement a variety of data retention and anonymization policies. March 28, 2023 Change in Functionality Added configuration option to restrict Organization Administrators from adding, editing, or deleting applications outside of their assign role. TIBCO Support must be contacted to enable feature. March 9, 2023 March 7, 2023 Closed Issues WA-12494 - IllegalStateException error seen when deleting an API created through Swagger, and recreating the API using the same Swagger. WA-12583 - Custom developer email notification template was not being applied even though a new API key was issued. Change in Functionality The Notification Email that is sent to Administrators is now editable. When automating API publishing within a CI/CD pipeline, users now have access to manage APIs within TIBCO Cloud API Management via the Platform API created within TIBCO Cloud (TCI, BW, etc.). Also, users are now able to analyze available endpoints, paths and methods through TIBCO Cloud Mesh. February 28, 2023 Closed Issues EIN-10456 -Resolved a URL routing issue, for a specific call scenario, during call transformation. Change in Functionality Users can now create Admin-specific email templates for Package Key notifications. February 21, 2023 Closed Issues EIN-10181 -Resolved an issue where the X-Mashery-Message-ID header failed to propagate during call transformation. February 14, 2023 Closed Issues WA-12417 - Resolve an issue where a disabled user's keys remained active. WA-12556 -Introduced an enhancement to include the entire payload on package key deletion events, similar to package key creation events. January 31, 2023 Closed Issues EIN-10501 - Resolved issue where the backend slowness was resulting in socket exhaustion across the EU SNI Stack. EIN-10503 - Failsafe set for an area triggered 503 Service Unavailable errors for other areas. January 24, 2023 Closed Issues WA-12562 - Resolved issue where My Account - Appplications page still had keys data displayed. January 10, 2023 Closed Issues WA-12662 - Resolved an issue where packageKey couldn't call a particular endpoint. WA-12595 - There are consistent counts on Client Usage Report now. November 01, 2022 Change in Functionality Added ability to disable email notifications when a new application, key, or user is created. Closed Issues WA-12432 - Resolved an issue where the Username error notification is visible only if we have passed through the Captcha verification. October 18, 2022 Change in Functionality Added ability to mask API Keys and Secrets within Developer Portal Closed Issues WA-12114 - Unexpected error when attempting to delete organizations with APIs and Packages has now been fixed. WA-12136 - The Organization of an API can now be changed to Area Level in Untethered Cloud API Management Local Edition. October 11, 2022 Change in Functionality Administrators are now able to generate reports identifying client utilization of a given endpoint. Closed Issues WA-12425 -Resolved an issue where seconds to attempt initial connection to endpoint cannot be set to more than 7 seconds. WA-12453 -Resolved I/O Docs vulnerability issue. October 4, 2022 Closed Issues WA-12493 -Resolved an issue, when transforming an OAS 3.0 Swagger payload via API, where specified custom ports were not included in resulting APIM definition. September 20, 2022 Change in Functionality Added support for reassignment of sub-organizations (to Parent orgs) Closed Issues WA-12447 -Resolved an issue that prevented applications from moving across users. WA-12460 -Enhanced error logging in flows where application ownership is changed. WA-12504 -MARK API for POST/application now correctly supports validation for "id" field. September 13, 2022 Closed Issues EIN-9570 - Resolved an issue where specific forwarded headers were missing in authentication calls. September 6, 2022 Change in Functionality You can now detect if the last package key is deleted in the delete package key event. Closed Issues WA-12107 - Resolved an issue where applications have is_packaged set to false even though there are package_keys assigned. WA-12470 - Resolved an issue where IODocs default option didn't work. WA-12442 - Developer portal issue. July 26, 2022 Closed Issues WA-12400 - Resolved scenario where users were unable to clone endpoints. WA-12396 - Resolved issue where character-specific changes to endpoints could not be made. Changes in Functionality When deleting or removing a domain from an area, and an error is given, service details are now added with the error. July 12, 2022 Change in Functionality Enhanced user experience in Developer Portal by improving accessibility and searchability of API Documentation. Email notifications now occur for the creation of new user/package keys via the V3 API. Session timeout behavior has been enhanced to improve user experience and prevent data loss. June 28, 2022 Closed Issue EIN-9643 - Introduced infrastructure improvements to decrease data synchronization latency and quicken data accessibility. June 21, 2022 Closed Issues WA-12301 - Resolved a scenario where erroneous "Maximum limit reached" notifications are presented when creating new API definitions in the Organization. WA-12267 - Resolved an issue where API/endpoints were responding unexpectedly to specific package/plan configurations. June 07, 2022 Closed Issue WA-6834 - Eliminated erroneous prompts when adding API Key inputs on the Developer Portal. May 24, 2022 Change in Functionality Enabled an enhanced theme on the Developer Portal for improved user experience. Closed Issues WA-12243/WA-12144 - Resolved an issue where the API application threw an error while adding API endpoints to a package/plan. WA-12013 - Allow toggle to deactivate "autocomplete" browser functionality on the DevPortal login. WA-11656 - Resolved "duplicate entry" errors when adding endpoints to a plan. WA-10472 - Unable to update the Plan Designer. May 10, 2022 Change in Functionality Updated response code for the JWT authenticator when an invalid token is passed in the API call. Closed Issues WA-12218 - The Portal Setup documentation link, API Management Customization Documentation, has been fixed. EIN-9612 - Resolved an issue where the REST > SOAP connector failed to render the correct content hierarchy in SOAPBody. April 26, 2022 New Feature Introducing a new optional query parameter, (record_offset), for MARK (Members, Applications, Roles, Keys) objects. More information can be found here and here. Closed Issue WA-12268 - Resolved an issue where API/endpoints were responding unexpectedly to specific package/plan configurations. April 19, 2022 Closed Issues WA-12252 - Addressed a scenario where inactive plans could not be accessed, deleted, or re-enabled. EIN-8908 - Resolved an issue where a SOAP endpoint WSDL retrieval request updated only the hostname and not the URI/path. April 12, 2022 Changes in Functionality Implemented health checks of APIs for "ptl" and "api-v2" workers to resolve sporadic permission-based errors. Resolved a processing issue where the lighttpd server became destabilized due to lighttpd error logs. Service Endpoint type is now displayed as "standard" or "token" for GET Service definition endpoints on package/plan level. Enhanced DevPortal login experience to include richer security configurability options. April 05, 2022 Change in Functionality Resolved an issue where token endpoints were responding unexpectedly to 'OPTIONS' (preflight) requests. Closed Issues EIN-9512 - Resolved an issue where creating tokens without an Origin header, using the token endpoint (V3 API), responded unexpectedly. EIN-9506 - Resolved an issue where CORS-enabled endpoints were responding unexpectedly to preflight requests. EIN-8767 - Resolved authentication error of API Key in request body for ?Content-Type: application/json?. March 22, 2022 New Feature Added visibility of functionality for plan/package EAVs. Changes in Functionality Redesigned Plan Designer page by separately sorting in-use API endpoints and methods for better user experience. Improved functionality by allowing propagation of rate limits from the plan/key level to the method level on existing endpoints. Added support for custom error codes. Closed Issues WA-12119 - Resolved a sporadic response inconsistency in V3 API (GET) invocation. WA-12055 - Increased the number of visible organizations within User Access configuration. WA-11117 - Resolved an error where a deleted endpoint was displayed as ?active? in the plan_endpoints table database. EIN-9403 - Addressed a scenario where limit values at the PackageKey level were not honored when Plan level limits were unlimited/different. EIN-8675/EIN-7846 - Resolved Memcached inconsistencies after configuration changes. March 08, 2022 Changes in Functionality Removed restriction to add EAVs for packages and plans. API Definitions on the Plan Designer are now sorted and displayed for improved user experience. Improved GET calls retrieving all package keys accessible for a plan. Resolved an inconsistency by adding a "stop on error" configurable boolean field on the Call Transformations page. Improved discovery of packages linked to specific API definition endpoints. March 01, 2022 New Feature Improved readability of functionality for individual EAVs in the Control Center. Changes in Functionality Added a date filter to V3 APIs for improved user experience. Closed Issues WA-12050 - Resolved an inconsistency identified between User Package Keys and Applications. WA-12068 - Updated package ids for existing keys having incorrect package/plan combination. February 15, 2022 Closed Issue EIN-9198 - Resolved Null Pointer exception error after SSL handshake. February 08, 2022 Changes in Functionality Clarified error response in scenarios where package key update fails. Closed Issues WA-12070 - Resolved an issue where the Plan Designer page didn't load for any packages. WA-12010 - Resolved an issue where endpoint reversion was not completing successfully. EIN-6001 - Addressed a scenario where API Management sync displayed Turkish time zone instead of UTC or user timezone. February 01, 2022 Closed Issues WA-12008 - Addressed a scenario where any low-privileged user was able to issue SQL queries to access sensitive information. WA-11955 - Addressed an issue where a new/cloned endpoint didn't work with the AMSData URI. WA-11888 - Resolved an issue where one could easily access/download the Swagger specifications from the API Management without authentication. EIN-8691 - Resolved Memcache inconsistencies after configuration changes. EIN-1369 - Resolved Memcached inconsistencies after configuration changes. January 25, 2022 Changes in Functionality Resolved an issue where API Management sent notifications for the user, key, and application activity using an outdated PHPMailer. Added functionality to retain the entries in public_domain_endpoints by marking them as "not-active" when the state changes to "deleted". January 11, 2022 Change in Functionality When a user is about to delete the account of any other user in Mashery, a warning appears with the necessary actions that would be taken on deleting that particular user. Closed Issues WA-11803 - Blocked the creation of endpoint/s with relative path "/../" in the URI. WA-11788 - Resolved an issue related to the mismatch of user data in the database. WA-11777 - Masked the API keys in the email notification when the Call Inspector was Enabled/Disabled for the Mashery Cloud. November 16, 2021 Changes in Functionality SOAP Cache Connector default TTL (Time-to-live) value of 300 seconds can now be overridden by Endpoint TTL or Service TTL. For more information, refer to the SOAP Cache Connector. REST Cache Connector default TTL (Time-to-live) value of 300 seconds can now be overridden by EndpointTTL or ServiceTTL. For more information, refer to the REST Cache Connector. Closed Issue EIN-8805 - SOAP Cache Connector loses European/Unicode characters. EIN-8854 - Resolved an issue where the Custom HTTP headers configured in Mashery APIs had "encoded" values instead of actual values. EIN-8488 - Analyzed and resolved the issue related to AWS Lambda Sidecar Integration Connector. November 9, 2021 Closed Issue WA-11611 - Resolved a sporadic issue where an SSO user is unable to access an API Definition. WA-11739 - Users removed from TIBCO Cloud were still showing up in Control Center. October 20, 2021 Changes in Functionality On the Plan Designer page, the defined fetch limit to fetch all endpoints in multiple calls has been set to 600. Enabled "Full" SSL support on Mashery developer portals by default; previously set to "None". Pre-flight check added in CIC Subscription provisioning to verify if the current Mashery area name already exists. Closed Issue WA-11824 - Changed queries in PersistedServiceMapi to select based on the status i.e. "not-deleted" instead of "active". EIN-8850 - Resolved the issue related to InjectModelAttributeHeader and InjectConditionalHeader connectors when the call is run through EU-Central. October 13, 2021 Closed Issue EIN-7977 - Resolved OAuth issue related to U.S. Daylight Savings time change. October 6, 2021 Improvements SOAP Cache Connector / REST Cache Connector - When defining cache_ttl at the service level or endpoint level, then the regular cache is coming into play and it is overriding the SOAP Cache Connector/REST Cache Connector. Now, cache_ttl will be defined in pre input and not at the service level or endpoint level. September 28, 2021 Changes in Functionality Tool Tip Text Update for Cache Disabling The following tool tip is now added for how to disable caching once Cache Time-to-Live feature is enabled on the API Service and API Endpoint pages: "Setting a value of 0 will disable caching." Closed Issues WA-11756 - Resolved an issue with custom key creation in specific scenarios. WA-11691- Addressed a reported issue causing frequent logouts in Mashery Cloud. WA-11730 - Addressed a filtering issue with Organization picker within TIBCO Cloud Mesh. WA-11489 - Addressed a Mashery V3 API call issue when moving a given package key from one API Package to another API Package. For more information, see the Package Keys topic in the Mashery Cloud API documentation. EIN-8440 - Resolved a sporadic issue involving erroneous access to a defined Method not included in a Plan. September 14, 2021 Changes in Functionality Implemented optimizations to Service Definition configuration. Closed Issue WA-11704 - Package key audit history 'Changed By' column was incorrectly showing the owner of the key instead of the user that made the change. August 31, 2021 Closed Issues WA-11596 - Pagination was not working as expected on the HTTPS Client Profile page. WA-11715 / WA-11724 - Mashery throwing Duplicate Entry error for a particular URI. WA-11668 - Unable to change the Application Owner. WA-11689 - Resolved an intermittent accessibility issue within the Content Page of the Developer Portal. August 10, 2021 Changes in Functionality Developer Portal - TIBCO analytics tags updated/removed (Google Analytics). Added support for rejecting the whitelisting of a top-level domain when a sub-domain is already approved and or in use. Interactive Documentation within the Mashery Cloud Control Center now lists the current versions of endpoints. Closed Issues WA-11626 - New member profiles created during ?Invite New Members? now default to the user?s First Name and Last Name. WA-11691 - Addressed an uncommon scenario where users experienced sporadic logout behavior. July 27, 2021 Change in Functionality A Cancel button is added in the confirmation popup windows. Closed Issues WA-11590 - Fetching the service and endpoints using the Mashery API fetch call to the plans were returning invalid dates. WA-11678 - Content added (Using Manage -> Contents -> Select any random custom page) were not getting saved. WA-11434 - Pages (and their child pages) in the Developer Portal were not visible to users as expected. WA-11519 - The HEAD request to get the X-Total-Count header did not work consistently across resources. June 29, 2021 Change in Functionality IP Whitelisting Connector updated for improved compatibility with Azure. June 15, 2021 Closed Issue WA-11533 - Resolved admin issue of creating/deleting sub-organizations. June 01, 2021 Change in Functionality Admin is now warned if an Admin user has an Mashery API key while being disabled or deleted. Closed Issues WA-11426 - Cloning of an Application Service Registry endpoint now works as expected. WA-11538 - Issues with Mashery user accounts having special characters in TIBCO cloud account now fixed. May 18, 2021 Closed Issues WA-11344 - Updated visibility and access for the API Manager role to view HTTPSClientProfile in Mashery Control Center. WA-11554 - Developer portal key activity reports were not returning any data. This issue has been fixed. April 27, 2021 Change in Functionality When using the Mashery Platform API to CreateAccessToken, if User_Context is not passed in the call, the response will return a ?null? value instead of a blank value. Closed Issues WA-11270 - General performance, security, and stability fixes. WA-11255 - Resolved issue which prevented Organization Admins from creating Sub-Organization Endpoints. April 20, 2021 Change in Functionality The behavior of the Service User role has been updated: Service User can be assigned along with other roles. ACL Permissions of roles other than Service User role determine the access permission for the user. Evaluation Area Creation: For the auto-generated user with Service User, an Administrator role is now added in the creation process. Closed Issues WA-11518 - Resolved error during login from TIBCO Cloud into Mashery Control Center under a specific Organization/Child-Organization. WA-11456 - Updates to use and scope of Service User roles. WA-11316 - The Delete audit trail history for an API Package Key after a Package/Plan is deleted was missing. This is now fixed. April 13, 2021 Change in Functionality The user_context field is now included in the response from TIBCO Cloud Mashery. March 30, 2021 New Features Enriched Call Log Export (ECLE) has been updated as follows: All ECLE profiles now require the enhanced security configuration which includes assumed-role access and native s3 bucket encryption. As communicated in the past, all un-encrypted and IAM access functionality will be deprecated and all the un-encrypted configurations will be disabled. Please see the setup instructions present on the Control Center ECLE page for more information about configuring your AWS account prior to creating or updating an ECLE profile. Added the ability to validate API calls using encrypted JWT JWE (JSON Web Encryption). Change in Functionality General performance, security, and stability improvements. (AJ-2249, AJ-2260, AJ-2281, AJ-2294, AJ-2298, AJ-2322) March 2, 2021 New Feature Support for Mutual Transport Layer Security (mTLS) Control Center UI updated for supporting mTLS (Mutual TLS) configuration for endpoints. mTLS ensures verification between client and server. Note this feature is only for Mashery Local 5.3.1 and above customers, who are using tethered mode only. Change in Functionality General performance, security, and stability improvements (WA-11271, WA-11351, WA-11437). Closed Issue EIN-8084 - Broken formatting on Call Inspector Call Detail panes. This is now fixed. February 9, 2021 Change in Functionality General performance, security, and stability improvements (WA-11253). January 26, 2021 New Feature Ability to Configure Content Security Policy (CSP) for Developer Portal A Content Security Policy (CSP) editor is now available when configuring a Developer Portal. For more information, refer to Customizing your Portal. Change in Functionality General performance, security, and stability improvements (WA-11275, WA-11385). November 10, 2020 New Feature The Service User role, initially available only for CIC areas, is now available on all areas. Once a user is assigned this role, the user will not able to login to the Control Center/Dashboard. The appropriate warning/confirmation is displayed to the user when this role is assigned to any member in the Access settings panel. A user assigned to this role will be able to invoke APIs as an area admin. A service user will be also able to login to developer portal. October 29, 2020 New Features The API Policy Connector has been updated with the following new feature: JWE (JSON Web Encryption) support for third party JWT token. Compliant to JWE RFC https://tools.ietf.org/html/rfc7516. Supports following key algorithms and content encryption algorithms: JWE 'alg' : [ RSA1_5, RSA-OAEP, RSA-OAEP-256, ECDH-ES,ECDH-ES+A128KW, ECDH-ES+A192KW and ECDH-ES+A256KW] JWE 'enc' : [ A128CBC-HS256, A192CBC-HS384 and A256CBC-HS512, A128GCM, A192GCM and A256GCM, HS512] OIDC Token Authentication Connector The OIDC Token Authentication Connector is now available. This Connector supports securing APIs in TIBCO Mashery using third party OIDC IDP based ID token. Features include: Ability to configure up to ten user info endpoints per service endpoint for ID validation using any third party OIDC IDP. Conditional pickup of user info endpoint for user info based on incoming meta data for geo-distributed API services. Ability to enrich API request header with user info meta data that is returned after successful ID validation. Support for strict case sensitive method for GET and POST calls to third party OAuth2.0 Auth server user info endpoint. HTTP Verb must be case-sensitive and supported that way in compliance with RFC 7231 guidelines. Support of configurable parameter enable_error_set to control error response code sent by TIBCO Mashery. If enable_error_set is configured as "true", TIBCO Mashery responds with ERR_403_NOT_AUTHORIZED that is Gateway supported error message. In this case, http response status code and status text for connector is overridden by error set defined for that endpoint in Mashery Control Center. If enable_error_set is configured with value other than "true", then there is no change in Mashery Connector existing functionality that responds with ERR_401_UNAUTHORIZED for backend server response code with 401 for unauthorized calls. enable_error_set parameter value with "true" is case-insensitive. Support of UserInfo error responses on error condition as defined in the OAuth 2.0 Bearer Token Usage Specification. https://tools.ietf.org/html/rfc6750#section-3.1 Change in Functionality The SOAP WS-Security Connector has been updated with the following enhancements: Supports SOAP message payload size up to 1024 KB (1 MB). Error handling improvement for accurate checking of supported signature and encryption algorithms. October 27, 2020 New Feature New Organization-specific Role: Organization Support User Added new organization-specific role - Organization Support User - for all organizations including existing organizations. The Organization Support User role has read-only access to all pages in the API Control Center dashboard with data filtered based on the Organization. Buttons (such as Save, Create, Edit, and Delete) and various fields (such as check boxes and text boxes) are disabled for Organization support users. Change in Functionality The warning message for 'Time to wait for a response from endpoint' has been updated to specify that it applies only for Mashery Cloud calls (and not for Mashery Local). Closed Issues WA-11295 - Fixed general issues related to Dapi. WA-11282 - Map Overlay reports were not loading correctly from API Control Center > Reports > Developer Activity > Map Overlay. This is now fixed. October 13, 2020 Closed Issue WA-11105 - Resolved packager-based reporting map overlay display bug. October 8, 2020 New Feature SOAP WS-Security Connector The SOAP WS-Security Connector is now available. This Connector supports SOAP WS-security specs to validate SOAP API calls for SOAP message signature, apply encryption/decryption to enforce integrity and confidentiality on messages. It also supports optionally creating the security header with the timestamp component in the outgoing request to the backend API server. Change in Functionality The AWS Lambda Sidecar Integration Connector has been updated with the following improvement: Better resiliency in error management by incorporating Lambda function custom runtime exception that comes with X-Amz-Function-Error header. (AWS Lambda Runtime Error Handling Documentation.) Improvement to secure and encrypt confidential credential like externalID by integrating with AWS Systems Manager Parameter Store. The REST <-> SOAP Transformation Connector has been updated with the following improvement: Supports accurate Content-Type header for REST ? SOAP transformation for both SOAP1.1 and SOAP1.2 REST(JSON) -> SOAP 1.1 , Content-Type header is set to application/xml;charset=UTF-8 after transformation. REST(JSON) -> SOAP 1.2 , Content-Type header is set to application/soap+xml;charset=UTF-8 after transformation. October 1, 2020 New Feature JSON Schema And Payload Size Validation Connector The JSON Schema And Payload Size Validation Connector is now available. This Connector supports RESTful API request validation using JSON schema provided either in Content Type header or Link header. Features include: Support for RESTful API payload size validation. Optionally supports fail-safe mode for payload size validation. In fail-safe true mode, an API call is forwarded even if it is more than the configured max size but less than max allowed payload size. Supports configuration 'override_custom_error_message' for enabling API service endpoint supported static custom messages to override Connector runtime message. September 23, 2020 Change in Functionality Call Log Export (ECLE) S3 Server-Side Encryption In an effort to provide improved security for the Call Log Export (ECLE) feature, we have added support for S3 Server-Side Encryption. To use this feature, all AWS resources are created by the customer, providing full ownership of the encryption, authentication/authorization, and storage mechanisms using the TIBCO provided CloudFormation template. To activate this feature, enable the Bucket Encryption flag on the ECLE profile create or edit screens. Once the Bucket Encryption flag is enabled, you will need to input fields S3 Bucket Name, IAM Role Arn, CMK Arn, and ExternalId for Role Assumption. This information is generated after successful stack creation using the provided CloudFormation template. For more information, refer to the Setup Instructions provided in the ECLE profile create or edit screen. Because security is more important than ever, we are deprecating the existing IAM based bucket policy functionality in early November. Between the launch of the encryption functionality and the depreciation of IAM bucket policy support, we are requiring customers to run in both modes. The provided CloudFormation template will allow you to either apply the new settings to an existing bucket, or create a new bucket with both sets of configuration. We will notify you once the IAM policy functionality has been disabled, at which point, we recommend that you remove the IAM based policy from your S3 bucket. ECLE profiles not implementing the new encryption policy by November 10th will be disabled until such time their configuration is updated to the new encrypted mode. September 15, 2020 Improvement The API Policy connector has been updated with the following improvements: Extend payload match policy to support SOAP messages. Now payload match policy supports both REST & SOAP. Support of new configuration 'Enable_Error_Set' for enabling API service endpoint supported static custom messages to override Connector runtime message. August 27, 2020 New Feature AWS Lambda Sidecar Integration Connector The AWS Lambda Sidecar Integration Connector is now available. This Connector supports TIBCO Cloud Mashery sidecar integration for AWS Lambda function. Features include: Supports AssumeRole IAM policy with external ID for enhancement security of AWS Lambda resources access in compliance of AWS shared responsibility model. Supports configurable sure-fire and fail-safe modes to invoke AWS Lambda function to influence Gateway action. Supports RESTful POST messages only for AWS Lambda function invocation. Supports optional configurable parameters to apply business policies to influence API behavior in the end-to-end call flow. Change in Functionality The REST <-> SOAP Transformation connector has been updated with the following improvement: Now supports handling of JSON payload with namespace in the transformation. August 18, 2020 New Feature The following headers are added in the response of the Mashery Developer Portal and Mashery Control Center page: X-Content-Type-Options nosniff, X-XSS-Protection 1; Content-Security-Policy. For Content Security policy header, Portal administrators may want to update the Content Security Policy from the Portal Settings page. About Content Security Policy Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. CSP makes it possible for server administrators to reduce or eliminate the vectors by which XSS can occur by specifying the domains that the browser should consider to be valid sources of executable scripts. A CSP-compatible browser will then only execute scripts loaded in source files received from those allowed/listed domains. By default, Content Security Policy header is not added in the developer portal response. Portal administrator can set the content security policy through Control Center > Manage > Potal > Portal Setup page. Administrators can set the content security policy in the given text field. By default, no content security policy is set on the Developer Portal. Example of security policy required for the Developer Portal is provided in the description text. Example - If the administrator wants to set the Content Security Policy, the administrator will copy the example text, replace the value for portal-domain and then add/update any other directives. The policy provided in the example is required by the Developer Portal; hence those values should not be removed. If the administrator wants to allow to load script from another domain, such as abcd.com , and a font from coolfonts.com, then the administrator will add *.abcd.com in the script-src directive and *.coolfonts.com in font-src directive of the example and set the entire text as a new content security policy. August 4, 2020 Changes in Functionality There is a change in the way error messages are displayed to the user. The error message is now more informative with service key and endpoint key information and a hyperlink pointing to existing endpoint. Also a single message is now displayed for all the conflicting HTTP verb instead of one error message for each verb. July 30, 2020 Improvements The OAuth 2.0 Token Authentication connector has been updated with the following improvement: Support of configurable parameter Enable_Error_Set to control error response code sent by TIBCO Mashery. If Enable_Error_Set is configured as "true", TIBCO Mashery responds with ERR_403_NOT_AUTHORIZED in place of ERR_401_UNAUTHORIZED. In this case http response status code and status text for connector is overridden by error set defined for that endpoint in Mashery Control Center. If Enable_Error_Set is configured with value other than "true", then there is no change in Mashery Connector existing functionality that responds with ERR_401_UNAUTHORIZED for backend server response code with 401 for unauthorized calls. Enable_Error_Set parameter value with "true" is case-insensitive. July 21, 2020 Change in Functionality General performance and stability improvements (WA-11046, WA-10992, WA-10843, WA-10786, WA-9402). Closed Issue WA-11039 - While persisting Swagger 2.0 documents, a publicly-available schema document was relocated to a different URL location. Access to this schema document is not required to validate the document, so the reference to this URL has been removed. July 7, 2020 New Features Previously, there was no option to re-parent a Portal Access Group role, once it was created. Now, you can re-parent an existing Portal Access Group role, by going to the edit page of Portal Access Groups, and re-parent it to any other organization or area level based on the permission of the user. RFC compliance for handling cache logic has been implemented. Change in Functionality UI improvements (Plan Designer page) and performance enhancements in API Control Center dashboard. Closed Issues EIN-1052 - Several POST,PUT,DELETE requests failed to return the correct response. EIN-4445 - GET response that was cached was being returned for POST, PUT, DELETE, PATCH and OPTIONS calls to the same endpoint WA-8858 - Improved session management for TIBCO Cloud enabled Mashery subscriptions. Users will no longer risk being logged out of the API Control Center when their session in TIBCO Cloud is left unused, assuming they are actively using the API Control Center. WA-10868 - If the 50 most recently created or updated records in the Organizations list were Sub organizations, the "New organization" button was getting hidden. This is now resolved and the button will not be hidden. WA-10906 - The drop-down value for HTTPS Client Profile went blank or changed to a previous value. WA-11009 - Endpoint address not shown in Load Balancing menu in API Definition configuration. July 2, 2020 Improvements The OAuth Token Authentication connector has been updated with the following improvement: Support for strict case sensitive method for GET and POST calls to third party OAuth2.0 Auth server token validation endpoint. HTTP Verb must be case-sensitive and supported that way in compliance with RFC 7231 guidelines. https://tools.ietf.org/html/rfc7231#section-4 The HTTP Basic Authentication Connector has been updated with the following improvements: Support of 401 (Unauthorized) status code and WWW-Authenticate header field for an empty Authorization header in HTTP Basic Authentication Connector. Improvement is in compliance to RFC https://tools.ietf.org/html/rfc7617 for an empty authorization header in API request needed for HTTP Basic Authentication. Optional configuration parameter to keep TIBCO Cloud Mashery proxy platform response codes for backward compatibility. June 11, 2020 New Features REST <-> SOAP Transformation Connector The REST <-> SOAP Transformation Connector is now available. This Connector supports the transforming of API request payload from REST(JSON) to SOAP and transforming backend SOAP response into REST(JSON). Also, supports RESTful POST messages only for transformation. OAuth2.0 Token Authentication Connector The OAuth2.0 Token Authentication Connector is now available. This Connector supports securing APIs in TIBCO Mashery using third party IDP based OAuth2.0 access token. Features include: Ability to configure up to ten OAuth2.0 introspection endpoints per service endpoint for token validation using any third party IDP. Conditional pickup of introspection endpoint for token validation based on incoming meta data for geo-distributed API services. Ability to enrich API request header with meta data that can be returned after successful token validation. June 2, 2020 New Feature TIBCO Cloud Mesh TIBCO Cloud Mesh allows you to discover any private REST endpoint exposed within TIBCO Cloud domains, within your organization or related organizations. Authentication and authorization for these private endpoints is provided automatically. You can browse available services and select one, rather than copying and pasting a URL. For more information, see Creating an Endpoint using TIBCO Cloud Mesh. Closed Issue WA-10959 - Resolved issue wherein links on API Control Center > Manage > Portal > General redirected to blank pages. May 28, 2020 New Feature Sensitive Data Field Masking for Call Log Export Call Log Export (ECLE) Masking feature allows customers to mask some or all characters in sensitive fields such as API Key and OAuth token in both new and existing ECLE profiles. Customers must update ECLE profile in order to activate for existing exports. For more information, see Call Log Export Setting. May 21, 2020 Change in Functionality Updated API Policy Connector The following improvement was made in the API Policy Connector. Supports 'Effect' factor that drives 'Allow' or 'Deny' behavior on match policy. May 12, 2020 Closed Issues WA-10860 - API Control Center threw a duplicate endpoint error when "/" was included at the end of the request URL path. New Features Revised the UI text in API Control Center for the "Remove API Key and Signature from Endpoint Call" feature for clarity of actual function. May 11, 2020 New Features JWT Authentication Connector The JWT Authentication Connector is now available. This Connector supports match policy to allow additional validation based on JWT claims value. OAuth2JWT Authentication Connector The OAuth2JWT Authentication Connector is now available. This Connector supports match policy to allow additional validation based on JWT claims value. API Policy Connector The API Policy Connector is now available. This Connector allows you to apply policies to change the behavior of the API through configuration. Currently supports Request, Response and third party JWT object context. Additional features of this Connector: Third party JWT Claims Verification Policy. Supports JWT token object context. Third party JWT Signature Verification Policy. Supports JWT token object context. API Payload Attribute Match Policy. Supports Request and Response object context. API policy for finding payload attribute and applying match. Support JSONPath (JSON Payload) and XPath expression (XML Payload). API Request and Response object context based match policy. Supports match keywords using operation ContainsAny, ContainsAll, JSONPath, and XPath. Closed Issues WA-10798 - Conflict when creating a public endpoint resolved. April 2, 2020 Change in Functionality Updated XML <-> JSON Transformation Connector The following improvements were made in the XML <-> JSON Transformation Connector. Support optional charset check in the application/json Content-Type header for accurate JSON ? XML transformation. Support overriding default Connector error messages with APICC configured custom error messages using an optional flag 'override_custom_error_message'. Updated SOAP <-> REST Transformation Connector The following improvements were made in the SOAP <-> REST Transformation Connector. Support accurate caching of POST request having XML payload with namespace. Support overriding default Connector error messages with TIBCO Mashery Control Center configured custom error messages using an optional flag 'override_custom_error_message'. Updated SOAP Cache Connector The following improvement was made in the SOAP Cache Connector. Support accurate caching of POST request having XML payload with namespace. Updated REST Cache Connector The following improvement was made in the REST Cache Connector. Support accurate caching of POST request having XML payload with namespace. March 24, 2020 Closed Issues WA-10685 - Mashery provided OAuth Token endpoint was returning ?Service Not Found? during CORS pre-flight call. WA-10618 - Resolved ACL consistency between API and Dashboard. March 20, 2020 Change in Functionality Updated IP Blocking Connector Following improvements were made in this Mashery Connector: 1. The IP Blocking Connector has been improved to accurately identify Client IP addresses for blocking feature. 2. Connectors now supports overriding default behavior of X-FORWARDED-FOR header to pick client IP address using a configurable flag keep_client_ip_as_source. This flag overrides default selecting IP address of intermediaries like load balancer or third party proxy that is closest to the Mashery stack. March 19, 2020 Change in Functionality Updated IP Whitelisting Connector Following improvements were made in this Mashery Connector: 1. The IP Whitelisting Connector has been Improved to accurately identify Client IP addresses for whitelisting feature. 2. Connectors now supports overriding default behavior of X-FORWARDED-FOR header to pick client IP address using a configurable flag keep_client_ip_as_source . This flag overrides default selecting IP address of intermediaries like load balancer or third party proxy that is closest to the Mashery stack. New Feature REST Cache Connector New Mashery Connector, REST Cache Connector, supports caching of REST POST requests, which allows requests that have the same payload and configured headers value to be served from the cache. March 10, 2020 New Feature Organization-related information (Org/SubOrg Name & UUID) synchronized to Mashery Local for inclusion in logs is now available through Log Service. February 27, 2020 New Features SOAP Cache Connector New Mashery Connector, SOAP Cache Connector, supports caching of SOAP with POST requests, which allows requests that have the same payload and configured headers value to be served from the cache. Ping Auth Connector New Mashery Connector, Ping Auth Connector, consists of the following: Ping Federate OAuth2 Connector - covers frontend security. Ping Federate OAuth2 LMS Connector - covers Last Mile Security. January 21, 2020 New Features Normalize Audit History time zone from PDT to GMT. Support hyphen and underscore in Organization and Sub-Organization names. Closed Issues WA-10600 - Enum values not honored during ?try it now? with Swagger 2.0 on Interactive Documentation resolved. WA-10380 - Manually-entered parameter values were reverting to defaults in interactive documentation. WA-9635 - Page content was blank in CMS on page load. WA-9903 - Second use of authorization resulted in ?Unknown security definition type http? error. January 9, 2020 New Features XML <-> JSON Transformation Connector New Mashery Connector, XML <-> JSON Transformation Connector, supports transforming an API request payload from XML to JSON and vice versa.: SOAP <-> REST Transformation Connector New Mashery Connector, SOAP <-> REST Transformation Connector, supports transforming API request payload from SOAP message to REST(JSON) and vice versa. November 12, 2019 New Feature In an effort to simplify Domain whitelisting, the Control Center has been modified to not allow IP addresses to be specified when adding whitelisted domains. A warning message is displayed if an IP address is specified. November 5, 2019 Closed Issue WA-10256 - Removal of replacement variables in New Member Registration email were being appended to Email regardless of the configured template. This has been fixed. November 1, 2019 Closed Issue WA-10439 - Developer-facing Reporting and CSV download on Developer Portal returning 404 page not found. October 10, 2019 New Feature Time stamp of last login for Developer Portal user now exposed on the member record, accessible via API Call. July 3, 2019 Closed Issue RPT-3250 - Unable to create Amazon S3 bucket path for Enriched Call Log Export (ECLE). June 19, 2019 New Feature Geo Target Routing Connector updated in the TIBCO Cloud? Mashery - Connectors Guide. Mashery Connectors are TIBCO Mashery's Cloud feature plugins and extensions that have been developed and available out of box for Mashery Cloud customers. Connectors have been carefully envisioned to address common use-cases such as: content injection, content filtering, content transformation, call authentication using third-party IDP, IP-based call filtering, domain-based routing, geo-location based routing and HTTP header manipulation.

Storing a variable (or state) of fields/values, multiple entities, and child records can be complex to design and even more difficult to maintain using out-of-the-box functions. In addition, you may want to store a JSON format of your data when using Connectors such as Files, HTTP, and Variables. Using the TIBCO Scribe Online connector for Mapper, you can help you create a blueprint for your dataset, such as JSON, and provide the ability to get and set the entities and fields in that variable/state. These simple flows attempt to demonstrate some concepts and how they can be achieved using the Mapper Connector. Review the Group Block labels in the flows that explain the purpose of the Blocks inside the Group. Prerequisites You can import the Sample App from the marketplace listing by searching for Samples for Mapper Connector and selecting Get. You will also need to Install the other prerequisite Connectors (if not installed already): Sample - CRM Connector and an associated Connection named SampleCRM with no spaces or special characters. On the Connection Configuration dialog set the Use Sample Data field to true to use the sample data distributed with the Connector.Variables Connector and an associated Connection named Variables.Tools Connector and an associated Connection named Tools.HTTP Connector and an associated Connection named HTTP.Mapper Connector and an associated Connection named Mapper. Sample CRM Connector Note the following when using the Sample CRM Connector: A sample database is installed in the agent folder when the Connector is installed.If you have more than one Connect on-premise agent installed, there is a separate database for each agent. In this case, the database associated with the agent that runs an app using the Sample CRM Connection is the database that is updated. If you have multiple agents, you can expect the databases to be different over time.If you are using a Connect cloud agent, there is a separate database for each app that uses the Connect cloud agent. In this case, you can expect the database for each app to be different over time. Mapper Connector The Mapper Connection configuration includes the names of the entities used in the Maps/flows as well as a JSON sample for each entity. Configure the following three entities and copy/paste the associated JSON sample into the Mapper Connection dialog. Entity Name: customer Sample JSON: { true, "string", "string", "string", "string", "string", "string", "string", "string", "string" }, "string", "string", "string" }, "string", "string", "string", "string" }, 10000, true, "string", "string" } }[/code] Entity Name: array_of_customer Sample JSON: [ { true, null, null, "North", null, "Aberdeen Inc.", "ABERDEEN0001", "(617) 832-9863", "(617) 832-7300", "Main" }, "Mr. Harold Michaelson", "President", null }, "SYSTEM_USER", "2016-04-01 00:00:00", "SYSTEM_USER", "2016-04-07 11:07:43" }, 10000.0, false, "Net30", "Retail" } } ][/code] Entity Name: response_array_customer Sample JSON: { true, null, null, "North", null, "Aberdeen Inc.", "ABERDEEN0001", "(617) 832-9863", "(617) 832-7300", "Main" }, "Mr. Harold Michaelson", "President", null }, "SYSTEM_USER", "2016-04-01 00:00:00", "SYSTEM_USER", "2016-04-07 11:07:43" }, 10000.0, false, "Net30", "Retail" } } ] } [/code] Serialize and Deserialize (JSON) This flow demonstrates the following: Starting a flow with no source data for the Query Block.Using a Fetch Block to retrieve Account records from a Sample CRM database.Serializing an Account record input to output JSON. The customer entity in the Serialize Block uses the customer entity JSON sample configured on the Mapper Connection dialog to determine how to map the Account record fields to a JSON format. The objects on the Serialize Block Properties Include tab represent how TIBCO Cloud? Integration - Connect interprets the objects in the JSON sample.Writing the results to the Agent log.Using an Upsert Block to create a variable that stores the JSON so it can be used later in the flow since Fetch Block results cannot be accessed outside of the Fetch Block.Using a Loop Exit Block to exit the Fetch Block. This forces the Fetch Block to only process one record at a time instead of all of the records returned by the Fetch. The flow can then process the record stored in the variable before processing any additional Account records.Using a Lookup Block to retrieve the customer record from the variable.Using a Fetch Block to deserialize the JSON. The Filter tab captures the JSON returned from the variable retrieved in the previous Block and deserializes it based on the sample JSON in the Mapper connection dialog.Using an Execute Block to write the response to the Agent log. Working with Arrays This flow demonstrates the following: When configuring sample JSON in the Mapper Connection dialog, the square brackets [ ] indicate that the sample is an array. The top-level of this array corresponds to the object labeled Anonymous in the Include tab of the Serialize and Fetch Blocks. To reveal and access the objects within the array, you must select the Anonymous object on the Include tab. The Include tab displays the format of the JSON as TIBCO Cloud? Integration - Connect interprets it. Starting a flow with no source data for the Query Block.Using the Serialize Block to establish the format of the array_of_customer JSON output by selecting the objects on the Include tab. Errors display because there are no fields mapped on the fields tab, but for this scenario, no field mappings are required.Using a Fetch Block to retrieve Account records from a Sample CRM database.Using an Add Block to map Account fields to the correct array_of_customer JSON objects and add each customer record into the array.Using an Execute Block to write the output to the Agent log.Using a Fetch Block to deserialize the JSON. The mapper_input field on the Filter tab captures the JSON output generated by the Serialize Block and deserializes it based on the sample JSON in the Mapper Connection dialog.Using the For Each Child Block to retrieve one customer record at a time from the deserialized JSON.Using an Execute Block to write a message for each record to the Agent log. Working with HTTP This flow is a more complete scenario and demonstrates the following: Starting a flow with no source data for the Query Block.Using the Serialize Block to establish the format of the array_of_customerJSON output by selecting the objects on the Include tab. Errors display because there are no fields mapped on the fields tab, but for this scenario, no field mappings are required.Using a Fetch Block to retrieve Account records from a Sample CRM database.Using an Add Block to map Account fields to the correct JSON objects and add each Account record into the array.Using a Send Block with the POST HTTP verb to send the JSON array in an HTTP request. This Block uses Postman Echo to echo the HTTP request back to TIBCO Cloud? Integration - Connect.Using a Fetch Block to deserialize the JSON in the HTTP response. The mapper_input field on the Filter tab captures the JSON response from the Send POST Block and deserializes it based on the sample JSON in the Mapper Connection dialog.Using the For Each Child Block to retrieve one customer record at a time from the deserialized JSON.Using an Execute Block to write a message for each record to the Agent log. DISCLAIMER Copyright © 2022, TIBCO Software Inc. All rights reserved. No Support. You acknowledge that TIBCO will not provide any maintenance or support for this software. You have no right to receive any upgrades, patches, enhancements, bug fixes, new versions or new releases of the software. Internal Use Only License Grant. TIBCO hereby grants you a limited, non?transferable, non?exclusive license to use the software solely for your internal business purposes. The name of TIBCO Software Inc. may not be used to endorse or promote products derived from this software without specific prior written permission of TIBCO Software Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

In TIBCO Cloud? Integration - Connect, you can use the Text Connector to process information in text files. However, in cases where multiple text files exist in the same folder, the flow processes a single file and then ends. The next file is not processed until the flow is executed again either manually or on based on the app schedule. This can cause a delay when there are many inbound files to be processed. Using the TIBCO Scribe Online connector for Files resolves this issue by allowing you to Query a folder with multiple files, and move and rename files as they are processed without exiting the flow. These flows are very simple and do not get into details about mapping data to other systems. They only demonstrate what can be done with files and folders. Each Block in the flows has a brief description that explains the purpose of that Block. Prerequisites You can import the Sample App from the marketplace listing by searching for Samples for Files Connector and selecting Get. You will also need to Install the other prerequisite Connectors (if not installed already): Sample - CRM Connector and an associated Connection named SampleCRM with no spaces or special characters. On the Connection Configuration dialog set the Use Sample Data field to true to use the sample data distributed with the Connector.Tools Connector and an associated Connection named Tools.Files Connector and an associated Connection named Files.You will also need a Connect On-Premise Agent. Sample CRM Connector Note the following when using the Sample CRM Connector: A sample database is installed in the agent folder when the Connector is installed.If you have more than one Connect on-premise agent installed, there is a separate database for each agent. In this case, the database associated with the agent that runs an app using the Sample CRM Connection is the database that is updated. If you have multiple agents, you can expect the databases to be different over time.If you are using a Connect cloud agent, there is a separate database for each app that uses the Connect cloud agent. In this case, you can expect the database for each app to be different over time. Accessing Local Directories If you choose to store files and folders on your own computer or a server on your network, you must edit the FoldersAccess.txt file installed with the Connector. When files and folders are stored locally, TIBCO Cloud? Integration - Connect uses the FolderAccess.txt file to maintain the list of directories it is permitted to access. The TIBCO Scribe® Online Files Connector is limited to the directories in this list. Add directories to the default list as needed. Navigate to the FolderAccess.txt file in the ..\Scribe Software\TIBCO Scribe® Online Agent\Connectors\Scribe.Connector.Files\ folder on the computer where the connect on-premise agent is installed.Open the FolderAccess.txt file in a text editor, such as Notepad.Add a line in the FolderAccess.txt file for each directory path that contains text files. Directory paths can be absolute, relative to the folder where the agent is installed, or a network directory. List each folder on its own line, for example: C:\folder2 \\myserver\archive .\dataexchange NOTE: Microsoft does not support mapped drive names with Windows services. However, UNC path names are supported. For more information, see Services and Redirected Drives (Microsoft MSDN Library) Save and close the file before you configure any files or folders. If you have not added the locations, TIBCO Cloud? Integration - Connect generates errors when you try to preview data or test Connections. The Files Connector can access all sub-directories under any listed directories. NOTE: The Files Connector can access all sub-directories under any listed directories. Files Connector Sample Flows Setup (Run once) This flow configures a folder system needed to demonstrate the use-cases with the Files connector. This flow provides the following: Creating three folders: Inbound, Processing, and Archive.Creating a file with a header row in the Inbound folder.Retrieving records from a source data store, such as Microsoft Dynamics 365Appending those records as text records or lines of text to the file. Pre/Post Processing Sample This flow demonstrates the following: Querying a folder. In this case we query the Inbound folder.Moving a file to from the Inbound folder to the Processing folderProcessing the contents of the file.Moving the file from the Processing folder to an Archive folder and renaming it after processing is complete. Reading And Writing Entire Files This flow demonstrates the following: Mapping files stored locally to another Connection.Looking up Byte Array (binary file data) for a file.Mapping the file to a target data store.Querying or Fetching files and attachments from a source data store, such as Salesforce.com.Writing files or attachments to your local system. DISCLAIMER Copyright © 2021, TIBCO Software Inc. All rights reserved. No Support. You acknowledge that TIBCO will not provide any maintenance or support for this software. You have no right to receive any upgrades, patches, enhancements, bug fixes, new versions or new releases of the software. Internal Use Only License Grant. TIBCO hereby grants you a limited, non?transferable, non?exclusive license to use the software solely for your internal business purposes. The name of TIBCO Software Inc. may not be used to endorse or promote products derived from this software without specific prior written permission of TIBCO Software Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

In TIBCO Scribe Online or TIBCO Cloud Integration - Connect, as data is being processed by a Map/flow, you can use the results of one operation in a subsequent operation. However, in some cases, the operation results do not persist through the entire Map/flow. For example, operation results for operations within a Fetch Block do not persist outside of the Fetch Block. Using the TIBCO Scribe Online connector for Variables to set and retrieve variables in a Map/flow resolves this issue by storing and retrieving variables as key/value pairs within the execution of a flow. The stored value is retrievable at any point in the flow, regardless of the scope in which it was set. Variables are useful for concatenating strings, finding Min or Max values of numbers or dates, and setting a calculated variable for values that are used throughout the flow execution. Prerequisites You can import the Sample App from the marketplace listing by searching for Samples for Variables Connector and selecting Get. You will also need to Install the other prerequisite Connectors (if not installed already): Sample - CRM Connector and an associated Connection named SampleCRM with no spaces or special characters. On the Connection Configuration dialog set the Use Sample Data field to true to use the sample data distributed with the Connector. See the Sample CRM Connector section of this document.Tools Connector and an associated Connection named Tools.Variables Connector and an associated Connection named Variables. If Connection names do not match the names specified in the prerequisites, you will have to reassign the Connections in the Sample Flows after you import them. Sample CRM Connector Note the following when using the Sample CRM Connector: A sample database is installed in the agent folder when the Connector is installed.If you have more than one Connect on-premise agent installed, there is a separate database for each agent. In this case, the database associated with the agent that runs an app using the Sample CRM Connection is the database that is updated. If you have multiple agents, you can expect the databases to be different over time.If you are using a Connect cloud agent, there is a separate database for each app that uses the Connect cloud agent. In this case, you can expect the database for each app to be different over time. Sample Flow The example problem solved by the Sample Flow is a scenario where a company has duplicate Customer Account records in their database. The company needs to determine which Account record is the most recent and retain the Customer Number to perform an operation using that number later in the Flow. The attached Sample Flow file illustrates one way to find the Account record that was modified most recently and to set a variable for the associated Customer Number. That variable can be used later in the Flow to update the correct Account record or write that record to another data store or any other operation you might find necessary. The Flow is very simple and does not get into determining which records are duplicates. It only demonstrates the use of variables. Each Block in the Flow has a brief description that explains the purpose of that Block. In this flow there are two variables that are being set. The first is a DateVariable, MaxModifiedOn, that contains the modified on date of a record and the second is a StringVariable, CustomerNumber, that contains the Customer Number for the associated Account record. Each time an Account record is retrieved, the flow checks to see if the modified on date for the new record is higher than the prior record. If the date is higher, both the date variable and the Customer Number variable are updated. If the date is lower, the variables are not updated. The Customer Number variable is retrieved using a Lookup Block outside the Fetch Block. DISCLAIMER Copyright © 2021, TIBCO Software Inc. All rights reserved. No Support. You acknowledge that TIBCO will not provide any maintenance or support for this software. You have no right to receive any upgrades, patches, enhancements, bug fixes, new versions or new releases of the software. Internal Use Only License Grant. TIBCO hereby grants you a limited, non?transferable, non?exclusive license to use the software solely for your internal business purposes. The name of TIBCO Software Inc. may not be used to endorse or promote products derived from this software without specific prior written permission of TIBCO Software Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

In TIBCO Cloud? Integration - Connect, there is no mechanism for encoding and decoding information, adding custom messages to the agent log, or pausing a flow. In addition, the requirement of a Query Block can be limiting depending on what you are trying to accomplish. Using the Query Block with the Tools SelectOne entity only returns one record with a DateTime. By using the SelectOne entity to start the flow, you can use Fetch Blocks to create sub-queries. For example, if you wanted to integrate Accounts and Customers into a Microsoft SQL Server database, you could do that within two Fetch Blocks. You can use these flows to learn about Debug also. These simple flows attempt to demonstrate some of these concepts and how they can be achieved using the Tools Connector. Review the Block descriptions in the flows that explain the purpose of the associated Block. Prerequisites You can import the Sample App from the marketplace listing by searching for Samples for Tools Connector and selecting Get. You will also need to Install the other prerequisite Connectors (if not installed already): Sample - CRM Connector and an associated Connection named SampleCRM with no spaces or special characters. On the Connection Configuration dialog set the Use Sample Data field to true to use the sample data distributed with the Connector. See the Sample CRM Connector section below for more details.Tools Connector and an associated Connection named Tools.Variables Connector and an associated Connection named Variables. If Connection names do not match the names specified in the prerequisites, you will have to reassign the Connections in the Sample Flows after you import them. Sample CRM Connector Note the following when using the Sample CRM Connector: A sample database is installed in the agent folder when the Connector is installed.If you have more than one Connect on-premise agent installed, there is a separate database for each agent. In this case, the database associated with the agent that runs an app using the Sample CRM Connection is the database that is updated. If you have multiple agents, you can expect the databases to be different over time.If you are using a Connect cloud agent, there is a separate database for each app that uses the Connect cloud agent. In this case, you can expect the database for each app to be different over time. Change the way flows are processed This flow demonstrates the following: Starting a flow with no source data for the Query Block.Using Fetch Blocks to return and process different sets of data.Executing a Sleep timer to pause the flow. Add Custom Logging and Errors in a Flow This flow demonstrates the following: Mapping dynamic values to the agent logs.Mapping a dynamic value as a Fatal Error message.Mapping a dynamic value as a Record Error message. Note that these are not real errors they are just demonstrating error logging. Encoding and Converting Values This flow demonstrates the following: Converting a DateTime to UNIX/Epoch.Encoding a value to Base64.Decoding a Base64 value.Encoding a value to SHA1. Converting between a String and Byte Array This flow demonstrates the following: Creating a variable for storing a CSV object and populating it.Converting a string to a byte array.Converting a byte array to a string. DISCLAIMER Copyright © 2022, TIBCO Software Inc. All rights reserved. No Support. You acknowledge that TIBCO will not provide any maintenance or support for this software. You have no right to receive any upgrades, patches, enhancements, bug fixes, new versions or new releases of the software. Internal Use Only License Grant. TIBCO hereby grants you a limited, non?transferable, non?exclusive license to use the software solely for your internal business purposes. The name of TIBCO Software Inc. may not be used to endorse or promote products derived from this software without specific prior written permission of TIBCO Software Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

In TIBCO Cloud? Integration - Connect, the REST Web Services Connector configures API calls for you based on a Swagger specification but is limited to RESTful HTTP/API calls. You can use the TIBCO Scribe® Online Connector for HTTP to build your own HTTP requests. The flexibility of HTTP allows you to configure Uri, Verb, Query Parameters, Headers, and Content. Content can be hard-coded in a formula or configured with the TIBCO Scribe® Online Connector for Mapper. These simple flows attempt to demonstrate some of these concepts and how they can be achieved using the HTTP Connector. Review the Block descriptions in the flows that explain the purpose of the associated Block. Prerequisites You can import the Sample App from the marketplace listing by searching for Samples for HTTP Connector and selecting Get. You will also need to Install the other prerequisite Connectors (if not installed already): Sample - CRM Connector and an associated Connection named SampleCRM with no spaces or special characters. On the Connection Configuration dialog set the Use Sample Data field to true to use the sample data distributed with the Connector. See the Sample CRM Connector notes.Variables Connector and an associated Connection named Variables.Tools Connector and an associated Connection named Tools.HTTP Connector and an associated Connection named HTTP.Mapper Connector and an associated Connection named Mapper. If Connection names do not match the names specified in the prerequisites, you will have to reassign the Connections in the Sample Flows after you import them. Sample CRM Connector Note the following when using the Sample CRM Connector: A sample database is installed in the agent folder when the Connector is installed.If you have more than one Connect on-premise agent installed, there is a separate database for each agent. In this case, the database associated with the agent that runs an app using the Sample CRM Connection is the database that is updated. If you have multiple agents, you can expect the databases to be different over time.If you are using a Connect cloud agent, there is a separate database for each app that uses the Connect cloud agent. In this case, you can expect the database for each app to be different over time. Creating Requests by HTTP Verb Flow This flow demonstrates the following: Starting a flow with no source data for the Query Block.Using Send Blocks to send HTTP requests.Using Postman Echo to echo the entire HTTP request back to TIBCO Cloud? Integration - Connect.Recording that echoed response in the Agent log. Adding Request Details Flow This flow demonstrates the following: Adding query parameters by mapping the entire query in a formula field.Adding query parameters by selecting QueryParameters on the Include tab of the Send Block and using an Add Block for each parameter or Key Value pair.Adding headers by selecting Headers on the Include tab of the Send Block and using an Add Block for each header or Key Value pair.Adding cookies by selecting Cookies on the Include tab of the Send Block and using an Add Block for each cookie or Key Value pair.Using Postman Echo to echo each HTTP request back to TIBCO Cloud? Integration - Connect.Recording each echoed response in the Agent log. Configuring Body with Content Type Flow This flow provides examples for specific types of content and demonstrates the following: Using a string variable.Sending the value of the variable as content type plain text.Sending the value of the variable as content type XML.Sending the value of the variable as content type JSON.Using Postman Echo to echo each HTTP request back to TIBCO Cloud? Integration - Connect.Recording each echoed response in the Agent log. Best practice is to keep mappings to the Content field very simple. Complex formulas may generate errors. You can use the Mapper and Variables Connectors to create the Content value you want to send. Authenticating Requests Flow This flow demonstrates how to configure authorization and authentication for HTTP web service calls, as follows: Warning: Information stored in variables, such as Username and Password, is stored in plain text making the variable values visible to other TIBCO Cloud? Integration - Connect users. Using Basic Authentication. - Store Username and Password as variables. - Encode the Username and Password. - Use a Send Block with Headers selected on the Include tab. - Use an Add Block to send a header with a Key Value pair containing the authentication type and the encoded output. Using Token Authentication. - Store ClientID and ClientSecret as variables. - Use a Send Block to send the authentication information. - Parse the token in the response to the Send Block. This step is not configured, but is represented by a Comment Block. - Store the token as a variable. - Use a Send Block with Headers selected on the Include tab. - Use an Add Block to send a header with a Key Value pair containing the token variable. Using HMAC Signature. - Store Access Key, HMAC Key, date stamp, and a string value as variables. - Use an Execute Block to generate an HMAC256 Hash for a signature. - Use a Send Block with Headers selected on the Include tab. - Use an Add Block to send a header with a Key Value pair containing the authentication type and the encoded output. Using Postman Echo to echo each HTTP request back to TIBCO Cloud? Integration - Connect.Recording each echoed response in the Agent log. Response Status Codes Flow Some APIs may return more detailed status codes that can be used to modify flow behavior. For example, with an HTTP POST, a 201 code could indicate that the operation created a new record instead of updating an existing record. Review the documentation for the API you are accessing to determine if any of these codes would be useful to you. The Response Status Codes flow demonstrates the following: Sending a request that returns a status code. In this example, the code returned is 201.Using an If/Else block to decide what to do if the status code returned is a 201 and what to do if it is any other code.Writing to the Agent log when a 201 status code is returned. HTTP Messages Flow This flow demonstrates the following: Support for Message flowsSupport for any string data, such as XML, JSON, or CSV.Responses to requests return a GUID (RequestID) that can be used in the flow. DISCLAIMER Copyright © 2022, TIBCO Software Inc. All rights reserved. No Support. You acknowledge that TIBCO will not provide any maintenance or support for this software. You have no right to receive any upgrades, patches, enhancements, bug fixes, new versions or new releases of the software. Internal Use Only License Grant. TIBCO hereby grants you a limited, non?transferable, non?exclusive license to use the software solely for your internal business purposes. The name of TIBCO Software Inc. may not be used to endorse or promote products derived from this software without specific prior written permission of TIBCO Software Inc. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

To access the End User License Agreement install both the TIBCO Scribe Online Connector and a TIBCO Cloud Integration - Connect on-premise agent. The End User License Agreement is included in the Connectors folder under the agent installation folder. The default location for installed Connectors is: C:\Program Files (x86)\Scribe Software\TIBCO Scribe® Online Agent If you have any questions please reach out to the Integration Product Management team - integration-pm@tibco.com. You can also contact the company listed in the Distributed By field by using the links available in the Marketplace or using the Request button.

For additional information see: TIBCO Cloud Integration Release Notes TIBCO Cloud Integration - Connect Known Issues TIBCO Scribe Online Connector Release Notes New And Noteworthy TIBCO Cloud Integration - Connect API Added a new parameter, byReference, to the POST /v1/orgs/{orgId}/solutions/{solutionId}/cloneAsync method. If set to ?true?, the source App and any associated cloned target Apps share resources, such as Flows. This improves performance when cloning. However, neither the source App nor the target Apps can be edited. See Copy Or Clone A Solution Using Shared Resources for more information. https://dev.scribesoft.com/en/main/how/copy-solution-byref.htm (SCCORE-7751)Added a new field to the App model to indicate whether or not a App has been cloned and is sharing resources. The new field and possible values are as follows: (IPAS-19950) solutionCloneType solution ? App does not share resources with any other App. solutionByReferenceSource ? Source App that has been copied to one or more target Apps and shares resources with those Apps, such as Flows.solutionByReferenceTarget ? Target App copied from a source App and shares resources with the source App, such as Flows.

For additional information see: TIBCO Cloud Integration Release Notes TIBCO Cloud Integration - Connect Known Issues TIBCO Scribe Online Connector Release Notes New And Noteworthy There are no new features in this release. Closed Issues SCCORE-8065 After a Connector release or in cases where Cloud Agents are moved to other servers for load balancing, Connection details sometimes do not display in the Connection dialog of an existing connection. (Case # 02091495, 02091918, 02092834, 02093791, 02095721, 02095880)