Hi All,
For any reason I can't imagine, if you run this instruction in a rule;
fn!extract("<a>some text</a>","<a>","</a>")
you will get {"some text"} as a result, which is what I expected.
But if you run this one
fn!extract("<p>some text</p>","<p>","</p>")
you get nothing as result.
Another example of this strange behaviour:
fn!extract("<l>some text</l>","<",">") returns {"l","/l"}, which is fine
fn!extract("<p>some text</p>","<",">") returns nothing, which is inexplicably to me
Any idea on why is that happenning?. I've tested that on Appian v25.1
Regards!
Discussion posts and replies are publicly visible
This is a known issue. Find the knowledge base item here: community.appian.com/.../kb-1489-the-extract-function-is-unable-to-handle-html-line-breaks
I just realized - this article gets it slightly wrong. It's not that Appian is failing to parse the extract per se - it's that the entire string is being stripped of certain HTML tags (presumably) immediately, before the "extract" operation is even attempted, and then the result of the "extract" works or fails depending on what's left after the HTML tags in question are removed.
For example: