Tc Classification Get Class Definitions

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

There is no required input.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is a list “result” containing all existing class definitions.

• Mapper
• Router

Default value: Tc Classification Get Class Definitions

Specify the classification to get is an advanced classification. If unselected basic classification is fetched.

Default value: Unselected

Example: Unselected

Appears when Advanced classification is selected.

Node ID. Leave empty to get all.

Default value: N/A

Appears when Advanced classification is selected.

Include details of class definition.

Default value: Selected

Example: Deselected

Appears when Advanced classification is selected.

Include descriptors of class definition.

Default value: Selected

Example: Deselected

Appears when Advanced classification is selected.

Level of classification tree to be expanded. Va.ue -1means to expand all levels.

Default value: -1

Example: 1

Appears when Advanced classification is selected.

Batch size for class node description retrieval. Value -1 means all at once. In some cases Teamcenter with -1 Teamcenter creates errors on loading the data from Teamcenter.

Default value: -1

Example: 2

Appears when Advanced classification and Include descriptors is selected.

Batch size for class descriptor retrieval. Value -1 means all at once. In some cases Teamcenter with -1 Teamcenter creates errors on loading the data from Teamcenter.

Default value: -1

Example: 2

Output will be structured as list of one-level Structure (flatten) or more complex as nested object structure as image of the multi-level Teamcenter Structure.

Default value: Selected

Example: Selected

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