Tc Start Workflow

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

The required input of the snap is the Object ID of the Teamcenter object, Template Name and Process Name for the workflow to be started in the Teamcenter system.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is the workflow is created in the Teamcenter. The resulting document contains the object information for the given object ID.

• Mapper
• Router

Default value: Tc Start Workflow

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

Default value: $._id

Example: $.uid

Specify the name of the template that you want to use for the workflow.

Default value: N/A

Example: TCM Release Process

Specify the name of the process that you want the workflow to follow in the Teamcenter system.

Default value: N/A

Example: TCM Release Process

Specify the subject of the process for the workflow in Teamcenter.

Default value: N/A

Specify the description of the process that you want the workflow to follow in the Teamcenter.

Default value: N/A

Specify the path to fetch the list of target IDs from Snap JSON input document.

Default value: N/A

Specify the path to fetch the list of references from Snap JSON input document.

Default value: N/A

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