This content has been marked as final. Show 7 replies
You can create a page hidden item like pxxx_success_message and compute a value for it (your custom value, you can assign the value to this item in your process itself) and in the "Messages" section for the process, in the process success message text box type &PXXX_SUCCESS_MESSAGE.
thank you for your input, but I am not seeing how this will make a difference. I am already placing my custom message in that location, but the &pxxx_var. is not being interpreted into a value, it seems to think the "&pxxx_va." IS the value to display.
Sounds to me like what you have should work. Here's what works for me. I have a PL/SQL Anonymous Block with a Process Point of On Submit - After Computations and Validations. It has Process Success and Process Failure Messages and I put in the value just like you have.
And it works for me.
CANCEL reset succeeded for '&P3_ST.'.
If you have some kind of secure that forces values to be taken literally and not parsed, then everything in your message would be displayed without substitution. Are some regions or fields "escaped" / "not escaped"?
Strange, &Pxxx_ITEM. is the substitution string and used with the html codes. As Howard said, it works for me also. Just a guess, try with the surrounding quotes?
Howard, you're not going to believe this .... I put the name of the page item in caps, and it worked perfectly, just as you said. How silly is that.
So I tired it in reverse .. back to lower case ... AND IT FAILED AGAIN as I originally described.
thanks to both for your contributions to my understanding.
Congrats. I'm going to have to reread the documentation. I was thinking APEX item names were case agnostic like Oracle. Maybe that's not the "case" -- pun intended!
(more) Lower case fails for me as well. Treats as a literal. And when I change an item name to mixed case in it's definition, for example "p3_ITEM", it uppercases when it saves. ???? I wish it could check for this and ask, "Did you intend to use LC here?" But that would require a longer parse.
From Arie Geller's book: http://books.google.com/books?id=YlQ7fxI34wkC&pg=PT222&lpg=PT222&dq=must+apex+items+be+upper+case&source=bl&ots=oXRhpm8dZm&sig=VSOMai9y0Vwa0pKQw2UIxVdwcvA&hl=en&sa=X&ei=_wpfUdgVh7zzBM71gBg&ved=0CGMQ6AEwBg
Note especially the last part!
Case sensitive APEX item namesThere is a greater confusion regarding the case sensitivity of APEX item names.
While defning a new APEX item, we can use any combination of case letters, but the
Application Builder wizard will convert any lower or mixed case item name into an all
Within SQL or PL/SQL code, item names are not case-sensitive (just like any other
bind variables). This is also the case when we are using them in declarative felds
within the Application Builder.
If we want to retrieve an item value using the &ITEM. substitution string notation
then the item name must be in uppercase. Otherwise, the APEX engine will treat
it as a regular string.>
So there you have it!
Edited by: Howard (... in Training) on Apr 5, 2013 1:43 PM