Replacing User Exits in IDD Applications

Replacing User Exits in IDD Applications

Other Ways to Customize the Behavior of an IDD Application

Other Ways to Customize the Behavior of an IDD Application

External calls are only one way to customize an IDD application.
Consider using some of the following features as part of your overall strategy to customize an IDD application:
Action
Feature
Comments
Cleanse or validate data by using Informatica cleanse libraries
Transformations
When you want to cleanse or validate data before a read or write operation, use transformations. You can map fields and specify cleanse functions for the fields.
When you need to cleanse data during a different service or service step, create external calls to Informatica Data Quality instead.
Perform an action from a custom button in the user interface
UI External resource components
You can add a component to the Start page or to an entity view. The component can call an external service and display the results. For example, the component can query a CRM system for information about a customer's last contact with the company or the next best offer for the customer.
Avoid adding a component to write data to a business entity. The user interface does not update to reflect the changed data. Use the existing Save button for writing data.
Enrich master data with data from a third-party provider
DaaS extensions
When users add or edit a business entity, the application checks the service for data related to the entity.
For more information about transformations, external resource components, and DaaS extensions, see the
Multidomain MDM Provisioning Tool Guide
.

0 COMMENTS

We’d like to hear from you!