GET_REST_VALUE question - Changes on getting value after the upgrade to 8.11

Hi,
I had a get_rest_value step which was getting some the content for an XML response. In order to get the text of child nodes, I was giving the path of the parent not and it was working fine. Now, after the upgrade to 11.0, the xpath give me some extra space along with the text of child node.

Blow are details: 
For below body and I want to get child nodes of <prefixes>

so I used "//prefixes" in the xpath of GET_REST_VALUE:

I see that the value get a link break on it:

This used be working fine before the upgrade as below:

0
5 comments
Avatar
Hasib Rostaiee

I was able to put a work around by adding some regex characters to exclude as below:

\n[\s\n]+

However, eventually this may lead to some other issues as we getting multiple values on the same GET_REST command

0
Comment actions Permalink
Avatar
Joseph Hamdan

Hasib,

Would you please confirm whether the response was changed from:
<prefixes>
BB
</prefixes>
to
<prefixes>
<string>BB</string>
</prefixes>
We checked changes that were done and to be absolutely sure we tried it on 8.10.2 and got the same result.

Regards,
Subject7 Team
0
Comment actions Permalink
Avatar
Hasib Rostaiee

Hi Joseph,

There was no code changes however on this web service so the response hasn't been changed. But from how Subject7 was displaying responses, I can't verify response of the tests before upgraded as it was in raw text format but it appears that <String> tag existed. The test just started to fail right after upgrade to 8.11.

The reason I need to used <prefixes> instead of <string> is because sometimes there are 1 <string> element and sometimes there more, so I want to be dynamic and get anything withing the <prefixes> element. 

0
Comment actions Permalink
Avatar
Joseph Hamdan

Hi Hasib,

Just to confirm, what was the Subject7 version you had when it worked correctly without characters excluding?

Regards,

Subject7 Team

0
Comment actions Permalink
Avatar
Hasib Rostaiee

Hi Joseph,
I know it was 8.10+ but don't know the exact version, may be Rex would know that. It's whatever version that NHLBI had before upgrading to the current version.

 

0
Comment actions Permalink

Please sign in to leave a comment.