Tc Classification Create

Optional.This Snap has at the most one document input view.

The required input of the snap is the Object ID that shall be classified in the Teamcenter with the classification given by the defined Class ID.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is he classified object in Teamcenter.

• Mapper
• Router

Default value: Tc Classification Create

Select the UID (unique identifier) or the Teamcenter adapter ID of the object.

Default value: $._id

Example: $.uid

Refresh object.

Default value: Selected

Example: Unselected

In case of refresh do a deep refresh.

Default value: Unselected

Example: Selected

For basic classification only.

ON: Usage of attribute labels allowed to resolve Teamcenter property.

OFF: Skip Label→ID mapping.

Default value: Unselected

Example: Unselected

Specify the ID of the classification definition you want to apply to the object.

Default value: N/A

Example: classify_docs

Only used for advanced classification. ON: given structured input data is given directly to classification functionality of Teamcenter. Use case e.g. polymorphic classification.

Structure of data, names and IDs have to be correctly build to have success. Deeper knowledge of advanced classification is necessarry.

Default value: Unselected

Example: Selected

Specify the path of the classification attributes in the input document.

In JSON document the content for path can look like this:

"classAttributes":{
		"2013": "1",
		"2014": "2"
	}

Name of the JSON property has to be the technical name of a valid property in Teamcenter datamodel for the given Class ID.

Default value: N/A

Example: $.classAttributes

Select this checkbox to make the Snap look for the name given in Expand Attributes Path in the input document (for example, $expand) or in the Pipeline parameters (for example, _expand), and use that content. Expand Attributes Path then changes to a String field with the default value $.expand. In Pipeline parameters, separate the attribute names with commas.

When deselected, configure Expand Attributes Path as a string or an expression.

Default status: Deselected

Specify the JSON path to the expand attributes in the input document. Expand attributes are the list of attributes that the Teamcenter response must contain. Each name must be the technical name of a valid property in the Teamcenter data model for the expected objects. For example:

"expandAttributes": [
  "item_id",
  "item_revision_id",
  "last_mod_date",
  "object_string",
  "items_tag.uom_tag"
]

Learn more: Configuring Expand Attributes.

Default value: N/A

Example: $.expandAttributes

Select how the Snap represents references and lists of values (LOVs) that Teamcenter returns. The Snap can return them as nested JSON objects instead of flattened IDs and internal values with additional _DISPLAY attributes:

• References become {"_id": …, "UID": …, "_display": …} or null, including inside reference arrays.
• LOVs become {"_value": …, "_display": …} or null, including inside LOV arrays.

The available options are:

• Yes. The referenced object or LOV is a separate JSON object in the result. For example:

  "owning_user": {
    "_id": "TC*User*null***AgKAUUYTZLWoZA",
    "object_string": "user111 (user111)",
    "UID": "AgKAUUYTZLWoZA"
  }

• No. The referenced object or LOV is flattened into attributes on the current result object, and synthetic attributes such as those ending in _DISPLAY are added. For example:

  "owning_user": "TC*User*null***AgKAUUYTZLWoZA",
  "owning_user_DISPLAY": "user111 (user111)"

• Use Default. The Snap uses the default configured for the Snap Pack, which is Yes or No depending on the adapter.tc.snaplogic.expandReferencesAndLovs setting in the teamcenter_snappack.properties file.

Default value: Use Default

Example: Yes