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 MDM server, allowing the plug-in to communicate with MDM.
Click
to select an MDM connection.
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.
- SYNCHR: The client invokes a service, and waits for the completion of the workflow execution.
- ASYNCHR: The client invokes a service, but does not wait for the completion of the workflow execution.
|
Repository
|
No
|
The name of 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.
- Confirmed: Merge confirmed records.
- Unconfirmed: Merge unconfirmed records.
|
Command Qualifier
|
Yes
|
The qualifier of the command. The default option is
Validate/Process.
- Validate/Process: Validate records, save them, and initiate the New Record Introduction Edit workflow.
- Validate/NoProcess: Validate records, and save them without initiating the New Record Introduction Edit workflow.
- NoValidate/Process: Save records without validation, and initiate the New Record Introduction Edit workflow.
- NoValidate/NoProcess: Save records without validation nor initiation of the New Record Introduction Edit workflow.
|
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.
- ATTACHMENT: Indicates that the client sends the file as SOAP attachments to the MDM server. The file name must be a valid path so that it can be attached to the SOAP request.
|