Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Taskflows and linear taskflows
  3. Taskflows
  4. Linear taskflows

Taskflows

Taskflows

Back Next

Start properties

Start properties

Use the Start tab to define the binding type and access details for a taskflow.

Taskflow binding

The
Binding
 property defines how a taskflow is invoked and run. You can select one of the following values:
REST/SOAP
If you select the
REST/SOAP
 binding type, you can run the taskflow by using a REST or SOAP endpoint. You can use the
Allowed Groups
 and the
Allowed Users
 fields to define the user groups and users who can run a published taskflow as an API.
The following image shows the binding set to
REST/SOAP
, the
Allowed Groups
 and
Allowed Users
, and the
Parameter Set
 fields:
The image shows the binding set to REST/SOAP, and the Allowed Groups, Allowed Users, and Parameter Set fields.
Event
If you select the
Event
 binding type, the taskflow is invoked when the specified event occurs. For example, a taskflow can be invoked upon an event such as arrival of a file in a file system. The
Event Source Name
 field is available with a
Select
button. Click
Select
to browse and select from a list of file listeners, application ingestion and replication tasks, or database ingestion and replication tasks.
When you define a
database ingestion and replication
 task or
application ingestion and replication
 task, you can select the
Execute in Taskflow
 option to make the task available to add to taskflows.
For more information about file listeners, see
Components
.
For more information about application ingestion and replication tasks, and database ingestion and replication tasks, see
Data Ingestion and Replication
.
The following image shows the binding set to
Event
, the
Event Source Name
, and the
Parameter Set
 fields:
The image shows the binding set to Event, and the Event Source Name and Parameter Set fields.
After you publish a taskflow, you cannot edit the binding details. You must unpublish the taskflow to edit the binding details.

Taskflow access

If the taskflow uses the
REST/SOAP
 binding type, you can define the user groups and users who can run a published taskflow as an API in the
Allowed Groups
 and the
Allowed Users
 fields. If a user falls into either of these categories, the user will have access to the taskflow service URL at run time.
If you do not configure either the
Allowed Groups
 field or the
Allowed Users
 field, Data Integration does not generate the taskflow service URL. You can run and schedule the taskflow. However, you cannot run the taskflow as an API.
The
Allowed Groups
 and the
Allowed Users
 fields define the access details for running a taskflow as an API. To configure permissions for running a taskflow from the taskflow designer or invoking a taskflow through a file listener, you must create a role in Administrator and assign the required permissions.
Configure the following properties:
Allowed Groups
Defines the groups that have access to the taskflow service URL at run time.
Use the
Allowed Groups
 option when you want a group of users to have access to a taskflow service URL. For example, you have a group called 'Order Approvers'. If you enter
Order Approvers
 in the
Allowed Groups
 field, all users within the group will have access to the taskflow service URL.
The following image shows the Order Approvers group added to the
Allowed Groups
 field:
This image shows the Allowed Groups field with the group Order Approvers. The Allowed Users field is empty.
You can specify more than one group in the
Allowed Groups
 field.
If a taskflow uses the
Allowed Groups
 or the
Allowed Users
 fields, you can use one of the following ways to invoke the taskflow through a REST client such as Postman:
  • Use basic authentication, and enter the user name and password.
  • Use session ID in the HTTP header to invoke the taskflow without providing the user name and password.
For example, to invoke a taskflow service URL using Postman, authenticate the GET request in one of the following ways:
  • Use basic authorization and specify the Informatica Intelligent Cloud Services user name and password.
    For example: 
    GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name>
Accept: application/json
Authorization: Basic Auth
username: <Informatica Intelligent Cloud Services user name>
password: <Informatica Intelligent Cloud Services password>
  • Use the IDS-SESSION-ID in the HTTP header.
    For example: 
    GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name> 
Accept: application/json
IDS-SESSION-ID: <sessionId>
    To get the SESSION-ID, use the Platform REST API version 3 login resource. For more information about the login resource, see
    REST API Reference
    .
Allowed Users
Defines the users that have access to the taskflow service URL at run time.
Use the
Allowed Users
 field when you want a specific user to have access to the taskflow service URL. The following image shows a user
jsmith
 in the
Allowed Users
 field and the group
Order Approvers
 in the
Allowed Groups
 field:
This image shows the Allowed Groups field with 'Order Approvers' and the Allowed Users field with 'jsmith.'
Users in the Order Approvers group and the user jsmith will have access to the taskflow service URL.
You can specify more than one user in the
Allowed Users
 field.
If a taskflow uses the
Allowed Groups
 or the
Allowed Users
 fields, you can use one of the following ways to invoke the taskflow through a REST client such as Postman:
  • Use basic authentication, and enter the user name and password.
  • Use session ID in the HTTP header to invoke the taskflow without providing the user name and password.
For example, to invoke a taskflow service URL using Postman, authenticate the GET request in one of the following ways:
  • Use basic authorization and specify the Informatica Intelligent Cloud Services user name and password.
    For example: 
    GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name>
Accept: application/json
Authorization: Basic Auth
username: <Informatica Intelligent Cloud Services user name>
password: <Informatica Intelligent Cloud Services password>
  • Use the IDS-SESSION-ID in the HTTP header.
    For example: 
    GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name> 
Accept: application/json
IDS-SESSION-ID: <sessionId>
    To get the SESSION-ID, use the Platform REST API version 3 login resource. For more information about the login resource, see
    REST API Reference
    .
Parameter Set
Defines the parameter set to provide values for the taskflow input parameters.
The parameter set contains sections and parameters at the taskflow level and are uploaded on the Informatica managed cloud-hosted repository using the ParamSetCli utility.
For more information about parameter set, see Parameter set documentation.
0 COMMENTS
We’d like to hear from you!
Natalia Suchocka - May 06, 2025

Hello! 
Is this part true in the 'Taskflow access' that 'If you do not configure both the Allowed Groups and the Allowed Users fields, Data Integration does not generate the taskflow service URL. You can run and schedule the taskflow. However, you cannot run the taskflow as an API.'? Cause it looks like ANY of these two (Allowed Users OR Allowed Groups) should be configured to generate taskflow's URL and run a taskflow using the API call.

Informatica Documentation Team - May 07, 2025

Hi Natalia,
We’re happy to let you know that we addressed your feedback in the documentation.
Thanks,
Informatica Documentation team