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
  • Application Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using App Connections
  9. System Services, Listeners and Connectors
  10. Designing Human Tasks

Design

Design

Back Next

Decision Step

Decision Step

A Decision step allows a
process
 to take different paths depending on the value of the field.
You can configure the following Decision step properties:
Name
The name of the Decision step. The name can contain only alphanumeric characters, underscores (_), spaces, and Unicode characters.
Decision
The process takes a decision based on the fields, formulae, and paths you define here.
Use one of the following option to specify the path:
  • Field.
     Select an input field, output field, or temporary field from the list of fields you defined under the
    Start
     step.
    Enter conditions and values that you want the Decision step to base a decision on.
    The conditions available depend on the field that you select.
    For example, if you select a field of type
    Simple
    Text
    , the following conditions are available:
    • Contains
    • Equals
    • Starts with
    • Ends with
    • Starts with any of
  • Formula.
     Open the formula editor to create a complex expression.
    You can define a path and set appropriate conditions. You can also evaluate simple and complex expressions directly in the Decision step with no dependency on the prior steps.
    When you select the
    Formula
     option and define the expression, the following conditions are available:
    • Contains
    • Equals
    • Starts with
    • Ends with
    • Starts with any of
    • Not equal to
    • Less than
    • Less than or equal to
    • Greater than
    • Greater than or equal to
    However, you must select the appropriate conditions based on the return type of the functions used in the expression.
    The following table describes the supported and unsupported conditions based on the return types:
    Return type
    Supported conditions
    Unsupported conditions
    String and Boolean
    Contains
    Equals
    Starts with
    Ends with
    Starts with any of
    Not equal to
    Less than
    Less than or equal to
    Greater than
    Greater than or equal to
    Number and Integer
    Contains
    Equals
    Starts with
    Ends with
    Starts with any of
    Not equal to
    Less than
    Less than or equal to
    Greater than
    Greater than or equal to
    None
    DateTime
    Contains
    Equals
    Starts with
    Ends with
    Starts with any of
    Not equal to
    Less than
    Less than or equal to
    Greater than
    Greater than or equal to
    Default is
    Field
    .
You can enter text values against the conditions you select.
You can add multiple conditions to a Decision step. Each condition is a potential data path.
For each path that you add, a corresponding branch appears on the UI. Drag branches to rearrange the order in which the branches appear on the UI.
Most Decision steps have an Otherwise path. This path handles execution if no data meets the conditions in your tests.

Evaluating Paths

A process evaluates conditions based on the criteria you specify. Ensure that you construct paths with non-intersecting conditions.
For example, you create a Data Decision step with the following paths:
  • Path 1: Field less than or equal to 100.
  • Path 2: Field less than or equal to 75.
  • Path 3: Field less than or equal to 25.
  • Path 4: Otherwise
If the integer field for which the Data Decision step was created has a value of 25, the Data Decision step takes path 1. This is because 25 is less than 100 and path 1 is the first option.
To ensure that the Data Decision step follows the "Field less than or equal to 25" path, re-create the paths with the following criteria:
  • Path 1: Integer between 0 and 25
  • Path 2: Integer between 26 and 75.
  • Path 3: Integer between 76 and 100.
  • Path 4: Otherwise
Important
: The process evaluates conditions in a top-down manner. Ensure that the Otherwise branch is the last path.
A Decision step can lead to another Decision step. For example, a branch could run if an annual income exceeds $100,000. The next decision test along the same path could test if the city is Boston, or otherwise. Using this technique, you use Boolean AND logic because you base the test for the second condition on the true branch of the first condition. In this example, you use the Decision step to set the condition "Annual Revenue exceeds $100,000 AND city is Boston".
Similarly, to support Boolean OR logic, you can add a test for the second condition on any branch.
0 COMMENTS
We’d like to hear from you!