Symptoms

FPS requires a mapping between the input field and it's json path target

Impact

FPS can't handle this parameter because there are 2 json paths mapping options and only one option can be configured.

Conditions

A single form field is mapped to multiple JSON paths. for example, page contains an input field for parameter 'pswd' if pswd is numeric, application send it as: { "cred" : { "token": 1234} } if pswd is alphanumeric, application sends is as: { "cred" : { "pswd" : "abc123"}}

Workaround

N/A

Fix Information

None

Behavior Change