Adding more inputs into Flow Designer Action even with the limit reached

[matthew_hughes]

One thing that I've noticed when creating a Flow Designer Action, there is a limit to the number of inputs that are allowed. 

Because it this, it means that I've had to create two separate Flow Designer Actions:

I was just wondering if anyone has come across this issue before and if there's a way of combining two Flow Designer Actions into one.

[Dr Atul G- LNG]

Yes, mate. If it reaches above the limit, it means the subflow needs to be 2 or 3, as this can cause a performance issue.

[matthew_hughes]

Hi @Dr Atul G- LNG  So there are no properties or methods that can be used to increase the number?

[Dr Atul G- LNG]

NO , but you can follow solution provided by @Itallo Brandão 

[Itallo Brandão]

Hi there,

To answer your questions directly:

1. Has anyone seen this? Yes. While there is no hard "limit" on the number of inputs, the Flow Designer UI (Action Designer) starts to lag significantly and becomes unmanageable when you have too many individual inputs (like the 40+ you have there).
   
   

2. Is there a way to combine them into one? Yes. The best way to handle this amount of data in a single Action is to stop using individual String/Boolean inputs for every field.
   
   

   The Solution: Use a JSON Object Instead of creating 50 separate inputs, create one input:

   • Name: payload

   • Type: JSON (or String)
     
     

   How to implement:

   1. Pass all your data (Name, Description, Owners, etc.) as a single JSON object from your Flow.

   2. In your Action's Script Step, parse this single input and update the record dynamically:

   (function execute(inputs, outputs) {
       var gr = new GlideRecord('cmdb_ci_business_app');
       if (gr.get(inputs.bus_app_sysid)) {
           var data = JSON.parse(inputs.payload);
   
           // Automatically updates any field sent in the JSON
           for (var key in data) {
               if (gr.isValidField(key)) {
                   gr.setValue(key, data[key]);
               }
           }
           gr.update();
       }
   })(inputs, outputs);

   This allows you to update 5, 50, or 100 fields using just one Action, solving both the split-action issue and the UI lag.
   
   
   If this response helps clarify the platform behavior and solve your requirement, please mark it as Accepted Solution. This helps the community grow and assists others in finding valid answers faster.

Best regards,
Brandão.