Release 10.15

Highlights

New features and enhancements	Description
Release 10.15.3	webMethods.io B2B Connector Enhancements on webMethods.io Integration
Addition of four 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.
Release 10.15.2
Fixes included in the 10.15.2 release	See the Fixes section for information on the 10.15.2 fixes.
Release 10.15.1
Restart and resume Workflows and FlowServices	The execution listing page of the Monitor tab is enhanced to provide two new options for Restart and Resume under the newly added Actions column. Using these options, you can now restart and resume Workflow and FlowServices executions from the main execution listing page.
Search tenant users on User Management page	You can now search tenant users listed on the User Management page through the newly added search box. You can use the name or email address associated with the user as a keyword.
setCustomContextID input parameter length	A maximum of 72 characters are now supported for the ID parameter in the setCustomContextID service. In the event that an ID exceeds 72 characters, only the first 72 characters are stored. With this support for lengthy IDs, users can easily correlate the onprem and cloud executions especially for hybrid integrations. Previously, the ID length was limited to 36 characters.
Fixes included in the 10.15.1 release	See the Fixes section for information on the 10.15.1 fixes.
Release 10.15.0
OAuth 2.0 authentication for Coupa	Coupa has strengthened its security for all API integrations and require the use of only OAuth 2.0 authentication, for all integrations. You can select this authentication type while adding a custom action in Coupa. The OAuth 2.0 authentication for Coupa requires Scope - assignment which is like a set of permissions set on the API key. You can find the list of scopes and their underlying Coupa permissions by going to the Coupa API Scope management page at /oauth2/scopes. Scopes are available for review on https://{your_instance_address}/oauth2/scopes. For detailed steps on OAuth Client creation and scope assignment in Coupa, see the OAuth 2.0 Transition Guide at the Coupa Success Portal. Click here for information on how to set up a Coupa OAuth 2.0 client and configure a connection.
OAuth 2.0 authentication for SAP SuccessFactors	OAuth 2.0 authentication is enabled for the SAP SuccessFactors connector to authenticate users in a more secure way. Mandatory fields required to generate the access token to authorize the API requests under the OAuth 2.0 authentication for SAP SuccessFactors are as follows: Company ID: SuccessFactors Company ID. Client ID: API Key you obtain after you register your client application in SAP SuccessFactors. Grant Type: Set the value to urn:ietf:params:oauth:grant-type:saml2-bearer. Assertion: Base64-encoded assertion obtained from generating a SAML Assertion.
Custom connector enhancements	In earlier releases, you could import, export, share, clone, and deploy a workflow having a custom connector to another tenant, only if it was first made global. In this release, this restriction is removed. You can now import, export, share, clone, and deploy a workflow having a custom connector to another tenant, without making it global.
Multiple WSDL files while creating a SOAP API	You can now select one or multiple dependent WSDLs, XSDs, and/or XMLs to the primary WSDL at the same time by clicking Browse file(s) or using the drag and drop functionality. Earlier, you could select only one dependent WSDL, XSD, and/or XML to the primary WSDL at a time.
Enhancements in Edit Account screen	The following changes are now implemented in the Edit Account screen: In earlier releases, when you clicked the Edit Account button, all the existing values of the mandatory fields were automatically cleared. You had to re-enter the value for each mandatory field. In this release, the existing values of the mandatory fields (for example, Client Key) are masked. You can now update the masked value of any mandatory field. To do so, click the Edit icon on the relevant mandatory field, enter updated value, and click Save.
Publish projects across regions	In earlier releases, you could publish projects to different environments, only if they existed in the same region. In this release, this restriction is removed. You can now publish projects to environments existing across different regions. Note: The destination environment must be on the same or higher version than the source environment. If the destination environment is on a lower version than the source environment, an error appears.
Free Forever subscription	If you now sign up for a webMethods.io Integration trial tenant, the Free Forever Edition plan is assigned by default, which does not have an expiry. You can optionally upgrade to the Basic, Advanced, or Enterprise paid plan based on your requirements, by contacting Software AG Sales.
New service	The createMessageDigest service has been added in this release in the Utils category, which allows you to generate a message digest for a given message.
Stability and performance improvements	Event data is now directly stored into the database.
Support for concurrent message processing	The Messaging feature has been enhanced to process messages received from the Messaging Provider in parallel. That is, a subscriber processes multiple messages at the same time resulting in faster performance than processing in a serial manner. A new tab, Message Processing, has been added in the Subscriber settings screen to configure the subscriber processing mode. Additionally, a new property, Acknowledgement mode, has been added in the General tab of the Subscriber settings screen, which allows users to specify how the subscriber must acknowledge messages received from the Messaging Provider.
Support for Particular Replay ID in Salesforce Listener	The Salesforce Listener has been enhanced to receive events from Salesforce by providing a specific replay ID. A new screen, Configure listener, has been added allowing users to specify the replay ID while enabling listeners. Users also have an option to replay new or all events by specifying the values -1 and -2 respectively. Earlier, users were able to configure the replay ID only when creating a listener and not when enabling the listener.
New APIs	New APIs have been introduced in the following domains: Workflow APIs: Allows you to create, export, import, delete, and execute a workflow. Trigger APIs: Allows you to get the workflows that are trigger enabled and delete a trigger.
Tutorials	In this release, new tutorials are added to assist you in understanding the features of webMethods.io Integration.
End-to-End Monitoring documentation	End-to-End Monitoring documentation is now independent of webMethods.io Integration documentation for better visibility and ease of access.
New and updated Connectors	Explore new and updated connectors released recently in webMethods.io Integration.
Creating new document types	Create new SAP® ERP document types from an SAP RFC structure, or a SAP IDoc that matches the structure of the document and content of the SAP RFC structure, or SAP IDoc respectively.
Asset support matrix	View the list of functions supported for various assets in the current version of webMethods.io Integration.
Support for pre-bundled driver groups	Three new pre-bundled driver groups are now supported in webMethods.io Integration: Progress® DataDirect® for Microsoft SQL Server, Oracle Microsoft JDBC Driver for SQL Server for Microsoft SQL Server PostgreSQL JDBC Driver for PostgreSQL
Support to deploy connector builder connectors to data centers	You can now deploy custom connector builder connectors to different tenants within the same data centers or across data centers.

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 (v104 or later).

• Every time you upgrade webMethods.io Integration, ensure to 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.2 for connectivity. Click here to check the supported ciphers for inbound traffic.

• 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 webMethods.io iPaaS Service Status.

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

WFL-133
For cross-region and cross-cloud provider deployments, when a user updates a trigger event and redeploys the workflow from the source tenant, the updated trigger event is not reflected in the destination tenant.

WFL-924
For cross-region and cross-cloud provider deployments, if a workflow is not correctly imported in the destination tenant and a user tries to manually configure the trigger, an error appears.

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.