Merge Records
By using the Merge Records activity, you can merge already matched records, and also choose to manually merge records. In TIBCO® MDM, match and merge of records is performed as two separate activities. You can locate matching records by using the patterns search. After the matches are found, the output of match activity might be merged.
General
The General tab contains the following fields.
Field | Module Property? | Description |
---|---|---|
Name | No | The name to be displayed as the label for the activity in the process.
The default value is MergeRecords. |
MDM Connection | Yes | The MDM connection resource establishes a connection to an TIBCO® MDM server, allowing the plug-in to communicate with TIBCO® MDM.
Click
If no matching MDM connections are found, click Create Shared Resource to create one. |
Execution Mode | Yes | Select an execution mode. The default option is
SYNCHR.
|
Repository | No | The name of the repository where records are stored.
Click Select to select a repository. Note: When the selected repository model is complex and involves many related repositories, you need to increase the value of the
-Xms and
-Xmx parameters in the
TIBCOBusinessStudio.ini file which is located in the
TIBCO_HOME\studio\version\eclipse directory.
|
Record State | Yes | The state in which the available records are merged. The default option is
Confirmed.
|
Command Qualifier | Yes | The qualifier of the command. The default option is
Validate/Process.
|
File Type Attributes | Yes | Specify how to upload a file with file type attributes. This field is available when any attribute defined in the selected repository model is a file type attribute. By default, the attribute is
ATTACHMENT.
|
Description
Provide a short description for the activity.
Input
The following is the input for the activity.
Input Item | Description |
---|---|
PRODUCTID | ID of the record to be merged. You must specify PRODUCTID of the record to be merged. |
PRODUCTIDEXT | ID extension of the record to be merged. Optionally used to identify a record. |
RecordVersion | Specify the version of the record to be merged. |
Merge Attributes | Specify the merge attributes.
Note: New data types
Long and
URL are supported. The XPath Expression is used to edit complex data types, use the function constructor.
|
Edit Attributes | The set of attributes whose values are edited inline in the request. The attribute name is selected as a choice value and the new value is specified in the field. |
Relationship | Specify any one of the following ActionTypes:
The child record must exist in the target repository for the relationship. Only new relationships are created. The root record information is provided as part of parent ID, extension, and version number. For the child repository, specify the details of the related record to be added, modified, and deleted while merging. |
Output
The following is the output for the activity.
Output Item | Description |
---|---|
Result | The result of a transaction to indicate whether the command has succeeded or not.
Success does not mean the successful completion of the command. However, a failure does mean that the command is aborted. This element also captures details such as Result, EventID, EventStatus, EventResult, Description. |
Response | Detailed information of the repository and ResultList:
|