After upgrade plugin Parameterized-Remote-Trigger from 3.1.5.1 to 3.1.6.1

the child job is caused with incorrect parameter

Everything works properly in Freestyle-type(with plugin version 3.1.6.1) job

and the issue with Pipeline-type (with plugin version 3.1.6.1) job

In my pipeline job I use the next parameters:

parameters: """
BRANCH_NAME_APP=${BRANCH_NAME_APP_CORE_SERVICE}
BRANCH_NAME_INFRA=${BRANCH_NAME_INFRA}
ENV_TYPE=${ENV_TYPE}
DEPLOY_ENABLE=${DEPLOY_ENABLE}""", 

Then after building with the parameters parent's job
For, example

BRANCH_NAME_APP=staging-dev-test
BRANCH_NAME_INFRA=master
ENV_TYPE=feature-3
DEPLOY_ENABLE=true 
 

In the console parent job I see call the child job(k8s-base-downstream-core-service-MONOLITH) with correct values:

##############################################################################
Parameterized Remote Trigger Configuration:
- job: k8s-base-downstream-core-service-MONOLITH 
- remoteJenkinsName: Jenkins-MyCompany
- parameters: { BRANCH_NAME_INFRA=master, BRANCH_NAME_APP=staging-dev-test, ENV_TYPE=feature-3, DEPLOY_ENABLE=true}
- blockBuildUntilComplete: true
- connectionRetryLimit: 5
- trustAllCertificates: false
##############################################################################

However, the child job is started with its default parameter values and ignores those parameters passed via the parent job

Moreover, when I try to generate a Pipeline snippet in Pipeline Generator I get such error:

no public field 'parameterFile' (or getter method) found in class org.jenkinsci.plugins 

I have attached appropriate logs for pipeline generator

When the plugin is downgraded to version 3.1.5.1 the issue is resolved (as the pipeline job as and pipeline generator work properly)