Release 10.16

What's New

Error Management for Salesforce Listeners

Listeners functionality is introduced with an error management mechanism. As an integration developer, you can now configure an error call-back service and be notified when an error occurs with the Salesforce listener communication.

You can configure a FlowService to address how a listener must behave in case of errors. A new drop-down menu, Select ErrorCallBackFlowService name, has been added under the Event tab in the Add Listeners wizard. From this drop-down menu, you can either create a new FlowService or choose an existing FlowService that defines the listener behavior when an error occurs.

See this tutorial for more information.

Runtime Status of Connector Listeners

You can now view the runtime status of a connector listener from the Listeners screen. A new column Status is introduced to display the runtime status for each listener.

• If the Status is Active, it indicates that the configured cloud connection for a connector is successful and active.
• If the Status is Disabled, it indicates that the configured cloud connection for a connector is inactive.
• If the Status is Suspended, it indicates that the configured cloud connector listener was successfully enabled, but the subscription is currently inactive. To get a detailed explanation of the error status, you can click on the Suspended status in the Status column.
  Note: If the SAP® ERP Connector listener status is Suspended, it indicates that an error occured during enabling or disabling the listener.

Listener Improvements

Improvements were made in listeners to:

• Ignore duplicate trigger listener entries in Workflows.
• Avoid multiple executions and intermittent lack of response from listeners.

Information related to Hybrid Connectivity

If you are using on-premises Integration Server v10.15 for hybrid connectivity, and if your hybrid connectivity uses two-way SSL, ensure that you have installed IS_10.15_WmCloud_Fix1 in your environment.

In this release, on-premises Integration Server 10.3 or higher versions with the latest on-premises Integration Server and Universal Messaging fixes are supported for hybrid connectivity.

Size Limit for Hybrid Messages

The payload size limit for hybrid messages has been modified. Now, the maximum size limit for hybrid messages that can be transported between on-premises webMethods Integration Server and webMethods.io Integration is up to 25 MB.

Hybrid Integration Architecture Improvements

Routing mechanism of the hybrid integration solution is enhanced. In the hybrid integration solution, webMethods.io Integration uses Universal Messaging (UM) to route messages to the on-premises applications and vice-versa. While configuring the connectivity (routing) settings, currently the host name is provided in the format, um.int-aws-de.webmethods.io.

In the new approach, the host name format has been changed to *.um.int-aws-de.webmethods.io, where * indicates the tenant-specific identifier.

Example:

• Old UM URL: nhps://um.int-aws-de.webmethods.io:443//stage00-um-1397192613 -1012/
• New UM URL: nhps://tenant subdomain-ade43fe.um.int-aws-de.webmethods.io:443//tenant subdomain/, where ade43fe is a unique number generated by the system to identify the Integration Server.

Ensure that you allow the following domains in your firewall or proxy settings:

Note: For the list of allowed IPs, see the webMethods.io Integration section under Software AG Regions.

To migrate to the new hybrid routing mechanism, it is recommended to perform Update Settings and restart the on-premises Integration Server. On-premises Integration Server remains connected to the old Universal Messaging URL unless the settings are updated and the Integration Server is restarted.

With this feature, cloud hybrid communication traceability is improved.

Enhanced rate limits for manually run, trigger-enabled, and async webhook-enabled workflows

Under paid plans, you can now send execution requests for up to 15000 workflows within a minute. Earlier this was 1500. The first 15000 requests are processed, while the rest of the requests are Rejected.

Under trial/unpaid plans, you can now send execution requests for up to 300 workflows within a minute. Earlier this was 30. The first 300 requests are processed, while the rest of the requests are Rejected.

Such workflows are indicated with a Failed status against them in the Workflow Execution section of the Monitor page.

Execution Settings Enhancements

The seven day restriction on the Maintain workflow execution logs when executed via webhook or trigger checkbox under Execution settings is removed.
Earlier, when you selected the Maintain workflow execution logs when executed via webhook or trigger checkbox under Execution settings, it was auto-disabled after seven days. From this release, when you select this checkbox, it stays selected until you deselect it manually.

New APIs

New APIs have been introduced in the following domains:

• Account APIs: Allows you to retrieve, delete, and switch accounts from the workflow connector and also update the account configuration.
• Metrics APIs: Allows you to retrieve the execution summary and logs.
• Reference APIs: Allows you to retrieve, add, and update the reference data.

Monitor Page Enhancements

The following enhancements are now available in the Workflow Execution and FlowService Execution features:

• You can now directly retrieve a list of all successful, failed, or pending Workflow or FlowService executions from the Execution Status filter. Earlier, you had to choose Project(s) and Workflow(s)/FlowService(s), before selecting execution status(es) to retrieve the execution data.
  
  
  


• You can now set the limit of the number of items to be displayed per page by clicking on the Items per page drop-down menu located at the bottom of the Executions table. By default, 50 items are displayed on a single page. The maximum page size is restricted to 150 items.
  
  
  


• The execution listing section in the Monitor page is enhanced to provide two new options for Restart and Resume under the newly added Actions column. Using these options, you can restart and resume Workflow and FlowServices executions from the main execution listing page.
  
  
  
  
  
  
  
  
• You can now select one or multiple failed Workflow or failed/successful FlowService executions to restart in a single click. To do this, in the Executions table, select the checkbox beside the name of failed workflows or failed/successful FlowServices and click the Restart button. The checkboxes will be enabled only if the restart capability is enabled and also if the Enable FlowService to be restarted option is checked on the Overview page of the FlowService. In earlier releases, you could restart only one Workflow/FlowService execution at a time.
  
  
  


• In the Executions table, a new label named Restarted is introduced in the Status column . This label indicates that the corresponding failed workflow execution or failed/successful FlowService execution is restarted successfully.
  
  
  


• The chart view that shows the graphical representation of Workflow/FlowService executions located in the Workflow Execution and FlowService Execution page is now named as Overview. For better readability, you can now expand or collapse the Overview section by clicking the down arrow located next to Overview.
  
  
  


• FlowService Execution Results for new tenants are now retained for a period of seven days.
  

Monitoring SAP® ERP Performance

You can now monitor the SAP® ERP performance, the SAP® response time summary, query requests, and query components from the Monitor page.

Monitoring SAP® ERP Connection Pools

You can now monitor the SAP® ERP repository connection pools, the SAP® ERP client connections, and the listener status from the Monitor page.

New SAP® ERP Built-In Service

The new SAP® ERP built-in service createTIDOffline has been introduced in this release.
createTIDOffline allows you to obtain a transaction ID (TID; which is a GUID) that conforms to the format of SAP TIDs even when not connected to a SAP system. The transaction ID is based on a randomly created UUID Version 4.

FlowService Enhancements

Following improvements have been made in FlowServices for ease of use:

• FlowServices are made available by default for all tenants. Earlier, you needed to contact Software AG to enable FlowServices for your tenants.

• The Transform Pipeline panel is enhanced with the Expand All and Collapse All buttons. Using these buttons you can easily expand and collapse all nodes nested within another in a single click instead of navigating to each node.
  
  
  

• The Context ID details are displayed in the FlowService Execution page if a FlowService is created with Context ID. Earlier, the Context ID details were not displayed.
  
  
  

• The Picklist field in the Define input and output fields page is enhanced for better ease of use. The Add and Delete buttons are provided for each list item for adding or deleting the corresponding item. To modify an item, you can double-click the item and update with a new value.
  
  Additionally, the Allow other values checkbox is provided under the Picklist field. If selected, you can enter new values while providing inputs during runtime. Otherwise, you can select only from the list provided in the Define input and output fields page.
  
  
  
  Earlier, an Untitled entry got added by default and to delete it, you had to click Edit, select the item, and delete it. The up and down arrows are no longer available to reposition the items.

• Service names are now displayed correctly across the Pipeline panel. Earlier, the name in the step and name in the Input and Output column headers were not the same.
  
  
  

• The Set Value dialog is enhanced with the Copy and Paste buttons and a read-only custom text area. By default, the normal text area is displayed for you to provide values. If the number of character limit exceeds, then the read-only text area with Copy and Paste buttons is displayed.
  Earlier, when the character limit exceeded, the Set Value dialog box did not respond and the FlowService failed.
  
  
  

• FlowServices now support the String Table, Date, and Character datatypes in addition to the existing datatypes.

• The Cancel button is added in the New Reference Data wizard for canceling the action at any time.

• The messages displayed during export are updated to provide additional information related to the components that are not exported or published.

• You can now select multiple fields by pressing a Ctrl key in the Define input and output fields page. Additionally, you can perform Cut, Copy, Paste, Duplicate, and Delete operations.

• The Clear All option is available for the transform step in the pipeline panel. You can clear the parameter values with a single click instead of clearing each parameter.
  Earlier, the Clear All option was not applicable for the transform step.

• A new option Add Document Type is provided for the Document reference option in the Define input and output fields page. On selecting the Add Document Type option, you are redirected to the Configurations page where you can add and define new document types in a new window. After saving the document types, the new document type is automatically added in the Define input and output fields page.
  Earlier, you had to first add document types in the Configuration page before defining the input or output fields in the Define input and output fields page. With this option, you can now add and define new document types while defining the input or output fields.
  
  
  

• A new option emptyString is added in the Case statement to verify if the input string is empty.
  
  

• A new option Isempty is added in Expression Editor to verify if the input string is empty.
  
  

Support for Caching in FlowServices

Caching is added for FlowServices to store the results of successfully run FlowServices for a specified period. When you enable the Caching feature for any FlowService, webMethods.io Integration stores the results of the invoked FlowService. Next time if the FlowService is run with the same input values, webMethods.io Integration returns the cached results from the previous invocation and does not run the FlowService again. By using the Caching feature, you can improve the performance of FlowServices by improving the response time.

Caching is not available by default for a tenant. To enable this capability, contact Software AG Global Support.

The Cache settings dialog box is added to enable and configure caching. You can access the dialog box by using the Settings option from the FlowServices page.

Further, you can clear the cache for any FlowService using the Clear cache option.

Support Connectivity with Self-hosted Universal Messaging Servers from JMS connector

You can now publish and subscribe messages to publicly accessible self-hosted Universal Messaging servers. This option allows you to leverage your existing messaging system-based solutions to integrate with webMethods.io Integration. The JMS connector’s Add account wizard has been updated with new settings to support this connectivity.

Support for Reusing Previous FlowService Configurations and Parameter Values during Redeployment

You can now use the existing accounts configured for a FlowService during redeployment. This eliminates the need to manually reconfigure the FlowService accounts during each redeployment. 

Moreover, you can now use the previously configured values for project parameters during redeployment. This eliminates the need to manually provide values for project parameters during each deployment. 

These enhancements will reduce the cost of deployments and risk of errors while deploying. 

Support for Skipping Assets during Deployment

You can now select the assets that must not be deployed to the current environment. A new tab, Skip Assets is added in the Deployment wizard to provide information about the assets and their dependencies that are already existing in the current environment for that project. Before deploying, you can choose the assets that must be skipped.

Earlier, you had no option to view the assets being deployed from one environment to the other environment. Assets that are available in the environment were overridden.

With this feature, you have complete information about the assets and control over the assets that are being deployed to the current environment. Additionally, icons are displayed beside the assets for easy identification indicating the asset types.
This feature is not available by default. To enable this feature, contact Software AG Global Support.

Support for Multiple Port Bindings in SOAP Connectors

The URL field in the Add Account dialog box for SOAP connectors now gets updated with the corresponding link as per the selected Port Binding value when creating new accounts. You can also edit the URL to specify a different web service endpoint.

Support for Partner Certificate in SOAP Connectors

A new option, WS Security Partner Certificate Alias, has been added in the Add Account dialog box of the SOAP connector for providing the partner certificate information. With the partner certificate information, you can now invoke a web service using the SOAP connector, which was earlier not possible.

Custom Action Enhancements

While creating a custom action, you can now view the selected value for the Operation, Business Object, and Interaction fields at the top of the corresponding screens.

Label for deprecated triggers

All deprecated published triggers can now be identified by the Deprecated label displayed below the trigger name. The deprecated label appears under the relevant published trigger name on the trigger selection screen, trigger configuration screen, and on the workflow canvas.

Support for Updating Predefined Connector Account Information

You can now edit the account details of a predefined connector directly from FlowServices.
Earlier, you had to go to the Connectors tab to edit the account details.

webMethods.io B2B Connector Enhancements on webMethods.io Integration

• New operations

  • getFAReport: Retrieves a list of transactions with reconciled functional acknowledgments and generates a report.
  • resubmit: Resubmits the existing transactions of webMethods.io B2B as new documents based on the transaction IDs.
  • reprocess: Reprocesses the existing transactions of webMethods.io B2B based on the transaction IDs.
  • queryTransactions: Retrieves transactions that match the specified criteria.
    
    

• Flat file batching for large documents
  A new output parameter hasMore is added in the convertFlatFileToDocument to process large flat file documents in batches.

Connector Enhancements

• The CLI connector runtime Node.js version is updated to v18.12.1
• The npm library for the SFTP connector is updated from v5.3.2 to v9.0.4

New and Updated Connectors

Explore new and updated connectors released recently in webMethods.io Integration.

Tutorials

In this release, new tutorials are added to assist you in understanding the features of webMethods.io Integration.

Customer Actions Required

SSL/TLS Certificate Update

SSL/TLS certificates for webMethods.io Integration and webMethods.io B2B will expire on March 29, 2023. If you are currently using SSL/TLS certificates with webMethods.io Integration and webMethods.io B2B, download the updated certificates from the specified location below and replace your existing certificates before March 29, 2023.

If you do not update your certificates before March 29, 2023, your 2-way SSL transactions will fail and you might experience an SSL handshake error. Root and intermediate certificates remain unchanged.

Azure cloud regions US2, EU3, AU1: Download certificates

SFTP Connector Update

For SFTP connector, when you receive sftp.list is not a function or sftp.put is not a function or No SFTP connection available error, replace the existing SFTP connector with a new one and reconfigure the action and connection.

Hybrid Connectivity Update

If you are using on-premises Integration Server v10.15 for hybrid connectivity, and if your hybrid connectivity uses two-way SSL, ensure that you have installed IS_10.15_WmCloud_Fix1 in your environment. Read more

Hybrid Integration Update

The host name format for Hybrid Integration has been changed to *.um.int-aws-de.webmethods.io, where * indicates the tenant-specific identifier.

Please ensure you allow following domains in your firewall or proxy settings:

Read more

Regular Expression Update

The replace and tokenize built-in String services accept a regular expression as an input. If execution of one of these services results in the java.util.regex.PatternSyntaxException, change the syntax of the supplied pattern. For example, if your regular expression has a value of , change it to . This change is required because characters like { or } need to be escaped with \ in the expression. Read more

Usage Notes

This section provides any additional information that you need to work with webMethods.io Integration.

• webMethods.io Integration is supported on the latest version of Google Chrome web browser (v110 or later).

• Every time you upgrade webMethods.io Integration, ensure that you clear the cache manually before logging in to webMethods.io Integration. This is because the older browser’s cache and cookies are not cleared automatically and the page content may not display correctly.

• webMethods.io Integration is best experienced when the scale and layout settings are as follows:
  
  

• webMethods.io Integration supports Transport Layer Security (TLS) version 1.1 and version 1.2 for connectivity.

• Any time stamp displayed in webMethods.io Integration is based on the user’s registered time zone specified in Software AG Cloud. Not all the time zones in Software AG Cloud are supported in webMethods.io Integration. If a time zone in Software AG Cloud is not supported, then the time stamp in webMethods.io Integration defaults to the Pacific Standard Time (PST) time zone. To change the time zone for a user profile, using the App Switcher, go to My Cloud and in Software AG Cloud, click My Cloud > Administration. On the Administration page, edit the user profile. Under Locale Information, select the required time zone. Save the changes, log out, and then again log in to see the changes.
  
  

• Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Go to the Software AG Cloud Regions website for information on the available products and also the underlying infrastructure provider in each region. Select the Show IP option on the Software AG Cloud Regions website for information regarding IP addresses.
  See the Tenant URL and Software AG Cloud Region section for more information.
  
  

• For information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events, see the webMethods.io iPaaS Service Status page.
  
  

• webMethods.io Integration v10.16 uses the regular expression pattern as described in the java.util.regex.Pattern class. Earlier, webMethods.io Integration used Perl 5 compiler and pattern matching while evaluating regular expressions. Some Perl 5 constructs are not supported by java.util.regex.Pattern which can result in unexpected behavior, such as a java.util.regex.PatternSyntaxException during expression evaluation. If your FlowServices use regular expressions based on Perl 5 constructs, it is recommended to review the regular expressions to ensure compatibility with the behavior described in the java.util.regex.Pattern class API documentation available here:
  https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html
  Review the contents of the Comparison to Perl 5 section, which identifies Perl constructs that are not supported by java.util.regex.Pattern. Regular expressions that rely on these Perl 5 constructs must be modified to work correctly with java.util.regex.Pattern.
  Note: The replace and tokenize built-in String services accept a regular expression as an input. If execution of one of these services results in the java.util.regex.PatternSyntaxException, change the syntax of the supplied pattern. For example, if your regular expression has a value of , change it to . This change is required because characters like { or } need to be escaped with \ in the expression.

• You can simultaneously open five FlowServices in different tabs in a browser.

• For SOAP and REST connectors, if you have created an account while creating a FlowService, then that account:

  • cannot be edited or deleted from the Connectors page.
    
  • cannot be used in Workflows. The pre-existing accounts are not available in the Connectto drop-down list while creating a Workflow.
    
  • cannot be used in migrated REST applications.
    You have to create a new account in all the above mentioned scenarios.
    
    

• You can import FlowServices using an on-premise connector to different environments. However, you cannot use the FlowService until you configure the on-premise connector in the destination environment.

• Ensure to configure the On-Premise connector in the destination environment before publishing a project that has a FlowService using On-premise connector. This is so because, the On-premise connector is not published to the destination environment along with the FlowService.

• After changing a REST-based connector’s document type, ensure that you update the operation using that doctype. This updates the operation signature, and the doctype changes reflect correctly in the connector.

• After creating a SOAP connector, if you immediately try to update it’s description, the updation process takes longer than usual. Update the SOAP connector by going to the Connectors page.

• Some pre-defined operations in the Salesforce® CRM REST connector may not work if you are using an account configured with the JWT flow authentication type.

• Click here to see some of the most common scenarios you may come across while configuring an Account, as well as troubleshooting tips on Account configurations. Information on the connector Account configuration fields can be found here. For information on custom actions, custom fields, field lookups, business objects, business parameters, and interactions, click here. Browse through the Software AG Tech Community tutorials related to connectors here.

• The FTP connector used in a FlowService is different from the FTP connector used in a workflow. So if you create an FTP account in a FlowService, the FTP account will not be available inside a workflow. Similarly, if you create an FTP account in a workflow, the same FTP account will not be available inside a FlowService.

• As Reference Data generally varies across different environments, you need to reconfigure the Reference Data as per the respective environment. Therefore if you are publishing a project that has a FlowService with Reference Data, the Reference Data will not be published along with the FlowService. You are required to create the Reference data in the destination environment. Further, if a FlowService you are exporting has Reference Data, the Reference Data will not be exported along with the FlowService. You are required to create the reference data in the destination environment.

• Additional headers are observed when running a REST application.
  When a REST application FlowService is run with changed header attributes, sw6 headers may be observed in the pipeline output result. Note that sw6 is a valid request header used by End-to-End Monitoring for monitoring Software AG product runtimes. This has no impact on feature functionalities.

• webMethods.io Integration does not honor the following headers and their values will be ignored:

  • X-Forwarded-Host
  • X-Forwarded-For
  • X-Forwarded-Proto
  • X-Forwarded-By

• Although the Workflow to FlowService or on-premises application mapping of the following data types is allowed in webMethods.io Integration, such Workflows, FlowServices, or on-premises applications may not run as expected:
  • String type in workflows to Num (Double/Float/Int/Short/Long) type in on-premises applications
  • String type in workflows to Byte type in on-premises applications
  • Boolean type in workflows to Byte type in on-premises applications
  • Object type in workflows to Byte type in on-premises applications
  • Number type in workflows to Byte type in on-premises applications
  • Array type in workflows to Num type in on-premises applications
  • Number type in workflows to Boolean type in on-premises applications
  • Boolean type in workflows to Num type in on-premises applications
  • Object type in workflows to Num type in on-premises applications
  • String of String Array type in workflows to Boolean type in on-premises applications
  • Float type in workflows to Num type in on-premises applications

• If the data type of a FlowService is set to Object in the I/O signature, then it is considered as a String type in the associated workflow. Such workflows may not run as expected.
• Configuring the same client application details across multiple custom OAuth-based accounts may lead to issues related to access token invalidation. To avoid the issues, configure a unique set of client application details for a custom OAuth-based account.
• Listeners configured with the Select replay option as New and enabled with a specific replay id might miss some of the replay events. This is in accordance with the current feature design.

Known Issues

This section lists the issues for this release that were known when this release readme was published.

WSP-1758
Contact Support error observed while deploying a project having an SAP® ERP listener. This issue occurs while deploying a project having SAP® ERP listener notifications.
When you deploy a project containing SAP® ERP listener notifications, the deploy wizard provides you with an option to either create a new listener or select an existing listener. This listener is associated with the listener notification being deployed.
When you select a listener from the dropdown list, which is in disabled mode or enable pending mode, the listener notification deployment fails with an error related to enabling the listener. If you continue with the deployment even after the error, An error occurred while processing your request. Contact support. error message appears.
Workaround: Always select an enabled listener while deploying a project having SAP® ERP listener notifications.

WSP-1573
Unable to edit imported action with created account.
An account name is associated with each SAP® ERP action. If the account with associated account name is not enabled in the project, the SAP® ERP action cannot be edited.
When an export/import function is used, the SAP® ERP action in the target project contains the associated account name.
However, the SAP® ERP account is not created in the target project.
Workaround: To edit the SAP® ERP action in the target project, do the following:
- If an SAP® ERP account with an associated account name exists in the target project, enable the SAP® ERP account in the target project and disable it in all other projects.
- If an SAP® ERP account with an associated account name does not exist in the target project, create and enable the SAP® ERP account in the target project.

FLOW-2575
In a transform pipeline, when both direct mappings and prediction mappings are present and you try to scroll the pipelineInput or pipelineOutput panel, the mapping lines are broken.
Workaround: Collapse and expand the direct mappings. The mapping lines will be repainted properly. This issue exists only when the scroll bar exists and you scroll either horizontally or vertically.

FLOW-2215
The icon position for adding a new FlowService step is not proper when the Expand All and the Collapse All buttons are used.
Workaround: Toggle the expanded state of the step on which the icon appears. This corrects the icon position when adding a new step.

BIC-8481
Users are unable to update the custom time field under the Monitor tab with a simple click in Firefox browser.
Workaround: In Firefox, users can clear the time field value they want to update and re-enter the required value. Alternatively they can use any other browser to update the custom time field value with a simple click.

JDB-2977
In the Database application, updating an Update operation leads to incorrect output.
Workaround: Once you add or delete the table columns or data fields, verify the input/output names and update the proper input/output names if they are not correct.

BIC-5324
After logging out from Software AG Cloud, when a user logs in again using a different username and then navigates to webMethods.io Integration using the App Switcher, the user sees that the earlier user’s session has still not been logged out.
Workaround: Log out from webMethods.io Integration, instead of from Software AG Cloud.

JDB-3112
Editing an imported workflow or FlowService having database application operations displays an error.
When a workflow or a FlowService is exported using the webMethods.io Integration export functionality, the connection name is not saved in the exported workflow or FlowService. On editing the database operation in the imported workflow or FlowService, the connection associated with the action is not found.
Workaround: The imported workflow or FlowService having database operations can be executed with a valid connection.

JDB-3106
The SQL query in CustomSQL is parsed by the system using a third-party SQL query parser (FoundationDB SQL Parser) to populate the input and output. When the SQL query parser is unable to parse, the error Failed to fetch Database Metadata appears.
Workaround: If the input and output for CustomSQL operation is not populated, ignore the error and configure the input and output explicitly.

Flow-4355
Ensure that you provide correct values for the input fields in the Set Value or Run dialog boxes when running a FlowService. This is because the input values are not validated according to their data types by the system and you may encounter errors.

Fixes

This section provides information on the fixes for webMethods.io Integration v10.16.

Release 10.16.0