Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

Binary

Binary or Document

  • Min: 0

  • Max: 1

  • Mapper

  • Copy

  • Teamcenter BOM Structure Get

The Revision Rule, Mode and Object ID that needs to be fetched from the Teamcenter software.

Output

Document

Binary

Binary or Document

  • Min: 1

  • Max: 1

  • Teamcenter Classification Create

  • Teamcenter Change Ownership

The multilevel expanded level of the BOM Structure.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

...

Info
  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ((blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the fieldset.

  • Remove icon ( (blue star)): Indicates that you can remove fields from the fieldset.

  • Upload icon ((blue star) ): Indicates that you can upload files.

Object ID*

Field Name

Field Type

Field Dependency

Description

Label*

 

Default ValueTC Structure Get
ExampleTC Structure Get

String

None

The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipelinepipeline.

 

Object ID*

Default Value: N/A
Example: hdj_983

Dropdown

None

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

Revision Rule*

 

Default Value: N/A
Example: 3<1

String/Expression

None

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

Mode*Configure Output

Default Value: Inline deselectedExample: collect

Checkbox

Dropdown

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

  • each

  • inline

  • collect

None

None

Type

 

Type

 

Default Value: N/A
Example: hdj_983

Dropdown

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

Diameter

String/Expression

Configure Output

Specify the name of the Teamcenter type.

Expand attributes path

Default Value: N/A
Example: Diameter attributes1 → item_response

String/Expression

Configure Output

Specify the name path of the Teamcenter typethe expand attributes in the input document.

Expand Attributes

Specify the attributes you want the Snap to fetch from Teamcenter. Each atribute must be specified as a new row. Click (blue star) to add a row.

Name*

Default Value: None.
ExampleItem_response

String

Configure Output

 

Specify the name of the attribute.

Snap Execution

Default Value
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

...