Tc Query

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

The required input of the snap is the Query Key and query criteria defined for saved query in Teamcenter.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is the result of the saved query execution from Teamcenter.

• Mapper
• JSON Splitter

Default value: Tc Query

Specify the key name of the query that you want the Snap to execute in Teamcenter.

Default value: N/A

Example: Item Revision…

Specify the maximum number of results that you want in the output of the query. (0 for unlimited)

Default value: 0

Example: 10

Use manual result limit approach to handle read access problems.

Default value: Unselected

Example: Selected

Specify the JSON path of the attributes in the JSON input document which shall be used as query criteria.

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

"attributes": {
            "Type": "Part Revision",
            "ModifiedAfter": "2025-01-01T00:00:00Z"
        }

Names of the JSON properties have to be valid properties for the defined Saved Query in Teamcenter.

Default value: N/A

Example: $.attributes

Result can contain multiple elements, and these can be given back in one document containing “result” object with list of elements or as multiple documents for each element.

• selected

  output document contains all elements in one document.

• unselected

Response contains document for each element.

Works not in Ultra Tasks

Default value: Unselected

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