Vince,
You can use a pseudo-element for the #FOSI tests so the savetext and #FOSI aren't in the same e-i-c.
Good luck!
Suzanne Napoleon
www.FOSIexpert.com
Vince,
I know you've got some responses on this, but here's a thought. What all have said thus far is fairly correct. The help Clay mentions shows the example you're looking for alright. The problem is that it doesn't mention the timing part of it. With, ACL, you can achieve this functionality, but it's somewhat over-kill unless there is no way to test after the <title> elelment. As Brandon (I believe) mentioned you have to get the variable filled with the element content before the element you actually test it in. This goes back to the old problem centered around the fact the FOSI moves forward testing as it goes. If it hasn't reached an element, or its content, it doesn't exist yet.
The <title> element can do the savetext to your variable. However, the next elment outside the <title> is where you need to do your test, and it will be reliable with "#ANY" or "#NONE" as the values to test for.
If you can't wait until after the element, meaning you have no other element to use, you will need to do an ACL function call using attloc="system-func" as your <att> test. The ACL function can then get the current OID, get its contents, and then evaluate it returning a value to stuff in a variable to display within the <title> element. Obviously, this is much more complicated.
Hope this helps,
Bob