Fixes are available
APAR status
Closed as program error.
Error description
Map type UNKNOWN to String doesn't work in the Java Script case . Although using the same search alias for variables of different types is invalid/discouraged, a change is being made to lessen the problems exhibited with the javascript TWSearch API with this scenario. The search variable is internally mapped to Unknown type due to the conflicting types, so code is being added to map the returned value to String type when the results of the search are returned to the javascript layer. Otherwise the values for that searchable variable are never returned.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users utilizing Javascript API to create * * saved searches. * **************************************************************** * PROBLEM DESCRIPTION: Defining two or more process * * variables with identical search alias * * values but of different type will * * return with null value when queried. * **************************************************************** * RECOMMENDATION: * **************************************************************** When creating saved searches using Javascript API, the queried results may return with null values if two or more variables are defined with the same search alias. The issue can be seen when the variables of the same search alias are declared as different variable types. The existing saved search, which worked previously, will now return a value of null when executed. When executing this scenario, during runtime the low level engine code will return the variable as type UNKNOWN. The following may be seen in the trace logs with runtime tracing enabled: com.lombardisoftware.server.core.pse.impl.ProcessSearchQueryEngi ne prepareQuery propertyNames[...., businessData.problematicVariable3@Unknown,....] Javascript API code is unable to handle the UNKNOWN type and returns null.
Problem conclusion
Code changes have been made to handle the duplicate search alias and properly return the correct value. An interim fix is available on v7.5.1.1. The fix will be integrated into the next fix pack.
Temporary fix
Comments
APAR Information
APAR number
JR47710
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-06
Closed date
2013-09-26
Last modified date
2013-09-26
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R750 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022