Script Action steps evaluates the inputs differently when testing the action - Known Error

Script Action steps evaluates the inputs differently when testing the action Description Script Action steps evaluates the inputs differently when testing the action. Using the action in a flow/subflow gives different results.

Steps to Reproduce

1. Create a action. Define a String type action input.

2. Add a Script action step, and define a String type step input, map the action input to the step input.

3. Define a String type step output.

4. In the script action, use script to evaluate the step input. e.g.: if (inputs.parm_v_1 != '') outputs.s_out_v_1 = 'not empty' + inputs.parm_v_1; I attached screenshot of the action design.

5. Save the action and click on Test to test the action.

6. Provide no input value, and check the test result. The script step output is "not empty null", which should be empty. I also attached screenshot of the action test.

7. Use this action in a flow, the script works correctly and the input evaluates as empty as expected.

**So the issue is that the action designer tests produces different results compare to using the action in real flows.

Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In and Intended Fix Version fields to determine whether any versions have or are planned to have a permanent fix.