Explore the release highlights for webMethods.io Integration.
|New features and enhancements||Description|
|Projects home page enhancements||The following changes have been made to the Projects page in this release for improved usability:
New Project: Click the icon available on the Projects page to create a new project.
FlowServices: Click the FlowServices link available on a project to go to the FlowServices page for the project. In earlier releases, you could create complex integrations by switching to the Flow Editor using the App Switcher, where you used a drag and drop tool to create the integrations and then used them in your Workflows. In this release, this process is simplified by introducing the Flow Editor capabilities as FlowServices directly in your webMethods.io Integration project, thus eliminating the need for you to access the Flow Editor to create complex integrations. Click here to see how to enable the FlowServices capability.
Workflows: Click the Workflow link available on a project to go to the Workflows page for the project. The Workflow landing page is also enhanced to improve the usability. You now need to click the icon on the Workflows page to create a new Workflow.
|Publish Projects||The project publish pages have been enhanced to increase the usability.|
|Monitor page enhancements||In earlier releases, you could access the Dashboard, Audit Logs, Activity Logs, and Alert Rules pages through the Monitor tab. In this release, the Monitor tab pages are reorganized in the following categories to improve usability:
|Environments option changes||You can now register new environments and view, switch, and manage existing environments from your tenant home page.|
|Help option changes||The following options are available in this release when you click the Help icon.
|White labeling||You can now apply white labeling on your tenant as per your company brand identity and customize your tenant theme using the White Labeling functionality. These settings work at tenant level and only admin users have the permissions to create and modify themes.
This allows you to boost your brand visibility and strengthen customer loyalty.
|Flow Editor and FlowServices||In earlier releases, you could create complex integrations by switching to the Flow Editor using the App Switcher, where you used a drag and drop tool to create integrations.
In this release, this process is simplified by introducing the Flow Editor capabilities as FlowServices directly in your webMethods.io Integration project, thus eliminating the need for you to access the Flow Editor to create complex integrations.
In the Flow Editor, you used a graphical drag and drop tool to create integrations. You set up your integrations by plugging blocks together in the workspace and coding concepts were represented as interlocking blocks. In the FlowServices editor, you now can easily build a FlowService by adding steps and selecting the constructs including Applications, Controls, FlowServices, and Services from within the steps. The editor is visually enhanced to offer ease of use and is more interactive. A FlowService contains flow steps, which is a basic unit of work that webMethods.io Integration interprets and executes at run time.
After you enable the FlowServices capability, you can create complex and advanced integration scenarios involving multiple application endpoints and then include the FlowService in a Workflow.
|webMethods.io Flow Apps||The Flow Editor has been renamed to webMethods.io Flow Apps in this release. You can connect to a database using the Database Application. The Database Application allows you to perform database operations with cloud databases using a JDBC driver.
Use the Flat File Application to translate documents into and from flat file formats. To set up the translation, you create the definition and structure of the Flat File Application, which is called a flat file schema. The schema also contains the instructions for parsing or creating the flat file and defines how to identify individual records within a flat file and what data is contained in each of those records.
|Migrating Flow Editor Integrations||If you have created integrations in the Flow Editor, you can migrate those integrations to the same project in FlowServices using the Migrate Integrations functionality.|
|APIs||webMethods.io Integration allows you to write integration logic to integrate different types of applications. This logic can be exposed to the external world using APIs.
In the earlier release, you could create only REST APIs from the webMethods.io Integration user interface. In this release, you can also create SOAP APIs from scratch or by using a WSDL file from the webMethods.io Integration user interface. A SOAP API exposes one or more FlowServices as operations, so each operation in a SOAP API corresponds to a FlowService.
SOAP APIs and REST APIs are now both grouped under the APIs category for improved usability.
|Tenant credentials for webhook authentication||You can now secure your webhook by adding tenant credentials authentication to it. This will require the user of the webhook to specify the tenant credentials first, before sending an execution request.|
|Connectors||All connectors are now grouped under the new Connectors category for improved usability. You can create Accounts by clicking on a connector available on the Available Connectors panel.
The connectors are also grouped and available when you start creating a Flow Service. Flat File Applications created in the Flow Editor are available as Flat File Connectors in the FlowServices panel.
Note: A few connectors are deprecated in this release. A deprecated connector displays the Deprecated label just below the connector where ever it appears in the user interface. Deprecated connectors will continue to work as before and are fully supported by Software AG. If you are using deprecated connectors in your existing Workflows and/or FlowServices, they will work as expected. No new feature enhancements will be made for deprecated connectors. If you are creating new Workflows or FlowServices, it is recommended to use the provided alternative connectors instead of the deprecated connectors. The deprecation is applicable only for Actions. The deprecation is not applicable for Triggers, that is, Triggers are supported for both deprecated and alternative connectors. For the list of triggers, see the documentation for alternative connectors.
|New Connectors||The following connectors are added in this release:
|Configurations||In earlier releases, you could access the Webhooks, Accounts, Triggers, and Parameters pages through the Configurations tab. In this release, the Configurations tab pages are reorganized in the following categories to improve usability:
|Rate Limiting for Workflows||Rate limit is the maximum number of requests that you can make to the webMethods.io Integration server in a span of one minute. The rate limit works at the tenant-level and is applicable only for manually run, trigger-enabled, and sync/async webhook-enabled Workflows.|
|Time stamp updates||Any time stamp displayed in webMethods.io Integration is now based on the time zone you have specified in Software AG Cloud.
Note: All time zones available in Software AG Cloud are currently not 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.
|[Support for Transaction-based tenants]||The following types of tenants are now supported:
|Plans for Transaction-based tenants||When you sign up for a webMethods.io Integration tenant, it will be assigned the 30-day Trial plan by default. You can optionally upgrade to the Free Forever Edition, Basic, Advanced, or Enterprise plans based on your requirement by contacting Global Support.
Once your trial period is over, your tenant will be deactivated until you reactivate it by switching to one of the offered plans.