LogParams changed behaviour on TC 8.5
Hi there, I've noticed a change in the behaviour of the LogParams object in TC 8.5. We use the OnLogError event to write the details of the error to an external text log. This is useful for ...
Forum Discussion
Hi Ory,
I have discussed the matter with the developers, and they say that there are no plans to modify the LogParams.StrEx value to make it support both the HTML and plain text formats (like the Log.Error operation can do). This would affect the performance of the text execution.
In most cases, if you need to parse the HTML text, it should be sufficient to create a script that will just remove all tags from the text and replace the </br> tag with a line feed.
Unfortunately, this approach will not work for errors with complex data in the Additional Information panel (for instance, for checkpoints that post tables).
I have discussed the matter with the developers, and they say that there are no plans to modify the LogParams.StrEx value to make it support both the HTML and plain text formats (like the Log.Error operation can do). This would affect the performance of the text execution.
In most cases, if you need to parse the HTML text, it should be sufficient to create a script that will just remove all tags from the text and replace the </br> tag with a line feed.
Unfortunately, this approach will not work for errors with complex data in the Additional Information panel (for instance, for checkpoints that post tables).
