Explore the release highlights, usage notes, and known issues for webMethods.io Integration.
|New features and enhancements||Description|
|Smart Mapping||Smart mapping provides you with recommendations while mapping the pipeline data and utilizes a series of algorithms to determine the likely accuracy of a given suggestion, enabling you to toggle between high, medium, and low levels of mapping confidence.
A Machine Learning (ML) algorithm is applied to provide the suggestions. The ML algorithm learns from the mappings you create and provides suggestions automatically to map similar fields. The algorithm benefits from having more data from more number of users.
Smart mapping is anonymous and does not store any customer-specific information or actual data of any kind and is available to only those tenants who provide their consent to share their mapping information.
|OAuth 2.0||You can now protect integration services and REST APIs using the OAuth 2.0 protocol. In OAuth 2.0, the client obtains an access token issued by an authorization server on approval of the resource owner. The client uses the access token to access the protected resources.
|Two-Way SSL for inbound connections||webMethods.io Integration now supports Two-Way SSL for inbound connections. You can store client certificates, associate a certificate with a user account, and also set the following Two-Way SSL security mode while configuring an SSL connection:
|Cloud Messaging||The webMethods.io Integration messaging solution allows you to implement the publish/subscribe or point-to-point messaging styles by bringing the JMS-based messaging capabilities.
Messaging is not available by default for a tenant. To enable this functionality, contact Software AG Global Support.
|Support for FlowService Recipes||In earlier releases, you could browse and use only workflow recipes in the selected project.
In this release, FlowService recipes are also available on the Recipes page, which enables you to use pre-configured FlowServices in your project.
|Project Permissions for Custom Roles||In earlier releases, you could create custom roles to define which projects are accessible under a particular custom role.
In this release, project permissions for custom roles determine the actions a user can perform in each project.
There are three types of project permissions:
|Custom domain names||A custom domain is a unique name that identifies your website. There are scenarios where you do not want to expose the default domain provided by webMethods.io Integration. In such cases, you can customize the default tenant URL or domain and access the tenant using your own domain. Use custom domains if you want to make your application accessible on your own domain.
Contact Software AG Global Support for details on how to enable and configure the custom domain capability.
|Refreshing OAuth 2.0 Access Tokens||To refresh the access tokens for accounts which use the OAuth 2.0 protocol, you can now specify a Refresh Token Callback Service which will execute when the access token expires. Select Refresh Token Callback Service in the Refresh URL Request field and provide the integration name in the Refresh Token Callback Service field.
|Dedicated messaging infrastructure support for hybrid integration scenarios||Performance, scalability, and availability of on-premises connectivity for hybrid integration scenarios have now been enhanced by having dedicated Software AG Universal Messaging (UM) nodes for each tenant. A tenant can be configured with dedicated UMs based on the license.
Contact Software AG Global Support for assistance in setting up the dedicated hybrid infrastructure.
|Manage environments through Software AG Cloud||In earlier releases, you could register and manage environments from within your webMethods.io Integration tenant.
In this release, you can register, link, and manage environments from Software AG Cloud as well.
|Grouping of right-click options in the FlowServices editor||In this release, if you right-click on a field in the pipeline, you can copy a field, move fields up, down, left, or right in the pipeline, set a value for a field, remove the value set for a field, drop a field from the pipeline, undo the drop field action, and delete, or edit a field.
|Modified rate limit condition for paid plans||The rate limit for all tenants under paid plans is now 150 requests per minute for AWS-based tenants and 400 requests per minute for Microsoft Azure-based tenants. This rate limit is applicable to sync webhook-enabled, async webhook-enabled, trigger-enabled, as well as manually run workflows.|
|Enhanced Operations screen||You can now view the root level element of the Input and Output signatures for all the newly added predefined and custom connectors in webMethods.io Integration in the same way as on-premises. These changes are not applicable to the existing pre-defined and custom connectors in webMethods.io Integration.
|Support for REST resource error handling||You can now handle HTTP errors by selecting the Error Response message option.
If this option is selected while creating a REST resource, then during the execution of an operation in a Workflow or a FlowService, if you receive a corresponding Status Code as response from the back end, an exception appears.
For example, if a resource is created with status HTTPs code as 300-500 identified as Error Response, then during execution, if we receive any response from 300-500, the operation execution will be considered as failure.
|Audit log enhancements||webMethods.io Integration now allows you to apply filters on audit logs to retrieve specific logs through the Monitors tab. You can filter your logs by using the following criteria:
|Alert email notification enhancements||The following enhancements are now available in the alert email notification process for Workflows:
|Disable accounts||webMethods.io Integration now allows you to stop a workflow or a FlowService from being executed through the Connectors tab. Disabling an account of an application or an external web service is temporary. You can re-enable the account anytime as per your requirements.|
|Enable invalid or disabled accounts||Occasionally, accounts configured for connectors get disabled and/or become invalid due to several reasons. In such cases, webMethods.io Integration now allows you to re-establish the invalid or disabled account connection of configured accounts through the Connectors tab.|
|Conditional logging||webMethods.io Integration now stores the execution logs of workflows, only if you select the Maintain execution logs option under Workflow Settings.
|User interface and user experience improvements||For improved usability and experience, the following user interface enhancements are implemented in this release:
|Configure Stop icon for Workflows||webMethods.io Integration now allows you to configure the Stop icon for workflows. The Stop icon allows you to output a message (up to 256 KB) of the preceding action or a workflow in console logs. In case the specified message exceeds 256 KB, you will get the Message Size Too Large string.
This icon works the same as the Logger action.
|Secure webhooks with Webhook Key authentication||You can now apply the Webhook Key authentication mechanism to add an extra layer of security to your webhooks.
When you select the Webhook Key authentication option while configuring a webhook, a random webhook key is automatically generated. Once configured, you will need to pass this webhook key as a header every time you send a webhook execution request. Without this webhook key, the webhook execution request will not be processed.
|Disable workflow actions||You can now disable one or more actions of your existing workflows. This eliminates the need to manually detach or delete actions that you do not want the workflow to execute, thereby saving time and effort.
This feature is useful for complex workflows where you may want to disable multiple actions quickly and easily.
|Database application||You can connect to a database using the Database application and perform database operations with cloud databases. In earlier releases, you can create the Database application by clicking the webMethods.io Flow Apps option available on the App Switcher.
From this release, the Database application is available within the webMethods.io Integration User Interface.
|More connectors in the FlowServices editor||More connectors are now provided in the FlowServices editor. Note that all the connectors available in webMethods.io Integration are listed on the Connectors screen.
As the pre-defined connectors are currently being synchronized for Workflows and FlowServices, you may observe variances in the list of pre-defined connectors available on the Workflow and FlowServices screens.
|Connector account configuration fields||A new section on connector account configuration fields is added in this release. The connector account configuration fields allow you to connect with the connector. The fields available may vary according to the selected connector.|
|Common error scenarios while configuring an account||A new section is added in this release where you can learn more about some of the most common scenarios while configuring a connector account.|
|Rename conflicting child FlowServices during import||In earlier releases, you could not rename a child or dependent FlowService if it had a conflict during import. From this release, you can also rename the child FlowService if it has a conflict during import.|
|Default Authorization option for some connectors||In this release, you can easily get the Access Token automatically after selecting the Default Authorization option and specifying a few parameters while configuring an account from the FlowServices editor. The Default Authorization option is currently enabled for some connectors only.
|New Connectors||The following connectors are added in this release:
|Delete option in Data Store actions||In earlier releases, you could only set key-value pairs and fetch them when required during a workflow execution using Data store actions, namely Account Store, Flow Store, and Memory Store.
From this release, you can delete the stored key-value pairs using Data Store actions, namely Account Store, Flow Store, and Memory Store.
|Enhanced workflow keyboard shortcuts||Few new keyboard shortcuts and some existing ones have been enhanced in this release in the workflow canvas to make your integration experience richer.|
|Visual indicator for the Transform operation||All actions containing the Transform operation now have the icon. This eliminates the need to open the action, and check whether an action contains a Transform operation or not.
|Software AG Tech Community Tutorials||A new section in Tutorials has been added in this release where you can browse through some of the Software AG Tech Community tutorials relevant to webMethods.io Integration.|
|Masking sensitive project parameters in console logs||In Project Parameters, if you have marked a project parameter as a password field, then the value of the specified parameter will now not display in the console log.
|Clone, Import, and Export Workflows containing FlowServices||Earlier you had to manually clone, import, or export a FlowService if it was a part of a cloned, imported, or exported Workflow, respectively. From this release, all FlowServices available inside a cloned, imported, or exported Workflow will be automatically cloned, imported, or exported along with other Workflow assets.|
|View webhook and trigger payload data in execution logs||You can now view the payload data of your configured trigger or webhook in the workflow execution logs under the Monitor tab.
|Prevent concurrent executions in Clock trigger||You can now optionally restrict the concurrent execution of a clock trigger. If you set a clock trigger and set the Disable Concurrent Execution field to true, the clock trigger will not execute a new instance of the workflow till the previous workflow instance execution is completed, that is, the workflow executes successfully, time outs, or fails.
|Support for webhook payload increased to 10 MB||In earlier releases, the support for webhook payload was up to 5 MB. From this release, the webhook payload support has been increased to 10 MB.|
|Monitor Enhancements||In the Monitor tab, the following enhancements have been made in this release:
|Stream support for upload and download actions||In this release, stream support for upload and download actions has been added for the following connectors:
|Feedback on Documentation||You can now provide feedback on a page, specific content on a page, or on the webMethods.io Integration documentation website by using the feedback form.|
|Enhanced custom operation screens in FlowServices||In this release, custom operation screens for the following connectors are replaced with workflow screens for improved usability and experience.
Note: You cannot use the accounts created earlier for these connectors using the custom operation screens. Ensure that you create new accounts in such cases.
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 (v88 or later).
After webMethods.io Integration is upgraded, the older version browser’s cache and cookies are not cleared automatically. This may lead to incorrect display of page content. Ensure that you clear the browser’s cache manually after every upgrade, and then log in to webMethods.io Integration.
webMethods.io Integration is best experienced when the scale and layout are adjusted to the below settings:
webMethods.io Integration supports Transport Layer Security (TLS) version 1.1 and version 1.2 for connectivity.
Information on major releases, hotfixes, and patch releases including the latest statistics on cloud system availability, system performance, and security are available on the Cloud Trust Center.
If you are using hybrid connectivity and when you update the on-premises settings (Update Settings) for the first time after the webMethods.io Integration v3.0 upgrade, restart the on-premises webMethods Integration Server. After restart, upload the on-premises account to resume hybrid connectivity. This is applicable for all the on-premises Integration Servers connecting to webMethods.io Integration.
If you have whitelisted the Cloud Universal Messaging (UM) hostname in the firewall, you have to also whitelist the new UM hostname along with the old one.
Click here and select the Show IP option on the Software AG Cloud Regions website for information regarding IP addresses.
If you have changed the user password in the Software AG Cloud Administration Users page, in the webMethods Cloud Settings page in webMethods Integration Server Administrator, update the new user password, disable and then enable the webMethods Cloud Account, and then again upload the webMethods Cloud Application to webMethods.io Integration.
Accounts created for SOAP and REST connectors using the Flow Editor do not display the Edit and Delete icons when the same Accounts are displayed on the Connectors page in webMethods.io Integration. You can use the existing accounts configured using the Flow Editor, but you cannot edit or modify the account details. Ensure that you create a new account for the SOAP and REST connectors if any changes are required for the existing accounts.
Further, the accounts created for SOAP and REST connectors using the Flow Editor cannot be used in Workflows, that is, pre-existing accounts will not be available in the Connect to drop-down list while creating a Workflow. Ensure that you create new accounts in such cases.
Also, for migrated REST applications, you can modify an existing operation by creating a new account but not with an existing account.
You can simultaneously open up to five FlowServices in different tabs in a browser.
If you want to import a FlowService to another tenant that has an on-premises connector, before importing the FlowService, ensure that you upload the same on-premises connector to the other tenant in webMethods.io Integration, else you will not be able to import the FlowService.
When you publish a project that has a FlowService, and if the FlowService has an On-Premises connector, the On-Premises connector is not pushed to the destination tenant. Ensure that you configure the same On-Premises connector on the destination tenant to make the published FlowService work.
If the FlowService you are importing use SOAP or REST connectors and if those connectors do not exist in your system, continue importing the FlowService. The connectors are imported along with the FlowService. After importing, create the Accounts and then configure them in the imported FlowService.
If a FlowService you are importing uses an on-premises connector and if the connector does not exist in your system, the Account appears only after you have uploaded the on-premises connector.
If a FlowService is created with output HashTable and a workflow is created with the same FlowService, and if you run the same service in the FlowService, HashTable is not available in the FlowService Output. Set the Accept header as application/json so that the output has the HashTable object.
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.
A workflow, which contains an on-premises connector, cannot be cloned.
After navigating to Software AG Cloud, if the trial period has expired, you will not be able to switch back to webMethods.io Integration.
After creating a SOAP connector, updating the description of the same connector will take longer than usual. This happens if you try to update a SOAP connector just after creating it. After creating a SOAP connector, go to the Connectors page and update it.
If you are not able to map multiple documents to a document array based on indexing in a FlowService, create a document array that holds all the required documents using the insertDocument operation of the Document service. For example, if you want to map three documents (D1, D2, and D3) to a document array (DA1), add the insertDocument operation thrice, once for each document, and insert D1, D2, and D3 into the documents array. You can also use loops to run the insertDocument operation thrice. Finally, map the documents array, which holds all the three documents, to DA1.
This section lists the issues for this release that were known when this release readme was published.
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.
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.
Unable to create a REST API with JSON file.
This issue is observed when a REST API is created from a Swagger file, which has OAuth as the authentication scheme.
Currently, creating REST APIs from Swagger files which has OAuth as the authentication scheme is not supported.
If you add a Cumulocity trigger in a workflow and try to save the trigger, the trigger is not saved in certain cases.
When a workflow having 130 MB data is run, the workflow fails, but notifications do not appear in the user interface and the workflow keeps running.
Workaround: Refresh the page to view the failed status of the workflow.
On the Monitor screen under Workflow Executions, when users try to set a custom time frame using the Date-Time filter for fetching specific execution details by continuously increasing the Stop time while keeping the Start time constant, the Total Executions count fails to increase. Further, the total execution count and workflows count are not matching. For example, when a user sets the Start Time to 03/17/2021 12:30 PM and Stop Time to 03/17/2021 01:04 PM and then tries to increase only the Stop Time from 03/17/2021 01:04 PM to 03/17/2021 01:05 PM to 03/17/2021 01:06 PM with multiple rapid clicks, the Total Executions count fails to increase.
Workaround: Wait until the result of the previous action loads completely and then change the time.
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 reenter the required value. Alternatively they can use any other browser to update the custom time field value with a simple click.
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.
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.
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.
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.
Workflow executions take around a minute to sync with the data on the Monitor screen.