Skip to end of banner
Go to start of banner

Teamcenter Requirement Upload Rich Content

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

In this article

Overview

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

Snap Type

The Teamcenter Requirement Upload Rich Content is a Write-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 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 Requirement Download Rich Content

  • Teamcenter 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

  • 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 ValueTeamcenter Requirement Upload Rich Content
Example: Teamcenter 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.

Object ID*

Default ValueN/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 ValueExecute 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 rendering macro 'excerpt-include' : No link could be created for 'Teamcenter BOM Structure Add'.
Snap Pack History

 Click here to expand...

Error rendering macro 'excerpt-include' : No link could be created for 'Teamcenter Snap Pack'.


Related Content

  • No labels