Tc Resolve

This Snap has exactly one document input view.

The required input of the snap is an object or a list of objects including uid or a query.

Possible UID information input variants are listed below. Object Path* field would contain object for this example.

UIDs in Teamcenter are as the name says UNIQUE. The UIDs in documented examples only exist in our Teamcenter system as expected for our example. Same is valid for Adapter ID "_id" since its base is the UID.

[
    {
        "object": [
            {
                "uid": "QUDAAA6jZLWoZA"
            },
            {
                "UID": "ALGAAA6jZLWoZ2"
            }
        ]
    }
]

In case default query can be used to retrieve objects attributes defined in Teamcenter query can be given as input. Some combinations are:

[
    {
        "object": [
            {
                "item_id": "000264",
                "item_revision_id": "A"
            },
            {
                "item_id": "000264",
                "item_revision_id": "A",
                "object_type": "Part Revision"
            },
             {
                "item_id": "00026*",
                "item_revision_id": "A"
            }
        ]
    }
]

In case another query shall be used to resolve objects _query object including _queryKey and possibly attribute to query-attribute Mappings.

[
    {
        "object": [
            {
                "item_id": "000265",
                "item_revision_id": "B",
                "_query": {
                    "_queryKey": "Item...",
                    "item_id": "ItemID"
                }
            },
            {
                "ItemID": "000265",
                "_query": {
                    "_queryKey": "Item..."
                }
            }
        ]
    }
]

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is the resolved object(s) and an error status JSON object.

• Mapper
• Router

Default value: Tc Resolve

Specify the path in the JSON input document to the information for the object.

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

[
  {
    "uid": "AGLAApgK7hAnmD"
  }
]

UIDs in Teamcenter are as the name says UNIQUE. The UIDs in documented examples only exist in our Teamcenter system as expected for our example. Same is valid for Adapter ID "_id" since its base is the UID.

Default value: N/A

Example: $

OFF: Result contains resolved information.

ON: Result will be enriched with “original” object including input document information.

Default value: Unselected

Example: Unselected

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