Skip to main content
July 23, 2025
Solved

Issue Passing Parameter in MNI Subprocess

  • July 23, 2025
  • 2 replies
  • 0 views

Hi Team, good afternoon!

I'm facing an issue that I haven't been able to identify the root cause of, and I’d appreciate your help.

Context:
I created a subprocess node and configured it to call a specific process when reached. This subprocess expects two mandatory input parameters:

  • A map array
  • A record-type variable X (which should remain the same across all instances)

The node is configured with MNI (Multi-Instance) to launch one instance per element in the map array, using Spawn All, running all instances simultaneously, and continuing only after all have completed. The subprocess node is also set to Synchronous.

The issue:
When the process runs, only the last instance launched by the MNI receives the record-type variable X correctly. All previous instances receive it as null.

For example, if three instances are launched, only the third one gets the correct value for variable X; the first two receive null.

  • The variable is correctly populated in the parent process.
  • It is passed directly to the subprocess without any transformation.
  • The subprocess parameters are marked as required.

Note: Each instance must receive a position from the parent process's map variable (tp!instanceIndex). This variable is correctly populating all launched instances. The problem is with the variable that must be the same for all instances (pv!envelopeDocusign), which is only populating the last one.

Has anyone experienced something similar or have any ideas on what might be causing this?

Thanks in advance for your support!

Best answer by shubhama926776

It's weird behavior could you try this  

index({pv!envelopeDocusign}, 1, null) 

instead of passing directly

This forces Appian to evaluate the record for each instance separately

2 replies

shubhama926776
July 24, 2025

It's weird behavior could you try this  

index({pv!envelopeDocusign}, 1, null) 

instead of passing directly

This forces Appian to evaluate the record for each instance separately

July 24, 2025

It worked, thank you very much [mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05]