Release 10.15

Explore the release highlights, usage notes, known issues, and fixes for webMethods.io Integration.

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.

    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.




    Version Issue ID Release Date Region Description
    10.15.2 KUB-18604
    January 12, 2023
    January 12, 2023
    January 12, 2023
    January 13, 2023
    January 13, 2023
    January 13, 2023
    AU1 Australia East Azure
    EU3 West Azure
    US2 East Azure
    AU2 Sydney AWS
    EU2 Frankfurt AWS
    US1 Oregon AWS
    REST API returns 401 unauthorized error while supplying the X-Forwarded-Host header. Note that webMethods.io Integration does not honor the X-Forwarded-Host header and its value will be ignored.
    10.15.1 WFL-1391
    WFL-1671
    WFL-1673
    December 21, 2022
    AU1 Australia East Azure
    Some workflows time out before execution initiation without any execution logs. Changes are made to resolve this issue.
    10.15.1 WFL-100
    WFL-992
    December 14, 2022 AU1 Australia East Azure
    EU3 West Azure
    US2 East Azure
    AU2 Sydney AWS
    EU2 Frankfurt AWS
    US1 Oregon AWS
    While passing the token value through webhook payload and mapping it to the dynamic account token value to allow the REST connector use the token, the value shown is, $request.headers.token.
    10.15.1 WFL-1225 December 14, 2022 AU1 Australia East Azure
    EU3 West Azure
    US2 East Azure
    AU2 Sydney AWS
    EU2 Frankfurt AWS
    US1 Oregon AWS
    FTP, SFTP, and MySQL connectors were failing on BIGINT enabled tenants. Changes are made to resolve this issue.
    10.15.1 CCH-4856
    WFL-1579
    December 11, 2022
    December 11, 2022
    December 11, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    During the SFTP connector execution, sftp.list is not a function and sftp.put is not a function errors appear.
    10.15.1 BIC-17993
    FLOW-4304
    December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    Environment slowness observed during deployments.
    10.15.1 FLOW-4209 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    For Document types, the order of fields are now maintained during runtime.
    Earlier, the mapped fields were listed first followed by unmapped fields during runtime.
    10.15.1 WFL-1168 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    While configuring a customized input form in JSON Customizer, if users provide a numeric value for a particular field in the code block, the rendered input form shows the field type for that field as str instead of num.
    10.15.1 WFL-1124 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    Users receive invalid authorization error while testing a newly created authorization.
    10.15.1 WFL-1209 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    Users cannot save a workflow if the workflow contains a Run Workflow action that calls another webhook-enabled workflow having a $ key in the payload body.
    10.15.1 BIC-17858 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    The routing rules got deleted whenever users tried to update a routing rule for a subscriber from Messaging Service Trigger. This issue occurred because the cache memory was not getting refreshed.
    Modifications have been done to ensure that the data is stored correctly in the cache memory and the routing rules are not getting deleted.
    10.15.1 BIC-17997 December 4, 2022
    December 4, 2022
    December 11, 2022
    December 10, 2022
    December 11, 2022
    EU3 West Azure
    AU1 Australia East Azure
    EU2 Frankfurt AWS
    AU2 Sydney AWS
    US1 Oregon AWS
    Tenant is not responding or loading pages. Connections are getting consumed by the storage services as part of checking if the previous scheduled integration is still in progress when the preventConcurrentExecutions option is enabled in the scheduler for FlowServices. As the connections are blocked, any new execution waits for the connection. This issue is resolved by releasing the connections.
    10.15.1 WFL-1266 December 3, 2022
    December 4, 2022
    December 4, 2022
    December 10, 2022
    December 11, 2022
    US2 East Azure
    EU3 West Azure
    AU1 Australia East Azure
    AU2 Sydney AWS
    US1 Oregon AWS
    Listener executions did not happen. During deactivation and activation of listeners, workflow and listener went into an inconsistent state because of a communication gap. The listener was active but the workflow was inactive. Changes are made to handle the edge case for deactivation and activation of listeners.
    10.15.0 WST-6755 December 6, 2022 US1 Oregon AWS
    EU2 Frankfurt AWS
    Salesforce listeners were not working. Issues with missed events are now resolved.
    10.15.0 WST-6755 November 25, 2022 US1 Oregon AWS Listeners were not working. This issue is resolved. As part of this, added logic to capture additional logs that facilitate easy debugging.
    10.15.0 WFL-1266 November 24, 2022 EU2 Frankfurt AWS Listener executions did not happen. During deactivation and activation of listeners, workflow and listener went into an inconsistent state because of a communication gap. The listener was active but the workflow was inactive. Changes are made to handle the edge case for deactivation and activation of listeners.
    10.15.0 BIC-17997 November 20, 2022 US2 East Azure Tenant is not responding or loading pages. Connections are getting consumed by the storage services as part of checking if the previous scheduled integration is still in progress when the preventConcurrentExecutions option is enabled in the scheduler for FlowServices. As the connections are blocked, any new execution waits for the connection. This issue is resolved by releasing the connections.
    10.15.0 WFL-801 October 13, 2022
    October 18, 2022
    October 19, 2022
    EU3 West Azure
    AU1 Australia East Azure
    US2 East Azure
    Workflows scheduled to run every 30 minutes timed out after 30 minutes without showing the logs. Most of the executions timed out due to action timeouts. This was observed intermittently.
    10.15.0 WFL-1111 October 18, 2022
    October 19, 2022
    AU1 Australia East Azure
    US2 East Azure
    Some workflow executions fail with the following error message: Cannot convert object to primitive value.