Explore the release highlights for webMethods.io Integration.
|New features and enhancements||Description|
|REST and SOAP API enhancements||In the earlier release, you could create REST APIs from scratch or by importing an existing API from a swagger file. In this release, you can also create REST APIs by importing an existing API from a Swagger URL.
Also, while editing a REST API, you can upload a new Swagger file from the API Details page.
Further, you can now import REST APIs using URLs protected with basic authentication, that is, support is provided in case authentication is required, if the REST API URL supports credentials.
Alert Rules (Monitor > Alert Rules > FlowService Alerts) for REST API and SOAP API assets have also been added in this release.
|Support for Flat File connectors||webMethods.io Integration now supports the flat file connector to translate documents into and from flat file formats. You can create a flat file connector using any one of the following approaches:
|Enhanced custom operations screen||You can now view the input/output signature and test custom operations for REST, SOAP, On-Premises, and Flat File connectors. The Show i/o signature and Test operation options are available on the Custom Operations screen.
After you create an operation, click the Show i/o signature option to view the Input and Output signature of the custom operation. The input and output fields cannot be edited. You can click the input and output fields to view the field properties.
The Test operation option allows you to test the custom operation. Specify the Account name and the Input data and then click Run to test the operation and view the test results in the Result window. For array inputs, you can add the array items and then add the values. If an operation does not have an input signature, the input fields are not displayed.
|Support to modify service-level pipeline data before resuming FlowService execution||In earlier releases, you could modify only the FlowService-level pipeline data before resuming a FlowService execution. In this release, you can modify the service-level pipeline data till the failure point before resuming a FlowService execution.|
|FlowService enhancements||You can now right-click on a step on the FlowService editor and add a step or a child step for the selected step, and paste the step(s) after the selected step(s) by clicking the Duplicate option.
The Duplicate option is also available if you click the icon.
|Support for Branch construct in FlowServices||You can now perform different actions on different values of one or more pipeline variables by using the Branch construct.
Branch is a conditional execution of steps and constitutes a group of expressions. Within a Branch, webMethods.io Integration runs the first expression that evaluates to true. Expressions are the conditions on the pipeline variables.
At run time, Branch evaluates the conditions provided and runs the first expression whose condition is evaluated to true. If none of the expressions are true, the default expression if included, is run.
|Lock and Unlock FlowServices||webMethods.io Integration now allows you to manage a FlowService during the development life cycle by auto locking. When you edit a FlowService, it is automatically locked for you. This restricts multiple users from editing the FlowService at the same time. Other users can open the FlowService only in view mode. After you edit a FlowService and save the changes, you can exit the edit mode to unlock the FlowService and make it available for other users. Relevant messages appear in the user interface for other users if you are editing a FlowService and have completed editing the FlowService, and also if another user tries to delete the FlowService.
If you have kept the user session idle for quite some time or because of any other reasons a FlowService lock remains and is not resolved, only a user with Admin role can unlock the FlowService and make it available for editing by clicking the Unlock option available on a FlowService.
|Support for adding icons for REST and SOAP connectors||You can now add icons for custom REST and SOAP connectors while creating them.|
|Support for adding assets for alert rules for FlowServices||While adding an alert under Alert Rules (Monitor > Alert Rules > FlowService Alerts), you can now select the Assets option to select the list of all assets (REST APIs and SOAP APIs) created in a project. This will help you get notifications and keep relevant users updated about the status.|
|Restart workflow execution||You can now restart your failed workflows that were triggered using webhook, through the execution logs screen under the Monitor tab.
You can optionally edit the webhook payload of the workflow before restarting it.
|Resume workflow execution from the point of failure||You can now resume the execution of your workflow right from the point it has failed, using the execution logs screen under the Monitor tab. .
To enable this feature, select the Save status of each successfully executed action check box in the Execution Settings tab under the Workflow Settings screen.
You can optionally edit the JSON input schema of the failed action(s) before resuming the workflow execution.
|View transaction usage||Users of transaction-based tenants can now view the transaction usage statistics of their tenants on the Usage page under the Monitor > General tab. You can see the Usage page only if transactions are enabled for your tenant.
|Support for Node.js function to set the workflow status to failed||Support has now been added for a Node.js function which sets the status of the workflow to fail. This function can be used in any of the actions that enable you to write custom logic for your workflow.|
|Set failed status for workflows||In earlier releases, the status of a workflow used to be always Successful when the Global Error Handler action was used. In this release, we have introduced a new Set Workflow Status Failed Action, which enables you to modify the status of such workflows to failed.
You can also add a custom error message, which appears when the workflow fails.
|Support for Node.js function for Memory Store||Support has now been added for a Memory Store Node.js function, which allows you to set and retrieve the value of key(s) for a single execution run. You can use this function in any of the actions that enable you to write custom logic for your workflow.|
|Input/Output logs for Logger action removed from the Debug Panel||In earlier releases, whenever you executed any Logger action, you could view its input and output logs in the Debug Panel. In this release, input and output logs are removed for the Logger action from the Debug Panel.
You will continue to view the input/output logs in the Log section whenever you click on the executed Logger action in the Debug Panel.
|White label enhancements||In this release, the Link Border Color setting in the White label configuration screen is added. This setting allows you to change the border color of the user interface menu.|
|Tenant settings changes||In earlier releases, you could view and manage all the tenant settings by using the Settings option under the Tenant Profile icon. In this release, the following options are available when you click on the Tenant Profile icon:
|New Connectors||The following connectors are added in this release:
|Version field changes for the Workday connector account||The Version field in the account configuration dialog box of the Workday connector is now made read only.|