LI79712: MAP CODE RESTRICTION NOT ALLOWING JSON OBJECTS IN VALUE STRINGS

apiconnect-2.7.28
5.0.8.0-APIConnect-Portal-Debian7-20170908-0855
5.0.8.0-APIConnect-Portal-Ubuntu16-20170908-0855.ova
APIConnect_Management_5.0.8.0_20170905-1133_a7fe4cd1d442_c04798a.ova
APIConnect_Management_5.0.8.0_20170905-1133_a7fe4cd1d442_c04798a.vcrypt2
apiconnect-2.7.26
microgateway-1.6.3
5.0.8.0-APIConnect-Essentials-Portal-Ubuntu16-20170908-0855.ova

APAR status

• Closed as program error.

Error description

• The map policy has a restriction of not allowing json objects or
  arrays to be
  referenced by the map action's value string, so
  JSON.stringify(), which takes
  an object as its argument, is not being allowed.
  
  When having an API that consumes a Json payload and the Json
  payload is specified as a Json input to the map policy, a map
  action
  that specifies a value string JavaScript snippet that attempts
  to use a non
  primitive variable (an object or an array) from that input would
  return
  an undefined value which would not create any output map data
  for that action.  For example,
  JSON.stringify($(input.payload.myobject)) or
  $(input.payload.myarray)[0] would not be allowed.
  

Local fix

• No Work-Around
  

Problem summary

• A map input variable in a value string JavaScript snippet that
  was of an object or array datatype would be rejected, causing
  the map action to fail and no output created for that specific
  map action.
  

Problem conclusion

• The fix is targeted for inclusion in IBM API Connect V5.0.6.3
  and V5.0.8.0.
  

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels