Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace API Connect
Created by Guest
Created on Apr 6, 2022

Allow configurable settings for how large lines of code can be written inside Map Policy (Ref #CS2751743)

Gateway script can be written inside a Map policy to take care of the complexity of the source and target Data structure through Code. But adding lines of codes API will through the below error due to large size of the code..

{ "httpCode": "500", "httpMessage": "Internal Error", "moreInformation": "The assembly Map action failed." }

After checking the DP logs we got this stack trace.

20220322T122723.616Z [0x80a006c7][http-convert][error] : tid(9109953)[] gtid(3c0463ae6239c097008b01c1): temporary:///map/development_sandbox_customer-api_3.0.2_map_6.json:260,8210: The maximum length of a JSON type was exceeded for */ if(contacts.length > 0) out 20220322T122723.616Z [apiconnect][0x88c000c2][apigw][error] apigw(apiconnect): tid(9109953)[request][] gtid(3c0463ae6239c097008b01c1): The map file that is specified in the assembly map action is not valid JSON format. 20220322T122723.616Z [apiconnect][0x88c00023][apigw][error] apigw(apiconnect): tid(9109953)[request][] gtid(3c0463ae6239c097008b01c1): Assembly rule 'development_sandbox_customer-api_3.0.2_main' is interrupted: The assembly Map action failed.. 20220322T122723.616Z [apiconnect][0x00c3004d][apigw][error] apigw(apiconnect): tid(9109953)[error][] gtid(3c0463ae6239c097008b01c1): The assembly Map action failed.

Now the only way to overcome this to increase the size of the inline code of Map policy somewhere in the Product as suggested by Ops team.

Idea priority High
  • Admin
    Nathan Ziemann
    Aug 2, 2022

    To clarify, this was delivered int he DataPower fixpack, which works with the APIC release for container gateways and new X3 appliance. This will be available in other gateway form factors in future as APIC will provide OVA support with Gateway OVA and X2 support. Net is this is deliverd on a supported combination of APIC 10.0.5 and DataPower or greater, as defined in the official support matrix in the IBM Software Product Compatibility Report website.

  • Admin
    Aug 1, 2022

    Hi Sourav,

    This was delivered in by adding a ParseSettings object to the Map Policy configuration, which enables the customer to use whichever JSON parse settings they choose for a particular Map Policy to allow it to take more or less jSON configuration, smaller or larger JSON strings, including the inlined GatewayScript or large inlined schemas.