Input 

Document

• Min: 0

• Max: 1

• Mapper

• Copy

• PLM TC Info

The Object ID and Rich Content of the file that needs to be downloaded from the Teamcenter.

Output

Document

• Min: 1

• Max: 1

• PLM TC Requirement Download Rich Content

• PLM TC Revise

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

Label*

Default Value: Requirement Set Rich Content
Example: Requirement Set 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 Value: N/A
Example: $._id

Dropdown

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

Rich Content*

Default Value: N/A
Example: parseFloat()

Dropdown

Specify the HTML rich content to upload to the requirement/paragraph revision.

Snap Execution

Default Value: Execute only
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.

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.