IBM Support

Type mismatch error occurs if the same complex type exists in both a process and a toolkit

Troubleshooting


Problem

   You run a service and the following type mismatch error occurs.
Caused by: com.lombardisoftware.core.TeamWorksException: Type mismatch. Value TWObject[(Active: Y), (Type: TYPE_PROPERTIES), (TWClassID: TWClass.412c7b86-4fdb-45c1-956c-140ec4894051), (TWClassName: SendToEmailInfo), (Property names: marketerType, marketerName, marketerEmail), (MetaData: objectID=85204963-0842-4616-b077-6637af46feb5, dirty=true, invalid=false, shared=false, key=null, version=null, rootVersionContextID=2064.6f86ecb2-e15c-4f8f-bad7-de1cb2233cfb, className=SendToEmailInfo, contentObject=false, contentObjectKey=null, contentObjectSequenceNumber=null, contentObjectLocale=null, parentCaseId=null, parentActivityId=null)] must be of type SendToEmailInfo (CABR)
	at com.lombardisoftware.client.persistence.TWClass.assertValidValue(TWClass.java:950)
	at com.lombardisoftware.server.core.SymbolTable.assertValidType(SymbolTable.java:626)
	... 61 more
The process was migrated from a Business Process Manager environment to a Business Automation Workflow environment.

Symptom

   In the logged type mismatch error, the same type is listed in the TWClass and the the type mentioned in the clause "must be of type" contain the same class name.  
(TWClassName: SendToEmailInfo) must be of type SendToEmailInfo (CABR)
The error message means that the type SendToEmailInfo is not a match for the type SendToEmailInfo (CABR).

Document Location

Worldwide

[{"Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"ARM Category":[{"code":"a8m0z000000blatAAA","label":"Process and Service Engine"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0;20.0.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
06 June 2022

UID

ibm16426977