BRANCH Condition behaviour post Migration from IS Version 10.7 to 10.15

Kailash_Mishra · February 25, 2025, 5:43am

Product/components used and version/fix level:

IS 10.7 to IS 10.15

Detailed explanation of the problem:

Hi All,

We have recently performed IS Migration from 10.7 to 10.15. We have noticed that a BRANCH (Switch on Variable) Condition evaluation is exhibiting different behaviour in 10.15

We have below code in Flow service which worked fine in 10.7 version

getXYZDataOutput is an IS Document which contains a DocumentList named results and in turn results has a number of child string fields.

In 10.7 IS, the condition BRANCH on /getXYZDataOutput/results[0] was working fine, but in 10.15 version even though the getAdapter call returned multiple results successfully still flow goes to default
In 10.15 below variations of the BRANCH conditions are working in 10.15, we are using the Second Condition for now.

BRANCH on /getXYZDataOutput/results (This worked but if results documentList was returned empty still flow would go the the sequence of /.+/ indicating the condition was just checking if a variable with the same name results exist in the pipeline, so we did not use this )
BRANCH on /getXYZDataOutput/results[0]/stringFieldName ( we are using this for now in 10.15 to make the flow work)

Has anyone else faced a similar BRANCH Behaviour change post IS Version Upgrade and if yes how were they able to Resolve or workaround it? Thanks

Error messages / full error message screenshot / log file:

Question related to a free trial, or to a production (customer) instance?

Production Instance

Note : Have raised this on IBM TechXchange FOrum but no response there hence forced to raise here the same under a different Product Tag

webMethods Integration-Server-and-ESB

Holger_von_Thomsen · February 25, 2025, 2:33pm

Hi,

you can try to evaluate the length of the list with pub.list:length service and branch over the outcome:
Length=0 → list is empty
Length>0 → list contains n elements.

Regards,
Holger

Kailash_Mishra · February 25, 2025, 2:59pm

Thanks Holger for the response. Yes your suggestion to first check the size of the Adapter Response List and then action accordingly is also a valid option to put in use

Since other 2 Conditions /getXYZDataOutput/results and /getXYZDataOutput/results[0]/stringFieldName are working instead of /getXYZDataOutput/results[0] so we have for now edited the Condition to /getXYZDataOutput/results[0]/stringFieldName and it is working fine in 10.15

We got info that we need to Apply IS Core Fix 17 so that the Original Condition of 10.7 /getXYZDataOutput/results[0] can work in 10.15 too. Your thoughts on this?

Currently we are in IS Core Fix 16 on 10.15

wMFix.integrationServer.Core_10.15.0.0017-0010.txt (300.6 KB)

Holger_von_Thomsen · February 26, 2025, 12:27pm

Hi Kailash,

it is always recommended to apply latest fixes as soon as possible.

Esp. when the version reaches end of support date, which is not yet the case for 10.15, but will be the case in approx. two years.