This content has been marked as final. Show 3 replies
Create a copy of the "Process Row of..." process for each type of DML message you want to create.
Edit each process and set the "Allowed Operations", "Process Success Message", and "When button pressed" fields...
Name: Process Row of TABLE (Create)
Allowed Operations: Insert
Process Success Message: New record created
When Button Pressed: CREATE (Create)
Name: Process Row of TABLE (Update)
Allowed Operations: Update
Process Success Message: Reacord has been updated
When Button Pressed: SAVE (Apply Changes)
Name: Process Row of TABLE (Delete)
Allowed Operations: Delete
Process Success Message: Record deleted
When Button Pressed: DELETE (Delete)
Here is another approach. Create a hidden item e.g. P100_SUCCESS_MSG. It should be unprotected. In a post submit computation or process, set the text of the item based on the REQUEST. For example an after submit computation based on a query:1 person found this helpful
Next, in the DML process, make the DML success message something like this:
select decode(:REQUEST, 'CREATE', 'New record created', 'SAVE', 'Record has been updated', 'DELETE', 'Record deleted') ) success_msg from dual
You can also add html tags to make the message fancy, or maybe include the primary key value or some other item from your page.
Action processed: &P100_SUCCESS_MSG.
Edited by: JackieW on Apr 1, 2013 11:54 AM (spelling)
Thanks, JackieW, that's exactly what I need!
I created application level hidden item and 'after submit' computation also on application level, works like a charm!
Edited by: user1007 on Apr 2, 2013 8:49 AM