webMethods

 View Only
  • 1.  BRANCH Condition behaviour post Migration from IS Version 10.7 to 10.15

    Posted yesterday
    Edited by Kailash Kumar Mishra yesterday

    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.

    1. 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 )
    2. 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



    ------------------------------
    Kailash Kumar Mishra
    ------------------------------



  • 2.  RE: BRANCH Condition behaviour post Migration from IS Version 10.7 to 10.15

    Posted 8 hours ago

    Hi Kailash,

    The issue got resolved in wMFix.integrationServer.Core_10.15.0.0017-0010. 



    ------------------------------
    HARI PRASANNA RAJU CH
    ------------------------------



  • 3.  RE: BRANCH Condition behaviour post Migration from IS Version 10.7 to 10.15

    Posted 7 hours ago
    Edited by Kailash Kumar Mishra an hour ago

    Hi Hari,

    Thanks for your response.

    Currently we are on IS Core Fix 16. As per your shared information, we shall check on Installing IS Core Fix 17 and Test.



    ------------------------------
    Kailash Kumar Mishra
    ------------------------------