Activities (Tasks)
Constant Names
Generate Error
The master Generate Error activity has a constant name: GenerateError_ESIMaster.
Write Log
The master Write Log activity has a constant name: Write Log_ESIMaster.
Variable Names
<Node Name>_<Field 1>_<Field 2>
Activity naming depends on the type of activity.
The following describes each anticipated node type and how to name it.
Variable Node names
Node
Node Name
Field 1
Field 2
Example
Comment
Read File
ReadFile
File Name without path or targetID information, if applicable.
None, as the node contains the information provided in the file and does no other manipulation of it.
ReadFile_ESIDefa ult_BAPI_MATER IAL_SAVEREPLIC A
Write File
WriteFile
File Name without path or targetID information, if applicable.
None, as the node contains the information provided in the file and does no other manipulation of it.
WriteFile_ESIDeb ugLog
JDBC Update
JDBCUp Date
None, as this is a one-way communication.
The Service it references. Log or CrossReference.
JDBCUpdate_ESI Log_CommitBOM
A few words strung together to give a brief description of what was logged. No underscores.
JDBC Query
JDBCQueRy
None, as this is a one-way communication
The Service it references. Log or CrossReference.
JDBCQuery_Error HandlingCode_Ha ndlingCode
A few words strung together to give a brief description of what is being queried. No underscores.
Node
Node Name
Field 1
Field 2
Example
Comment
JMS Queue Sender
JMSSender
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the JMS Body (no underscores). for example, CBOPart or ESIPostResult.
Everything after the last dot in the queue name (after com.ptc.windchill.esi.) For example, Response.
JMSSender_ESIPo stResult_Result
JMS Queue Receiver
JMSReceiver
Everything after the last dot in the queue name (after com.ptc.windchill.esi.). For example, Response.
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the JMS Body (no underscores). for example, CBOPart or ESIPostResult.
JMSReceiver_Response_ESIResponse
Assumes that there is only one JMS receiver on each queue.
RV Subscriber
RVSubscriber
The Subject Name after com.ptc.windchill.esi: For example, Error.
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the RV Message (no underscores). For example, CBOPart or ESIPostResult.
RVSubscriber_Error_ESIError
Node
Node Name
Field 1
Field 2
Example
Comment
Publish RV Message
RVPublisher
The schema (if no schema is characterized, then use the business object name) from the Process Data column of the Input tab that is being mapped to the RV Message (no underscores). For example, CBOPart or ESIPostResult.
The Subject Name after com.ptc.windchill.esi: For example, Error.
RVPublisher_ESIError_Error
Parse XML
XMLParser
Input Schema into Parser only if the input schema is different than the schema that you are parsing against.
Schema Parsing against: ESI Response.
XMLParser_ESIResponse
Render XML
XMLRenderer
Input Schema into Renderer only if the input schema is different than the schema that you are rendering against. Typically, a map and render are combined, and thus this is the schema of the Process Data column of the Input tab.
Schema Rendering into: WindchillRequest
RenderXML_WindchillRequest
Checkpoint
CheckPoint
WC or SAP interaction schema that was last executed. For example, ESIResponse.
None.
CheckPoint_ESIResponse
Node
Node Name
Field 1
Field 2
Example
Comment
Mapper
Mapper
Input Schema Name - on the input tab, the Schema of the Process Data being used. See XML schemas for a list of the schemas used in Windchill ESI and use the schema name - without the underscores - except when using API's.
Output Schema Name - the schema that is selected on the Output Schema tab, and used to map to the Activity Input column of the Input tab.
Mapper_ESIRespo nse_CBO
In the case where the same schemas are being mapped from input to output, a description field should be included. The description should not have spaces or underscores- only two or three words strung together to describe the activity: Mapper_CB OMaster_C BOMaster_ FilterNoOrg s.
Java Code
Java
Description of what the class does using Windchill ESI Capitalization Notation.
Java_RemoveBina ryCharacters
Generate Error
Error
Process Definition Name without the "PD".
Error_LoggingSer vice
Unsure as to the functionality of this activity.
Call Process
CallProcess
Process Definition Name without the "PD."
(optional) The inputs to the process.
CallProcess_Logging_Service
Node
Node Name
Field 1
Field 2
Example
Comment
Label
A sentence
Label name is what displays as the label on the process definition workspace.
Start
Start
Process Definition Name, without "PD."
None
Start_Logging_Service
End
End
Process Definition Name, without "PD."
None
End_Logging_Service
Null
Null
None
(Optional) Description
Null_SimplifyLogB ranching
Invoke an Adapter Request-Response Sequence
Invoke
The name of the BAPI being invoked.
(Optional) The BAPI previously invoked.
Invoke_BAPI_TRA NSACTION_COMMIT_BAPI_DOCU MENT_CREATE2
Write to Log
WriteLog
Description of what information is being written to the log using Windchill ESI Capitalization Notation.
None
WriteLog_Invoked BAPI_MATERIAL_SAVEREPLICA
Was this helpful?