Categories
Find answers to some of the most common questions in webMethods.io Integration.
Find answers to some of the most common questions in webMethods.io Integration.
To delete a project, do the following:
Locate the project you want to delete.
Click on the vertical ellipsis icon (or three tiny dots) located beside the project name and click Delete.
No. The feature is currently not available.
In each tenant, a system-generated Default project is already available. You cannot create another project with the same name.
This could be due to one of the following reasons:
No. A user with custom role cannot create a new project, nor can the user update or delete the accessible projects.
You can find the list of predefined connectors supported by webMethods.io Integration under the Connectors section. You can also create custom connectors using the Connector Builder - Node.js CLI or using the Connector Builder for webMethods CloudStreams.
See Troubleshooting tips on Account configurations for some of the most common scenarios you may come across while configuring an Account.
See Account configuration fields for information on the connection configuration fields.
See the Tech Community tutorials related to connectors to browse through the connector related tutorials.
The maximum data size for a single object in Flow Store, Memory Store, and Account Store is 16 MB.
Yes, you can do this by using the the Run Flow action.
Yes. You can build your own actions for a particular service using the Node.js block or Connector Builder.
Yes. The default timeout period for every workflow is 3 minutes.
Yes. Default memory limit for your workflow is 256 MB.
Yes. Click here to learn how to do it.
You can delete accounts created under a specific project by going to the Configurations > Workflow > Connections page.
You can also delete the triggers set up under a specific project by going to the Configurations > Workflow > Triggers page.
If you do not find a specific connector, action, or trigger, you can either create them yourself using the Node.js block (for creating actions) or Connector Builder (for creating connectors, actions, and triggers) features.
Alternatively, you can get in touch with Software AG Global Support with your requirements. We will add the required connectors/actions/triggers for you.
The FlowServices feature enables you to create complex integrations that require advanced data transformation and custom logic implementation. Here you can easily build a FlowService by adding steps and selecting the constructs including Connectors, Controls, FlowServices, and Services from within the steps. The FlowServices editor is visually enhanced to offer ease of use and is very interactive. FlowServices currently supports a wide range of connectors and comes with several built-in services that makes your job easier. FlowServices provide you with rich data mapping capabilities, a familiar debugging mechanism, a large collection of built-in services, and more.
A FlowService mainly has two parts:
Workflows and FlowServices enable you to automate and optimize tasks based on a set of predefined rules and business logic. These features give you the power to connect apps, devices, and on-premises systems with only clicks and zero code. Although Workflows and FlowServices help you to accomplish the same goal, there are significant differences between both the features.
Click here for information on the differences between Workflows and FlowServices.
FlowServices are made available by default for all tenants.
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.
Click here to learn more.
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.
Note that 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.
Conditional steps are those steps that perform different actions based on the result of evaluated conditions/expressions. Types of conditional constructs include:
The purpose of transformers is to accomplish multiple data transformations on the pipeline data in a single step as compared to using normal steps one after another. Transformers are services that are inserted into and run within a Transform Pipeline step. Transformers act as a collection of normal steps embedded in a single Transform Pipeline step.
Click here to know more about transformers.
Click here for information on how to create a FlowService.
webMethods.io Integration allows you to trigger the execution of a FlowService from an external system. This option provides you with another way to trigger FlowService executions from a software application, for example, a REST client, apart from manual and scheduled executions from the user interface.
Click here to know more.
Click here for information on how to debug a FlowService.
You can edit an existing trigger from the workflow in which it is being used or can edit it from a project by navigating to Configurations > Workflow > Triggers tab.
Click here to know how to do it.
You can add conditions in triggers by using ‘Filters’ option located at the bottom of the Trigger Output Data screen, while configuring the trigger.
Know more about Conditions.
Some triggers constantly check for updates in the external services and run in real time, whereas some triggers check for updates in external services periodically, for example, every five minutes, and hence take more time. The second type of triggers are called Polling triggers and can be identified by the clock sign given beside the trigger service icon.
No, if a trigger is being used in multiple workflows, then any changes made to it will be reflected in all the workflows it is being used in. If you don’t want to change the trigger settings for the rest of the workflows, then it’s advised that you create a new trigger.
You can delete an existing trigger from a particular workflow it is being used in, via the Workflow Settings panel. If you want to delete the trigger permanently from the project, you can do so by navigating to the Configurations > Workflow > Triggers tab.
Click here to know more about it.
You can secure your webhooks by adding basic authentication or appending authentication tokens to webhooks.
Click here to learn more about it.
You can not change the webhook URL link manually; however, you can regenerate the webhook URL for an existing workflow by clicking the Reset Webhook icon in the webhook configuration window.
You can use webhook as a trigger by providing the webhook URL link to third-party applications.
Click here to know more about it.
You can use Return Data on Sync Webhook action in your workflow to send the response of the workflow to the webhook.
You can use AND operator when you want the workflow to proceed only if all the specified conditions are met.
Click here to know how to set up multiple conditions using AND operator.
You can use OR operator when you want the workflow execution to proceed if any of the specified condition is met.
Click here to know how to set up multiple conditions using ‘OR’ operator.
You can use Switch action to define multiple possible execution paths for your workflow. With Switch action, you can add one or more cases. Each case contains one or more conditions and a next step that will be performed if the defined conditions are met. The action also includes a Default case that specifies the action to be executed if none of the condition is met.
Click here to know more about using Switch statement in your workflow.
Audit logs screen is available only for Admin and Owner of the project. If you have been assigned a custom role by the tenant admin/owner, you cannot see the audit logs.
Click here for a summary on webMethods.io Integration iPaaS Security. You can also see the Data Access and Security section in this document for more information.
The OPTIONS method is open for webMethods.io Integration as this is required to run the site. As this is a REST API implementation, the application requires the OPTIONS method to be available for AJAX calls to work.