ImportCatalogRecords Parameters and Valid Execution Modes

The value can set using the Configurator (Repository > Catalog Import Error Threshold).

The order of the configuration is: Value specified in workflow file > Value specified in Configurator > Default value.

No

No

• MUTATION (M) — Indicates whether the record ID should be tested for mutations. Records are considered to have key mutation when PRODUCTID or EXT changes over the lifetime of the record. If the flag is not specified, the mutation test is not performed. (True in configurator means M in import option). False is default for Configurator (Optimization > Import Mutation Test Performed).
• DUPLICATE (D) — Indicates that a test for duplicate rows in the import should be performed. If this flag is specified and the same record appears more than once, only the first occurrence is processed and other occurrences are rejected. True in Configurator means D in Import options. True is default in Configurator (Optimization > Duplicate Row Check).

D

C

Default is D.

• CYCLIC (C) — Performs a cyclic check on the new relationship being imported. A cyclic check is very time consuming and should be requested only when data is expected to have cyclic relationships. (True in Configurator means C in import option). False is default in Configurator (Optimization > Cyclic Import Check).

  The Workflow file value will take precedence over the Config file value.

You can use ImportCatalog and EvaluateRuleBase in a single step, in which case, no additional record versions will be created and import will be faster.

To configure this:
Pass the rulebase through the ImportCatalog activity. For example:

<Parameter direction="in" name="Rulebase" eval="constant" type="string">D:\common\ac\rulebase/catalogvalidation.xml</Parameter>

The values to input variables defined in the rulebase can be passed though activity parameters. The names of the parameters must match the declarations in the rulebase.

<declare usage=”input”>

Split/Approval Required
Split/No Approval
Direct Load

• CONFIRMED : If you specify the CONFIRMED value, the imported records are confirmed immediately. When this state is specified, workflow does not require a separate UpdateRecordState activity. You should change the out-of-the-box workflow to skip updateRecordState activity.
• UNCONFIRMED : If you specify the UNCONFIRMED or DRAFT value, workflow may require the UpdateRecordState activity.
• DRAFT : If you do not specify any value, Draft is defaulted.

• NEW: using this option, you can create a new version of a record. This is the default value.
• CORRECT: using this option, you can update the existing record versions. New version is not created, only if the old record version state and new record version state match.
• OPTIMIZE: using this option, you can optimize the best choice between the CORRECT and NEW options. TIBCO MDM automatically decides if a new version should be created.

• NEW (Default): creates a new version
• CORRECT: updates an existing record version, no new version. If policy rule allows correction.
• OPTIMIZE: this is a combination of both NEW and CORRECT. TIBCO MDM automatically decides whether or not a record can be corrected; otherwise a new version is created.

For backward compatibility, outDocument will be the same as InDocument.