TIBCO Scribe® Online 2018 Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. See TIBCO Scribe® Online Current Known Issues for detailed information on Known Issues. See Release Notes TIBCO Scribe® Online Developer Portal for release notes associated with the API and the SDK.
Note: Close your browser and reopen it after the upgrade to ensure that the TIBCO Scribe® Online User Interface displays correctly with no errors.
Version 2.0.3 Release
TIBCO Scribe® released the Version 2.0.3 update to TIBCO Scribe® Online on October 19, 2018.
New And Noteworthy
Agent
IMPORTANT NOTE: We are updating the TIBCO Scribe® Online Agents to leverage Microsoft .NET Framework 4.6 in this release. Customers using On-Premise Agents need to ensure that the .NET version for any computers running an On-Premise Agent are upgraded to .NET 4.6 or higher. If you only use Cloud Agents they will automatically be updated and no action is required on your part.
Additional information can be found on the TIBCO Community.
Closed Issues
Connectors
8971 / 66932
Modified the Connection dialog to allow you to choose an Agent for testing the connection before selecting the Connector you are configuring. This alleviates a problem with the Oracle Database Connector. Previously, when configuring a connection to Oracle Database, the first Agent alphabetically was selected automatically and the Connection UI failed to load unless the machine hosting the Agent had the Oracle Client installed. Allowing you to select the correct Agent before selecting the Connector ensures that the Connection UI loads correctly. (Case # 60842, 65345, 65368, 65678, 66168)
Execution History
66046 / 66588 / 66844
Could not retrieve errors for Replication Services Solutions and Event Solutions containing Request/Reply Maps from either the API or the UI. From the API, the following error was generated: (Case # 65209)
Export with the specified id was not found.
Solutions
71264
Event Solutions containing Request/Reply Maps could not process messages that contained arrays or objects. (Case # 67341)
Version 2.0.1 Release
Released August 1, 2018.
New And Noteworthy
This update to TIBCO Scribe® Online includes the following changes:
Maps
Map revisions are no longer created when you save a Map that has had no changes since the last time it was saved. For example, if you open a Map and select OK to close it without any modifications, no revision is generated. (66915)
Closed Issues
Agents
64060 / 65087
In environments with a large amount of Request/Reply traffic, sometimes Agent capacity was exceeded causing Agents to fail. (Case # 64715, 65103, 66649)
64421 /64274
In some cases, Agents had to be restarted manually after an update due to a high volume of requests from Agents to the platform. Agents now wait until the platform responds instead of timing out.
Solutions
64577 / 64906 / 65133 / 66208 / 66209 / 66241
Some Solution statuses remained in a Stopping or In Progress state and did not return to the correct Idle state when complete. (Case # 64825, 64878, 64908, 64910, 65101, 65110, 65167, 65238, 65244, 65252, 65270, 65312, 65405, 65489, 65496, 65511, 65526, 65551, 65633, 65669, 65687, 65780, 65834, 65883, 65889, 66368)
Maps
64580 / 64736 / 66236
When metadata was modified and reset for a Connection in a Request/Reply Map, validation errors were generated, but the Fields tab in the target operation Block did not display the unmapped fields that needed to be remapped. (Case # 65161)
65960 / 66130 / 66240
After resetting metadata for a Connection, some queries generated a Query <entityname> is null error. (Case # 63418, 64344, 61433, 65531, 65559, 65852)
Blocks
66238 / 64934
Pasting a value into a target field in a Block associated with hierarchical data, such as CreateWith, sometimes populated the wrong field. (Case # 65830, 66218)
April 6, 2018 Release
In this release of TIBCO Scribe® Online we are introducing Map Revisions. Whenever a Map is saved a revision of the Map is created. You can go back to a prior revision at any time, export a Map revision, or import a Map revision into a Solution.
TIBCO Scribe® is making this feature available to every user as part of a Preview to gather feedback before making it available only for specific subscriptions. You are welcome to use it and we encourage feedback on our TIBCO Community. After our next major release, you will retain this feature if you have purchased our Professional Tier License.
New And Noteworthy
This update to TIBCO Scribe® Online includes the following enhancements and addressed issues:
Platform
Added the ability to generate an OAS 2.0 document from a Request/Reply Map endpoint, all Request/Reply Maps in a Solution, or all Request/Reply Maps in an Organization. For more information on OAS 2.0 refer to the OAS 2.0 Specification. (59102, 59105, 59109) For more information see, Using TIBCO Scribe® Online OAS Support With Microsoft Flow and Generate An OAS Document For Request/Reply Maps.
Limit the use of the warning message displayed when you exit TIBCO Scribe® Online to the Map edit page instead of all pages. (54927)
Requires that TLS 1.1 be enabled in browser settings. In addition, API endpoints like Request/Reply and Message Map will no longer support TLS 1.0. (56754)
Corrected display issues for the latest versions of Chrome where data was wrapping when displayed in a grid format. (63182)
Added the following Agent and Solution statuses to both the User Interface and the TIBCO Scribe® API to provide more detail about the Agent’s current status: (5396, 19634)
- Waiting To Update Agent - Agent completes any Solution executions that are running and updates Execution History for running Solutions, but does not start any Solutions or contact TIBCO Scribe® Online. Agent then goes to Agent Updating status.
- Waiting To Update Connector - Agent completes any Solution executions that are running and updates Execution History for running Solutions, but does not start any new Solutions or contact TIBCO Scribe® Online. Agent then goes to Updating Connector status.
- Updating Connector – Agent is installing Connector updates.
- Waiting to restart, user requested - A user has requested an Agent restart. Depending on the type of restart selected by the user, the Agent restarts immediately or after all running Solutions are complete and Execution History has been updated.
- Waiting to restart, memory limit reached - TIBCO Scribe® Online detects when an Agent's memory limits are being exceeded and requests an Agent restart. Agent completes any running Solutions and updates Execution History for those Solutions before restarting.
- Restarting – Agent is restarting.
IMPORTANT NOTE: If you are accessing Agent or Solution Status information via the API, make sure to update your application to accommodate the new Status types. If you receive an unexpected Status your application may not display the text correctly.
Agents
Added Request Agent Logs option to the Gear menu on the Agents page and Agents Dashboard widget to create and download a ZIP file containing log files for the selected On-Premise Agent. (58638)
Maps
Multiple revisions of a Map can be stored and retrieved, each with a revision number, comment, date, and the user name of the user who made the change. From the Revisions dialog you can revert the current working copy of a Map to the selected revision. (17233, 57501)
Added an optional Comment field at the bottom of the Map workspace for information about a Map revision. Each time a Map is saved a revision of that Map is stored with a Comment, if one has been entered. (60633)
A specific Map revision can be exported from the Gear menu on the Map Revisions dialog. (60686)
When a Map is imported, the revision comment Map Imported is automatically added to that revision of the Map along with a revision number, date, and user name of the user who imported the Map. (60685)
IMPORTANT NOTE: Map Revisions are part of a Preview and will only be generally available for a limited time. After the next major release, only Professional Tier Licenses will have access to Map Revisions.
Closed Issues
Agents
8413
The Agent service reported a Stopping status for long periods of time, preventing Solutions from executing. (Case # 77235)
57175
Improved managing Agent restart when excessive memory is being used and provided a more accurate Agent status. (Case # 62907)
60562
Enhanced the Agent's ability to handle local network connectivity issues, which could have prevented execution history from being sent to the platform. (Case # 63593, 63710, 63728, 63808, 64010, 64049, 64071, 64091, 64104, 64112, 64128, 64167, 64178, 64209, 64216, 64244)
Connectors
54820
When more than one Map configured with the Text Connector used the same text file as a source, and one Map took a long time to process, subsequent Maps failed. (Case # 60984)
55305
Custom Connectors displayed the Connector name and the phrase Distributed By Scribe Software Corporation in the Connector Type field of the Connection dialog, instead of just the Connector name.
58426
Changed the Bulk Batch Size and Bulk Concurrent Calls field labels on the connection user interface for the Microsoft Dynamics 365 / CRM Connector to Maximum Batch Size and Maximum Batch Threads to more clearly indicate their function.
58840
When using the Text Connector with a Cloud source or target, such as DropBox or OneDrive, the Connector was making too many requests and was reaching the API rate limit, which generated errors similar to the following: App is making too many requests and is being rate limited. (Case # 61648)
62079
Added a Message Format drop-down to the Connection dialog for the Amazon S3 Connector to allow users to select between standard JSON formatting and Redshift compliant JSON.
Connections
29262 / 57134
Disabled autocomplete for credentials on the Connection dialogs to prevent erroneous credentials from being entered.
36571
Occasionally a Target Text Connection failed to load operation Blocks or metadata, and TIBCO Scribe® Online did not try to load these objects again. (Case # 55818)
55139
Enhanced the timeout error message on the Connection dialog for OAuth Connectors, such as HubSpot, to provide a more user-friendly message. (Case # 62089)
57667
Improved error message displayed when attempting to configure a Connection using a Cloud Agent for a Connector that only supports the On-Premise Agent. The error message now says “This Connector requires an On-Premise Agent. Please add an On-Premise Agent to configure.” Instead of saying that the connection properties could not be displayed.
Solutions
26915
Solution status displayed as OnDemand during a Debug session instead of Starting or InProgress.
27624
Reprocessing failed records for an Event Solution Execution caused TIBCO Scribe® Online to attempt to reprocess all records in the event message. When the reprocessing execution encountered a record that was successful in the prior execution, TIBCO Scribe® Online generated Operation failed errors, and the reprocessing execution stopped. (Case # 77189)
35622
Solution schedule was lost when the Solution was disabled and then reenabled.
35954
Changing a Solution schedule to On Demand while the Solution status was “In Progress” changed the Solution status to "Preparing" and enabled the Run button allowing you to select Run when the Solution was already running.
37752 / 54926
Attempting to reprocess record errors from Message Map executions resulted in an error similar to the following, even when all fields were included in the failed record:
Error description: Operation failed. Label: Create Customers, Name: CustomersCreate, Message: Exception Type : ApplicationException
Message : Field Account.Name, used in current map is not a part of the failed record's data.
46636
When running a Solution from the Solution Edit page using the Run button, the Run button changes to Stop to allow you to stop the Solution execution. Occasionally the Stop button did not revert back to Run when the Solution execution finished.
48437
When running a Solution from the Solution Edit page sometimes Execution History status did not update and remained at In Progress.
57414
Radio buttons used to schedule a Solution did not display on some Apple devices. (Case # 62997, 60937, 60834)
57634
Scheduled Solutions now run with the last known configuration if the Agent cannot contact the TIBCO Scribe® Online API to check for changes to a Solution, instead of not running at all. (Case # 62535)
58066 / 58128
When an Agent running a Solution experienced network connectivity issues, the TIBCO Scribe® Online UI did not accurately reflect that the Solution was still running on the Agent.
58419
In some Organizations, Solution status was not updating from Preparing to Idle. (Case # 63315)
Maps
35199 / 57680
The first time you open an imported Map, Connections must be reassigned either automatically by matching Connection names or manually and then, TIBCO Scribe® Online must load metadata. In any scenario where metadata took a long time to load, such as reassigning Connections or resetting metadata, TIBCO Scribe® Online attempted to validate the Map before metadata was completely loaded and displayed a long list of errors in the Errors and Warnings tab.
39450
Renaming a Connection from within a Map did not update field mappings and formulas using that name, causing errors if the Map were to run.
39610
Field names configured in the Reply Block of a Request Reply Map were sent out in the reply in lower case even if they were configured in capital letters in the Reply Block Fields tab.
48646
Occasionally, if there was a brief loss of connectivity, a new Map was not listed immediately in the Map list on the Solution Edit page.
59826
Map occasionally generated an error message when there was no real error. (Case # 64325)
Lookup Tables
26030
Changes made to values in a Lookup Table that had already been used by a Solution sometimes resulted in both the old values and the new values being returned because the information was cached by the Agent. (Cases # 39530, 56921, 57563, 57702, 58150, 58184,58363, 61984, 62170, 84118)
You may have seen an error message similar to the following:
Error title: Error in mapping '<fieldname> ' for Operation 'Update'
Error description: Operation failed. Label: Update/Insert pricelevel, Name: pricelevelUpdateInsert, Message: Exception Type : InvalidOperationException
Message : Multiple values found in Value1 for lookup value 'd7c4df42-ed3d-e011-86c5-1cc1dee8da72' in Lookup Table '<table_name>'.
StackTrace : at Scribe.Core.Processor.ProcessSupport.LookupTableValueGeneric(String tableName, String value, Boolean lookupValue1, Object defaultValue, Boolean nullDefaultOk)
Debug
37182
When debugging a Map, mapping errors were not displayed in the Errors tab nor did the Debug process stop on the Block where the error occurred. (Case # 61588)
Blocks
18506
The Net Change option, Process only records created or update since last run, was not disabled if you removed a Query Block from a Map and added a Native Query Block causing an "Object reference not set to an instance of an object" error. (Case # 81371)
39213
Query Blocks configured with an outer join on related entities returned no records if the Map did not include field mapping for a related entity field. (Case # 55847)
Execution History
38642
Record errors referenced an incorrectly mapped field when the issue was caused by a formula in the Matching Criteria for a Block. (Case # 56735)
58097
Execution History export files did not include null field values. (Case # 59233)
59116
In some cases, record errors were not displaying in the Execution History UI. (Case # 63564)
January 19, 2018 Release
Note: After this update is released, remember to clear your browser cache. This release includes improvements in how TIBCO Scribe® Online interacts with the browser cache. Future releases will only require that you close your browser and log into TIBCO Scribe® Online again to access new features. (54661)
New And Noteworthy
Replication Solutions
With this release, TIBCO Scribe® Online Replication Solutions can take advantage of Bulk Processing if the associated target Connectors support this functionality, which now includes the SQL and MySQL Connectors. This feature speeds up the performance of both the initial replication and subsequent synchronizations. Each time a Replication Solution is created or updated, metadata is reset for the source and target Connections.
Note: If the Connection being used in the Replication Solution is new and has never been used in an Integration Solution, metadata is reset for the Replication Solution, but not for any Integration Solutions created later. (54918)
Workaround: Reset metadata manually either from the Gear menu in the Connections page, or from the Gear menu for the Connection in the Integration Solution Map.
As part of this new feature set, we have made great strides to improve how Replication Services (RS) notifies users about any issues processing data. Previously there was no mechanism to properly report some types of issues to the TIBCO Scribe® Online system. At the same time we also addressed new and existing issues specific to the Connectors being used. Any defects associated with a specific Connector are listed in the Release Notes for that Connector.
If the target Connection in the Replication Solution supports Bulk operations, then Batch Processing is used automatically when the Solution executes to enhance performance. (50472)
Note: To enable bulk processing for existing Replication Solutions, make a change to the Solution and save it. The change can be as simple as modifying the description.
When a record error is encountered, the Replication Solution skips that record and continues to execute. (50472)
Note: To reprocess records with errors, modify the data in the source again. This updates the datetime field forcing the record to be replicated in the target datastore the next time the Replication Solution executes. If you do not modify source data, the records with errors are skipped during subsequent Replication Solution executions.
Metadata is automatically reset for both source and target Connections any time a Replication Solution is created or modified to ensure that any schema changes or new entities are available for replication, which may cause a brief delay when opening the Solution. (51681)
Enhanced error handling for exceptions to generate a Fatal Error and provide more detailed information in Execution History. (52935)
Closed Issues
Replication Solutions
51972
In some cases, entity descriptions did not display on the Replication Solution Selected Entities page.
Execution History
54921 / 54979
Exporting errors from the Execution History Details dialog was not displaying the Save dialog, preventing completion of the export. (Case # 61981)
Connectors
54821 /54839
The Microsoft Dynamics 365 / CRM Connection dialog did not display the Home Realm URL field when the Partner-Hosted (IFD) Deployment Type was selected. (Case # 62027)
55379 / 55382
When using the Text Connector some users could not create connections to Dropbox or OneDrive accounts. (Case # 62147)
55973 / 56046
When a custom delimiter was selected on the Entities tab of the Text Connector dialog, the additional field to enter the delimiter did not display. (Case # 62408)
