Additional SOAPCALL logging option
Description
Conclusion
Activity
Kevin Logemann May 19, 2021 at 12:47 PM
Excellent – thanks for the examples.
Anthony Fishbeck May 18, 2021 at 9:08 PM
That same exact syntax doesn't work for accessing the input fields when directly building a record based soapcall.. there may be another way. But you can still build your expression based on what is accessible. Here's an example using getGlobalId.
Anthony Fishbeck May 18, 2021 at 8:46 PM
I could add something about it being the end but it does give you the power to put whatever you need in the expressions yourself.
Anthony Fishbeck May 18, 2021 at 8:43 PMEdited
Here's an example from the ecl test case:
That results in the following log entries:
Kevin Logemann May 18, 2021 at 8:15 PM
Thanks much Tony. This will be a big help for us (we'll be able to dramatically reduce log file content while still getting a start/stop message in the log).
I do have one follow up question about the example you provided, and the mention that it would produce log lines for each record in a dataset being sent to SOAPCALL. Your example seems to imply that something specific to a record in the dataset could be part of the log (e.g., 'record = 1'), or perhaps I'm reading too much into that.
If so, what is the syntax for EXPR1/EXPR2 to reference a field's value from a record of the dataset being sent to SOAPCALL?
It would be helpful to have a SOAPCALL LOG option that would:
1. log a message at the start and end of each SOAPCALL attempt
2. log an expression provided as an argument to identify the call being made