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
I can replicate this on 24.4. I suggest to open a support case to discuss this with Appian.
So is there any special conditions that Appian would not parse <p> tags ?
That's the question only Appian can answer.
we would at the very least expect text handling functions to handle all text without bias even if that text contains valid HTML tags.
I also confirmed this behavior in 24.4, and confirmed that the exact same code (but with the letter in question replaced to make it not a valid HTML tag) un-breaks it.