Tc BOM Structure Create Baseline

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

The required input of the snap is the id of the BOM Head object the baseline shall be created for in Teamcenter.

• Mapper
• Copy

This Snap has exactly one document output view.

The output of the snap is the newly created baseline in Teamcenter.

• Mapper
• Router

Default value: Tc BOM Structure Create Baseline

Specify the _id, a UID (unique identifier) or a Teamcenter adapter ID of the parent element where you want to add the new item to.

Default value: $._id

Example: $.parent_id

Specify the revision rule that you want the Snap to use for the structure creation.

Default value: N/A

Example: : Latest Working

Specify the view type to determine the layout, visibility, and organization of data within Teamcenter. The view type is a predefined set of properties and display settings used to present information about an object or a specific aspect of the system's functionality.

Default value: N/A

Example: View

Select this checkbox to establish a relationship between the new created object and the users Newstuff folder.

Default value: Unselected

Example: Unselected

ON: create a precise baseline

OFF: create unprecise baseline

Add a description for baseline revision.

Name of the workflow process template to be used for baselining.

Default value: N/A

Example: TC Default Baseline Process

Name to identify the job initiated during baselining.

Default value: N/A

Example: AutoBaseline

Description for baseline job.

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