Service Virtualization

Expand all | Collapse all

How to store a property which cannot change its value after extracting from the filters in multiple loops?

  • 1.  How to store a property which cannot change its value after extracting from the filters in multiple loops?

    Posted Nov 29, 2016 08:45 AM

    How to store a property which cannot change its value after extracting from the filters in multiple loops.

    I want a global filter which can take value from a filter in first run only and after the second run of the loop it will not change the value from the filter thus we can consider it as global filter.



  • 2.  Re: How to store a property which cannot change its value after extracting from the filters in multiple loops?
    Best Answer

    Posted Nov 30, 2016 02:09 AM

    If you need to use this parameter for the subsequent message then 1 way to do this, is to add an assertion to identify which is the first incoming message and go through an additional step to filter the parameter. While the subsequent messages will not go through this step and filter. 

     

    If you just want to keep track of all the parameters, then you can add a step to write to delimited file to act as a log file.