Home » Developer & Programmer » Application Express, ORDS & MOD_PLSQL » communication between two form without reset all variables (APEX 4.0)
|
|
 Re: communication between two form without reset all variables [message #648229 is a reply to message #648224] |
Fri, 19 February 2016 01:12   |
 |
Littlefoot
Messages: 21824
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
The "trick" here is to submit the first page (in order to put its item's value into session state), and then redirect to the second page.
If you use "Redirect to page in this application" as the button's action, it will do as requested - clear the second's page cache, navigate to the second page, but it won't be able to transfer item's value as it isn't stored in session state.
Therefore, here's one option you might try:
- Suppose that the first page's "Create" button is named P1_CREATE
- It should SUBMIT when pressed
- The "Button Request Source Type" should have its default value - "Static Assignment" as it will result with the request name to be equal to button name (i.e. P1_CREATE)
- Create a branch (under the Processing node)
- Branch point: On submit: before processing
- Target type: page in this application
- Page: the second page (suppose its number is "2")
- Request: put the "Create" button's name in here (as it is equal to request), i.e. P1_CREATE
- Clear cache: 2 (i.e. clear the second page's cache)
- Set these items: name the second page's item which should contain the first page item's value. For example, P2_ID
- With these values: name of the first page's item whose value should be transferred to the second page. For example. &P1_ID. (note both ampersand and dot! It *must* be "&ITEM_NAME.")
- When button pressed: P1_CREATE
That should do it. At least, it did for me.
[Updated on: Fri, 19 February 2016 01:14] Report message to a moderator |
|
|
|
|
|
Goto Forum:
Current Time: Thu May 29 10:45:14 CDT 2025
|
] 
Blog
Search
Help
Members
Register
Login
Home
