Tc File Get Downloadable

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

The required input of the snap is the Object ID of an element in Teamcenter.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is the dataset relations for the object from Teamcenter.

• Mapper
• JSON Splitter

Default value: Tc File Get Downloadable

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

Default value: $._id

Example: $.uid

Specify the JSON path of the values for primary relations which shall be expanded for related Dataset elements in the JSON input document. In JSON document the content for path can look like this:

"relations":[
      "IMAN_specification",
      "TC_Attaches"
    ]

Name of the relations have to be technical names of valid relations in Teamcenter datamodel.

Default value: N/A

Example: $.relations

Select the mode in which you want to showcase the results. The options available are:

• collect

  output document contains all relations in one document.

• each
  • Response contains document for each relation.
  • Works not in Ultra Tasks
• inline

Prerequisite: An input document is required. It will be enriched with relation information.

Default value: inline

Example: collect

Select this checkbox if you want the Snap to include the relation of the object in the results.

Default value: Unselected

Example: Selected

Select this checkbox if you want the Snap to include nullvalues for downloadables. Usually nullvalues indicate missing access rights.

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