Versions Compared

Old Version 3

changes.mady.by.user Shilpa

Saved on

compared with

New Version Current

changes.mady.by.user Shilpa

Saved on

Key

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

...

Table of Contents
true
minLevel1
maxLevel2absoluteUrl
outlinefalse
styledisc
typelist
printablefalse

Overview

You can use this Snap to upload a rich content stream to either a Requirement or a Paragraph revision.

...

Snap Type

The Teamcenter PLM TC Requirement Upload Rich Content is a Writewrite-type Snap. The content must be provided as a binary input stream into the Snap.

Prerequisites

  • Valid client ID.

  • A valid account with the required permissions.

Limitations and Known

...

Issues

None.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Binary

  • Min: 1

  • Max: 1

  • Mapper

  • Copy

Teamcenter

  • PLM TC Requirement Set Rich Content

The Object ID and Content-Type of the file that needs to be uploaded from the Teamcenter. The content must be provided as a binary input stream into the Snap.

Output

Document

  • Min: 1

  • Max: 1

Teamcenter

  • PLM TC Requirement Download Rich Content

Teamcenter

  • PLM TC Revise

The uploaded rich content file.

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 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.

Snap Settings

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.

Field Name

Field Type

Description

Label*

Default Value: 

Teamcenter

PLM TC Requirement Upload Rich Content
Example:

 Teamcenter

 PLM TC Requirement Upload Rich Content

String

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

Pipeline

pipeline.

Object ID*

Default Value: N/A
Example: $._id

Dropdown

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

Content Type*

Default Value: docx
Example: docm

Dropdown

Specify the type of the HTML rich content to upload to the requirement/paragraph revision. The options available are:

  • html

  • docm

  • docx

Snap Execution

Default Value: Execute only
Example: Validate & Execute

Dropdown

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.

Troubleshooting

...

Error

Reason

Resolution

Object ID does not exist

The object with the specified ID does not exist in the Teamcenter database.

Double-check the ID you are using to ensure it matches an existing object.

Incorrect ID Format

The entered format of the object ID is incorrect.

Teamcenter object IDs often have a specific format, including a prefix that identifies the object type and a unique identifier. Make sure you are using the correct format for object IDs.

Snap Pack History

Expand
titleClick here to expand...

Insert excerpt

Teamcenter

PLM TC Snap Pack

Teamcenter

PLM TC Snap Pack
name

XYZ

Team Center Snap Pack History
nopaneltrue

...

Related Content

...