Note: All release notes for TIBCO Scribe® Online and associated Connectors are included in the TIBCO Scribe® Online Help on the Release Notes page.

TIBCO released an update to TIBCO Scribe® Online on April 6, 2018.

Feature Preview

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.

This feature is 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 here on our Community.

Enhancements

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 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 - 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.
 

API

• Added the PUT /v1/orgs/{orgId}/connectors/{connectorId}/version endpoint to modify the locked/unlocked state of a Connector version. If locked, the Connector version on the Agents in that Organization is not automatically upgraded when Scribe releases a new version of the Connector. (61587)

• Added the GET /v1/orgs/{orgId}/connectors/{connectorId}/version endpoint to return the locked state and version of the selected Connector. (57826)
• Added the POST /v1/orgs/{orgId}/solutions/{solutionId}/maps/{mapId}/revert endpoint to revert a Map to a prior revision. (17233,57500)
• Added the GET /v1/orgs/{orgId}/solutions/{solutionId}/maps/{mapId}/revisions endpoint to return a list of revisions for a Map. Revisions are returned in descending order by revision number, which means that the latest revision is returned first. (57504)
• Added a revision parameter to the following endpoints to return or export a specific revision of a Map based on the revision number: (57498, 60686)
  • GET /v1/orgs/{orgId}/solutions/{solutionId}/maps/{mapId}
  • POST /v1/orgs/{orgId}/solutions/{solutionId}/maps/export
• Added an optional comment parameter for Map revisions to the following endpoints: (17233, 60633)
  • POST /v1/orgs/{orgId}/solutions/{solutionId}/maps/advanced
  • PUT /v1/orgs/{orgId}/solutions/{solutionId}/maps/advanced/{mapId}
• Removed API endpoints for Basic Maps from the API Swagger page since this map type is no longer supported in Scribe Online. (57524)
• Enhanced the GET /v1/marketplace/connectors method to provide Connector Version information for all stored versions of a Connector including Hotfixes created after the last General Release version. (57825)
• Enhanced the following Agent endpoints to return or save the ID and Version number of any installed Connectors: (57830)
  • GET /v1/orgs/{orgId}/agents
  • GET /v1/orgs/{orgId}/agents/{id}
  • PUT /v1/orgs/{orgId}/agents/{id}

Addressed Issues
 

Agents

• The Agent service reported a Stopping status for long periods of time, preventing Solutions from executing. (8413 / Case # 77235)
• Improved managing Agent restart when excessive memory is being used and provided a more accurate Agent status. (57175 / Case # 62907)
• Enhanced the Agent's ability to handle local network connectivity issues, which could have prevented execution history from being sent to the platform. (60562 / Case # 63593, 63710, 63728, 63808, 64010, 64049, 64071, 64091, 64104, 64112, 64128, 64167, 64178, 64209, 64216, 64244)

 

Connectors

• 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. (55305)
• 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. (54820 / Case # 60984)
• 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. (58840 / Case # 61648)
• 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. (58426)
• 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. (62079)

 

Connections

• Occasionally a Target Text Connection failed to load operation Blocks or metadata, and TIBCO Scribe® Online did not try to load these objects again. (36571 / Case # 55818)
• Enhanced the timeout error message on the Connection dialog for OAuth Connectors, such as HubSpot, to provide a more user-friendly message. (55139, / Case # 62089)
• Disabled autocomplete for credentials on the Connection dialogs to prevent erroneous credentials from being entered. (29262, 57134)
• 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. (57667)

 

Solutions

• Solution status displayed as OnDemand during a Debug session instead of Starting or InProgress. (26915)
• Reprocessing failed records for an Event Solution Execution caused 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, Scribe generated Operation failed errors, and the reprocessing execution stopped. (27624 / Case # 77189)
• Solution schedule was lost when the Solution was disabled and then re-enabled. (35622)
• 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. (46636)
• 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: (37752, 54926)

• 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. (57634 / Case # 62535)
• 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. (58066, 58128)
• When running a Solution from the Solution Edit page sometimes Execution History status did not update and remained at In Progress. (48437)
• 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. (35954)
• In some Organizations, Solution status was not updating from Preparing to Idle. (58419 / Case # 63315)
• Radio buttons used to schedule a Solution did not display on some Apple devices. (57414 / Case # 62997, 60937, 60834)

 

Maps

• 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. (39610)
• 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, 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. (D35199, 57680)
• 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. (D39450)
• 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. (48646)
• Map occasionally generated an error message when there was no real error. (59826 / Case # 64325)

 

Lookup Tables

• 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. (26030 / Cases # 39530, 56921, 57563, 57702, 58150, 58184,58363, 61984, 62170, 84118)

 

Debug

• 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. (37182 / Case # 61588)

 

Blocks

• 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. (18506 / Case # 81371)
• 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. (39213 / Case # 55847)

 

Execution History

• Record errors referenced an incorrectly mapped field when the issue was caused by a formula in the Matching Criteria for a Block. (38642 / Case # 56735)
• Execution History export files did not include null field values. (58097 / Case # 59233)
• In some cases, record errors were not displaying in the Execution History UI. (59116 / Case # 63564)

 
For additional information, see the TIBCO Scribe Online Help.

To receive release announcements for Scribe Online, see Sign Up For Scribe Product Release Notifications.
 
 

TIBCO Scribe® Online April 6, 2018 update released. This article provides information about the contents of that release.