Appsplus panel macro confluence macro | ||
---|---|---|
| ||
**Delete Before Publishing**
|
In this article
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Overview
You can use this Snap to update a classification instance with new or changed values of the class attributes. Class attributes are the properties or characteristics associated with a specific class within a classification structure. They define the information that applies to objects categorized under that class in Teamcenter's classification module.
...
Snap Type
The <Snap name> Teamcenter Classification Update Snap is a Read/Write/Parse/Transform/Flow/Formatwrite-type Snap that reads/fetches/writes/parses/executes/transforms/calls/creates… updates the existing classification in Teamcenter.
Prerequisites
Valid client ID.
A valid account with the required permissions.
None.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Works in Ultra Pipelines if....
Does not support Ultra Pipelines.
Limitations
None.
Limitations and Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description | |||
---|---|---|---|---|---|---|---|
Input Document Binary | Binary or Document |
|
| Requires the EDI data and internal ID as a JSON document. | Output | Document Binary Binary or
| The Object ID and Classification attributes to the fetch the required Classification from the Teamcenter software. |
Output | Document |
|
| The EDI transaction ID and order confirmation
| The updated Classification. | ||
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:
Learn more about Error handling in Pipelines. |
Snap Settings
...
data | {"features":["title","icon","rounded","collapsible","border"],"title":"Documenting Fields Based On Data Type/UI Element","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false} |
---|
**Delete Before Publishing**
Choose from the following sentences to document specific field types.
Drop-down lists/Option Buttons (radio buttons):
You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.
<State what the option should do in this field>. The available options are: <bullet list of LoVs>
Specify the Salesforce API to be used. The available options are:...Select the <category> that you want to use. Available options are...
* Option 1<italicized>. <third person singular form of the verb>
* Option 2<italicized>. <third person singular form of the verb>
Select the API that you want to use. Available options are:
Bulk API. Sends the Snap execution request details as a bulk API call.
REST API. ...
OR
Select one of the three following modes in which the Snap executes:
* Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then 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 downstream from it.
Check boxes:
If selected, <Snap behavior>.
If selected, an empty file is written when the incoming document has no data.If selected, <behavior>. If not selected/Otherwise, <behavior>
Use "If not selected" if the first sentence is long.
If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property.Select to <action>
Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
Select to execute the Pipeline during validation.
Text Fields
...
Info |
---|
|
Field Name | Field TypeField Dependency | Description | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Label* Default Value: ELT Database Account Teamcenter Classification Update | 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. | Number of records||||||||
Object ID*
Default Value: $._id | String/Expression | Sampling Type is Number of records. | Enter the number of records to output. | fieldset Name | Field 1* Default Value: <value> or None. | String | Debug mode check box is not selected. | Field 2 Default Value: <value> or None. | String | NoneSelect the UID (unique identifier) or the Teamcenter adapter ID of the object. | |
Classification attributes path Default Value: N/A | String/Expression | Specify the path of the classification attributes in the input document. | |||||||||
Classification attributes | Specify the table of attributes to set on the classification you want the Snap to create in the Teamcenter software. Each atribute must be specified as a new row. Click to add a row. | ||||||||||
Name* Default Value: N/A | String | Specify the name of the attribute. | |||||||||
Value* Default Value: N/A | String | Specify the value of the attribute. | |||||||||
Snap Execution Default Value: Execute Only | Dropdown listN/A | Select one of the following three modes in which the Snap executes:
|
Troubleshooting
...
Error
...
Reason
...
Resolution
...
Account validation failed.
...
The Pipeline ended before the batch could complete execution due to a connection error.
...
Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
Examples
Excluding Fields from the Input Data Stream
We can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:
<screenshot of Pipeline/Snap and description>
Download this Pipeline.
Downloads
Info |
---|
|
Attachments | ||||
---|---|---|---|---|
|
...
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Snap Pack History
Expand | ||||
---|---|---|---|---|
| ||||
|
...
|
...
Related Content
Endpoint Doc Link 1
Endpoint Doc Link 2
Endpoint Doc Link 3
...