JR63013: YOU SEE A TYPE MISMATCH EXCEPTION

workflow.2102.delta.repository

APAR status

• Closed as program error.

Error description

• When you call a service by using an input variable that has the
  same name as a root client-side human service (CSHS) variable
  but the isList attributes don't match, you receive the following
   type mismatch exception:
   Error: The "Example Service" service failed with the following
  information: com.lombardisoftware.core.TeamWorksException: Type
  mismatch. Value TWObject[(Active: Y), (Type: TYPE_ARRAY),
  (TWClassID: TWClass.d2e5a15a-ea53-4793-9e93-29af5bd80b13),
  (TWClassName: NameValuePair), (Array length: 2), (MetaData:
  objectID=09248c70-9e1d-49cb-b95a-ce2a78fa28f2, dirty=false,
  invalid=false, shared=false, key=null, version=null,
  rootVersionContextID=null, className=null, contentObject=false,
  contentObjectKey=null, contentObjectSequenceNumber=null,
  contentObjectLocale=null, parentCaseId=null,
  parentActivityId=null)] must be of type NameValuePair (TWSYS)
    You may also see the following error in a CSHS service:
    CWLLG0326E: The BPD encountered an error.
  com.lombardisoftware.bpd.runtime.engine.BPDCaughtException:
  Error: The "<service_name>" service failed with the following
  information: CWTBG0029E: The parameter 'params' has an
  unsupported value
  '{"name":"myVar","value":"6","@metadata":{"rootVersionContextI
  D":"2064.7334807e-4c81-41e6-b9eb-09d269583b06T","className":"myB
  O " } }'. Supported values are: 'NameValuePair'
   at
  com.lombardisoftware.bpd.component.flowcomponent.activity.worker
  .BPDActivityWorker.processCompletedTaskOutputs(BPDActivityWorker
  .java:2209)
    PRODUCTS AFFECTED
  IBM Business Automation Workflow
  

Local fix

• Change the variable name in either the service being called or
  in the root CSHS.
  

Problem summary

• The issue occurs because the input variable for a service has
  the same name as a root CSHS variable. The logic that checks for
   shared business objects doesn't consider the isList attribute
  of the variables and, therefore, mistakenly updates the metadata
   for the service input variable.
  

Problem conclusion

• A fix is available or will be available that ensures calling a
  service by using an input variable of the same name as a root
  CSHS variable when the isList attributes don't match works
  without errors.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BUS AUTO WORKFL

• Fixed component ID

  5737H4100

Applicable component levels