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
  • Multidomain MDM 10.3 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. IDC Concepts
  3. Implementation Process
  4. Configuring Controls in the IDD Configuration Manager
  5. IDC Control Overrides
  6. IDC Controls
  7. Embedding Controls

Data Controls Implementation Guide

Data Controls Implementation Guide

Back Next

Format of the Control URL

The format of the control URL is:
http://<host>[:<port>]/bdd/bdc/<controlName>/[sag:<sagName>|sa:<saName>],<key>/<controlType>/component.jsf[?username=<username>&password=<password>&bdd_name=<bddName>]
where:
Parameter
Description
Host
Name of the machine where the Informatica MDM Hub is hosted.
Port
Port number (defaults to port 80 if not specified in the URL).
controlName
Name of the control.
sagName
Name of the subject area group for the data to be displayed. This is required for HM and History controls.
saName
Name of the subject area. This is required for Duplicate Prevention control.
key
Key to the data to be displayed. This has different meaning depending on the control type.
  • Hierarchy Manager and History Controls:
    This can be either of the following:
    “rowid:<rowidValue>”
    OR
    “sourceKey:<sourceKeyValue>,systemName:<systemNameValue>”
  • Duplicate Prevention control:
    This should contain search criteria to perform search for duplicates, values of Hub match columns that will be used for matching:
    “fieldName:<fieldValue>[,fieldName:<fieldValue>]”
     "mc.<matchColumnName>:<v
    alue
    >[, mc.<matchColumnName>:<v
    alue
    >]"
    If match column is based on column of DATE type, then its value must be specified as string in the format 'M-d-yyyy H-m-s' (for example date 'March 17, 2010' should be passed as '3-17-2010 0-0-0')
controlType
For the default control types:
hm
,
history
 or
duplicate prevention
.
username
User name to use to authenticate this request.
password
Password to use to authenticate this request.
bdd_Name
The name of the IDD application to which the control is bound.
  • Any characters in the parameters that are not allowed in a URL must be double encoded (see HTML URL Encoding Reference for details on URL encoding). Double encoding (running the encoding process twice) is requested on purpose as it is needed to allow web server to accept requests containing slashes ("/" and "\") in parameters, when single-encoded, requests containing single-encoded slashes are thrown back by web servers. Only the parameter values should be double encoded.
  • The username, password, and bdd_name parameters are optional and can be used to automatically log a user into the control. This should be used with caution, however, because the URL is not encrypted (even if using HTTPS). Supplying login credentials as parameters can be useful when there is a read-only user account that can be accessed by all users.
0 COMMENTS
We’d like to hear from you!