Full Page Rendering?

I have an app with an informational page. At the top of the page is a selectOneChoice with the list of items for which the detail can be displayed.
Using a valueChangeListener on the selectOneChoice, I change the value object in the backing bean that holds the data for the 20+ inputText components on the page. When the value is changed in the list box, the listener method in the bean is called and the value object is changed. However, none of the text fields reflect this change. If I press the browser's refresh button, all of the data is properly displayed.
I "solved" the problem by setting the partialTriggers property on every inputText to the id of the selectOneChoice. It seems silly that I would have to partially render the whole page just to get a simple update.
Did I miss something? Was there a better way to do this?

Sorry for jumping the gun ...
I created this posting based on my initial posting at
can't reading JSF param from bean
If you look at my original posting, my JSPX page behaves correctly in Firefox but not in IE. In short, a request scope parameter (JSF parameter nested in the commandButton component) is not visible to my backing bean. It appears to be passed correctly in Firefox but when I use IE, the request parameter is not there. I initially thought it was a PPR issue --- maybe it still is?

Similar Messages

ADF UIX Partial page rendering

Hi
I am facing a mysterious problem with partial page rendering in ADF UIX.
My page contains a <header> H1 and inside this there are two headers(H2 and H3).
The partial page rendering is in the header H2 and is working fine.
When i remove the below header H3 the partial page rendering ceases to work and get stuck.
Pasting the full code below. Please suggest.
<?xml version="1.0" encoding="windows-1252"?>

<page xmlns="http://xmlns.oracle.com/uix/controller"
xmlns:ui="http://xmlns.oracle.com/uix/ui"
xmlns:ctrl="http://xmlns.oracle.com/uix/controller"
xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:myTemplate="http://xmlns.oracle.com/xhub"
xmlns:bc4j="http://xmlns.oracle.com/uix/bc4j"
xmlns:data="http://xmlns.oracle.com/cabo/marlin" expressionLanguage="el">


<bc4j:registryDef>

<bc4j:rootAppModuleDef name="XhubRegAM"
defFullName="oracle.apps.snw.tpadmin.server.XhubRegAM"
configName="XhubRegAMLocal" releaseMode="stateful">
<bc4j:viewObjectDef name="TpProfilesRegVO" rangeSize="1" autoCreate="false"/>
<bc4j:viewObjectDef name="UsersRegVO" rangeSize="1" autoCreate="false"/>

<bc4j:viewObjectDef name="IdentifierDomainsView" rangeSize="20"/>

<bc4j:viewObjectDef name="XhubTerritoriesTlView" rangeSize="300"/>
</bc4j:rootAppModuleDef>
</bc4j:registryDef>

<templates xmlns="http://xmlns.oracle.com/uix/ui">
<templateImport source="xhubtpadmin.uit"/>
</templates>
<content>

<dataScope xmlns="http://xmlns.oracle.com/uix/ui"
xmlns:data="http://xmlns.oracle.com/uix/ui">
<provider>

<data name="textSource">
<bundle class="oracle.apps.snw.uicommon.TextProvider"/>
</data>

<data name="adminInfo">
<method class="oracle.apps.snw.tpadmin.webui.AdminInfo"
method="getAdminInfo"/>
</data>
</provider>
<contents>
<document>

<metaContainer>
<head title="${textSource.REGISTRATION}"/>
</metaContainer>
<contents>
<body>
<contents>

<myTemplate:xhubTpAdminPageLayout selectedTab="1">
<contents>

<messageBox automatic="true"/>

<form name="reg" method="POST">
<contents>


<formParameter name="event"/>

<bc4j:rootAppModuleScope name="XhubRegAM">
<contents>

<header text="${textSource.REGISTRATION}">
<contents>

<styledText styleClass="OraInstructionText"
text="${textSource.REG_PAGE_EXPLAIN}"/>

<header text="${textSource.REG_COMPANY_INFO}">
<contents>
<stackLayout>
<contents>

<labeledFieldLayout id="TpPartialDetails" width="80%"
labelWidth="40%">
<contents>
<messageChoice name="OracleAppsCustFlag"
prompt="Oracle Apps Customer"
required="yes" statePreserved="true"
selectedValue="${ui:defaulting(uix.pageProp.OracleAppsCustFlag, 'select')}">
<primaryClientAction>
<firePartialAction event="buyorsup"
targets="TpPartialDetails"
formSubmitted="true"
unvalidated="true"/>
</primaryClientAction>
<contents>
<option text="-select-" value=""/>
<option text="${textSource.YES}" value="Y"/>
<option text="${textSource.NO}" value="N"/>
</contents>
</messageChoice>
<messageTextInput prompt="${textSource.ORACLE_CSI_Q}"
name="OracleCsi"
text="${uix.pageProp.OracleCsi}"
rendered="${ui:defaulting(uix.pageProp.OracleCsiRender, 'false')}"/>
<messageTextInput prompt="${textSource.YOUR_TP_NAME}"
name="TpName"
tip="${textSource.YOUR_TP_NAME_TIP}"
required="no"
text="${uix.pageProp.TpName}"
rendered="${ui:defaulting(uix.pageProp.TradeswithTPRender, 'false')}"/>
<messageTextInput prompt="${textSource.YOUR_TP_ALIAS}"
name="TpAlias"
tip="${textSource.YOUR_TP_ALIAS_TIP}"
required="no"
text="${uix.pageProp.TpAlias}"
rendered="${ui:defaulting(uix.pageProp.TradeswithTPAliasRender, 'false')}"/>
</contents>
</labeledFieldLayout>
</contents>
</stackLayout>
</contents>
</header>

<header text="${textSource.TP_DEFAULT_CONTACT_INFO}">
<contents>
<labeledFieldLayout width="80%" labelWidth="40%">
<contents>

<messageTextInput prompt="${textSource.PASSWORD_PROMPT}"
name="Password" id="Password"
required="yes" secret="true"
maximumLength="32"
text="${uix.pageProp.Password}"/>
<messageTextInput prompt="${textSource.PASSWORD_CONFIRM_PROMPT}"
name="PasswordConfirm"
id="PasswordConfirm" required="yes"
secret="true" maximumLength="32"
text="${uix.pageProp.PasswordConfirm}"/>
</contents>
</labeledFieldLayout>
</contents>
</header>
</contents>
</header>
</contents>
</bc4j:rootAppModuleScope>
<spacer height="10"/>

<inlineMessage required="yes"
prompt="${textSource.REQUIRED_FIELD}"/>
</contents>
</form>
</contents>

</myTemplate:xhubTpAdminPageLayout>
</contents>
</body>
</contents>
</document>
</contents>
</dataScope>
</content>

<handlers>

<event name="continue">
<bc4j:findRootAppModule name="XhubRegAM">
<method class="oracle.apps.snw.tpadmin.webui.RegistrationHandlers"
method="register"/>
</bc4j:findRootAppModule>
</event>

<event name="cancel">

<bc4j:findRootAppModule name="XhubRegAM">

<bc4j:rollback/>

<go name="main"/>
</bc4j:findRootAppModule>
</event>

<event name="buyorsup">
<bc4j:findRootAppModule name="XhubRegAM">

<method class="oracle.apps.snw.tpadmin.webui.RegistrationHandlers"
method="isBuyerorSupplier"/>
</bc4j:findRootAppModule>
</event>
<event name="*">
<bc4j:findRootAppModule name="XhubRegAM">

<method class="oracle.apps.snw.tpadmin.webui.RegistrationHandlers"
method="setContext"/>
</bc4j:findRootAppModule>
</event>
</handlers>
</page>
Please suggest if you know of any documentation on ADF UIX partial page rendering.
ADF UIX has very little documentation online and finding it hard to debug this issue.
It ll be of great help.
Thanks
Kamal

Hi Jason,
As of EA9, all rendered components support a partialTriggers attribute. This attribute takes a list of master component IDs. If any of the master components are updated via a partial event, the dependent component will be rerendered in the partial update.
If you are on an earlier release, you should upgrade.
Thanks,
Jeanne

XML Publisher report output in RTF format does not display full page

Hi,
We have one XML Publisher report, the output of report in RTF format is not getting displayed in Full Page in normal way (MS Word -->View menu --> Print layout) but we can see full page display when we do MS Word -->View menu --> Outline.
Appreciate your valuable inputs on this.
Is this a template issue or any profiles needs to be set.
Thanks
Vijay

Do you have any header and footer on your template?
If you have any header and footer then try to adjust it as of to display full page.
Thanks
Yasar

How can I print just a part of the page and not the full page with Adobe Reader v 10.1.2?

how can I print just a part of the page and not the full page with Adobe Reader v 10.1.2? I need to print a engineering print with lot of information but information is too small in letter size and I don't have a plotter.

Two ways to print a portion of a page: zooming or using the Snapshot Tool.
ZOOMING:
Zoom into the area you want to print.
Click the Print icon.
Under "Pages to Print", make sure "Current view" is selected under "More options" (you may need to click "More options" to open it).
If you aren't satisfied with the preview, try clicking "Fit" under the Size button.
SNAPSHOT
Choose Edit > Take A Snapshot.
Drag a rectangle around the area you want to print.
Click the Print icon.
Under "Pages to Print", make sure that "Selected Graphic" is selected under "More options".
To enlarge the snapshot to fit the sheet of paper, choose "Fit" under the Size button.
Hope this helps!

IView is not being displayed in full page

I created one iView, added it into a page. I set the layout as 1 Column Full width. My view is not being displayed in entire window. What kind of property, I should set in the page.

Sunil:
By default, the iView's height property is fixed. After I changed iView's height property to Full page, The page displays correctly.
I setup two views in one page using one column Full width. Both the iviews are setup in one page. Now both the iViews height is set up to Full Page as well as page's height is setup to Full page. Now, the Top iView is being displayed with 3/4th of window size and bottom iView is being displayed with 1/4th of window size. I want to display both of them with equal size.
Thanks for your help.

Full page prints from iPhone but not from iPad using photo app with AirPrint ?

Full page prints from iPhone but not from iPad using photo app with AirPrint ? iPad only prints 4x6 on full size paper. It's an HP 8600.

I also have this problem printing photos from an iPad to an Epson WF-2540 printer. It prints only 4x6 and without border (so print starts at extreme top left corner of paper). Borderless printing is not selected on printer. Printing a square photo just crops to 4x6 size.

I am trying to print a passport sized headshot and I get a full page photo. How to I print out a smaller size?

I am trying to print a passport sized headshot and I get a full page photo isntead. I downloaded the shot from i photo and chose "small" but it didn't help.
I also cropped the photo on iphoto to the dorrect size but no difference. I have a Canon MX 870 printer. Please advise.

In iPhoto select the photo and print - select the paper size and a custom print size (2x2 i believe for passports) and print
LN

I am trying to remove two full page black borders from my Pages document and when I click on them they are greyed out

I am trying to remove 2 full page size black borders in my pages document and whn i click on them they show greyed x's but i cannot manipulate or remove them. What to do?

John,
While the grayed x corners are showing, Arrange > Unlock.
Now you will be able to manipulate or delete the borders.
Jerry

PDF document not full page but need to print it as a full page

Hi,
I have a pdf document which is 15 cm by 8 cm and need to print it as a full page without the white border making up the full page. How can I do this?
The document was created in publisher and saved as a pdf.
I am reading the document from Adobe Reader on a Windows XP machine.
Thank you for any help any one can give.

Do you have a printer that can print pages without a white border?
Very few printers can do this.
Aandi Inston

Two questions: Event on a Date Picker and Read Only on a full page?

Hello,
I make use of this very informative board to develop an application but i have been unable to find info on these two topics. Sorry if it has been already discussed extensively.
Using HTMLDB 2.2 for now.
=>First question:
I have a date picker item with an event
onChange="resaStatusChange();"
in the HTML Form Element Attribute field.
The event is triggerring if i put a new data in the field but does not trigger if i use the picker.
Is it a standart behaviour? Is there a way to trigger the event when new data is provided through the date picker?
=> Second question:
One page in my application has to be used either to only display information or as a mixed displaying/entering data sheet.
When the context is appropriate to use the page as a simple display (testing both global authorization and data to be displayed), is there a way to put a read only attribute on the full page instead of putting the read only conditions through each and every item of the page?
Sorry if the questions are not clear and apologize for what should be newbie questions.
Any link or info will be appreciated.
Regards,
Daniel Gureghian

Hi Daniel,
I'm not sure about your first question, but I can hopefully give you a helpfull answer for your second one.
I'm handling it this way:
var elInput = document.getElementsByTagName('input');
var elTextArea = document.getElementsByTagName('textarea');
var elSelect = document.getElementsByTagName('select');
for (i = 0; i < elInput.length; i++)
setReadOnly(elInput, true);
for (i = 0; i < elTextArea.length; i++)
setReadOnly(elTextArea[i], true);
for (i = 0; i < elSelect.length; i++)
setReadOnly(elSelect[i], true);
function setReadOnly(pThis, pRead)
     if (pThis && pRead)
          pThis.disabled = pRead;
          pThis.style.emptyCells = "show";
          pThis.style.color = "black";
          pThis.style.backgroundColor = "#DDDDDD";
     else if (pThis && !pRead)
          pThis.disabled = pRead;
          pThis.style.emptyCells = "show";
          pThis.style.color = "black";
          pThis.style.backgroundColor = "#FFFFFF";
I never used it on a whole page, only for regions. So maybe you have to make some changes.
chrissy

The affect of failed validation on the page rendering phase

This is divided in two parts. In the first one I describe the behavior and in the second I show work around and make a suggestion.
The need that started this was that the value an item needed to be recalculated each time de page was shown. This page could be called from buttons and from branches on other pages. So the logical place to put this calculation is in Computation of the Page Rendering phase. But, when a validation failed the value wasn't shown on the browser and I later discovered it was not calculated at all. I tried moving the calculation in a Process of the Page Rendering phase, but to that didn't worked either. So I needed to have a beter understanding of happens when a validation fails, ence this test.
The test was done on version 3.1.2 of APEX.
For this test, here is what I programmed (if no values is specified, than the property has the default value):
1. I created a blank page
-- In the Page Rendering part --
2. I created a region with the following properties
Identification
- Title: Alpha
- Type: PL/SQL (Anonymous block)
Source
- Region Source: wwv_flow.debug('> RENDER REGION Alpha SOURCE');
Conditional Display
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER REGION Alpha CONDITION'); RETURN TRUE;
Caching
- Caching: Cahed
- Cache Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER REGION Alpha CACHE CONDITION'); RETURN TRUE;
3. I created an item with the following properties
Name
- Name: P1_X
- Display As: Textfield
Displayed
- Region: Alpha
Source
- Source Used: Always, replacing any existing value in session state
- Source Type: PL/SQL Function body
- Source value or expression: wwv_flow.debug('> RENDER ITEM P1_X SOURCE'); RETURN NULL;
- Post Calculation Computation: :P1_X || ' POST-CALCUL'
Default
- Default value: wwv_flow.debug('> RENDER ITEM P1_X DEFAULT'); RETURN 'RENDER ITEM P1_X DEFAULT';
- Default Value Type: PL/SQL Function body
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_X CONDITION'); wwv_flow.debug('> P1_X="'||:P1_X||'"'); RETURN TRUE;
Read Only
- Read Only Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_X READ_ONLY CONDITION'); RETURN FALSE;
4. I created a second item with the following properties
- Name: P1_Y
- Display As: Textfield
Displayed
- Region: Alpha
Source
- Source Used: Only when current value in session state is null
- Source Type: PL/SQL Function body
- Source value or expression: wwv_flow.debug('> RENDER ITEM P1_Y SOURCE'); RETURN NULL;
- Post Calculation Computation: :P1_Y || ' POST-CALCUL'
Default
- Default value: wwv_flow.debug('> RENDER ITEM P1_Y DEFAULT'); RETURN 'RENDER ITEM P1_Y DEFAULT';
- Default Value Type: PL/SQL Function body
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_Y CONDITION'); wwv_flow.debug('> P1_Y="'||:P1_Y||'"'); RETURN TRUE;
Read Only
- Read Only Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_Y READ-ONLY CONDITION'); RETURN FALSE;
5. I created a button with the following properties
Name
- Button Name: GO
- Text Label/Alt: Go
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Go CONDITION'); RETURN TRUE;
6. I created a second button with the following properties
Name
- Button Name: GOERRNULL
- Text Label/Alt: Go invalid
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Go invalid CONDITION'); RETURN TRUE;
7. I created a thrid button with the following properties
Name
- Button Name: RESET
- Text Label/Alt: Reset cache
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Reset CONDITION'); RETURN TRUE;
Optional URL Redirect
- Target is a: Page in this Appplication
- Page: 1
- resetpagination for this page: checked
- Request: RESET
- Clear Cache: 1
8. I created a computation with the following properties
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:Before Header
Source
- Computation: wwv_flow.debug('> RENDER CALCUL P1_Y SOURCE'); RETURN 'RENDER CALCUL P1_Y SOURCE';
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER CALCUL P1_Y CONDITION'); RETURN TRUE;
9. I created a process
Name
- Name: Beta
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Load - Before Header
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> RENDER PROC Beta SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER PROC Beta CONDITION'); RETURN TRUE;
-- In the Page Processing part --
10. I created a computation
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: wwv_flow.debug('> PROC CALCUL P1_Y SOURCE'); RETURN 'PROC CALCUL P1_Y SOURCE';
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC CALCUL P1_Y CONDITION'); RETURN TRUE;
11. I created a second computation
Item Name
- Item Name: P1_X
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: wwv_flow.debug('> PROC CALCUL P1_X SOURCE'); RETURN NULL;
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC CALCUL P1_X CONDITION'); RETURN TRUE;
12. I created a validation
Validation
- Name: Delta
- Type: Function Returning Boolean
- Validation Expression 1: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN FALSE;
Error Message
- Error Message: err msg
- Associated Item: P1_X
Conditionals
- When Button Pressed: GOERRNULL (Go invalid)
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC VALIDATION Delta CONDITION'); RETURN TRUE;
13. I created a process
Name
- Name: Gamma
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Submit - Before Computation and Validations
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> PROC PROC Gamma SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC PROC Gamma CONDITION'); RETURN TRUE;
14. I created a second process
Name
- Name: Epsylon
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Submit - After Computation and Validations
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> PROC PROC Epsylon SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC PROC Epsylon CONDITION'); RETURN TRUE;
15. I created a branch
Point
- Branch Point: On Submit: After Processing (After Computation, Validation and Processiong)
Action
- Target Type: Page in this Application
- Page: 1
- include process success message: checked
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC BRANCH P1 CONDITION'); RETURN TRUE;
As can be seen, I've programmed all condition to be true and therefore making all objects do thier calculations.
Here is the debug output when we click on "Go". (a line number was added for easy refence)
{color:#999999}001 0.05: A C C E P T: Request="GO"
002 0.09: Metadata: Fetch application definition and shortcuts
003 0.09: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
004 0.09: alter session set nls_language="AMERICAN"
005 0.09: alter session set nls_territory="AMERICA"
006 0.09: NLS: CSV charset=WE8MSWIN1252
007 0.09: ...NLS: Set Decimal separator="."
008 0.09: ...NLS: Set NLS Group separator=","
009 0.09: ...NLS: Set date format="DD-MON-RR"
010 0.09: ...Setting session time_zone to -05:00
011 0.09: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
012 0.09: Session: OK to reuse builder session for user:APEX_PUBLIC_USER
013 0.09: Fetch session state from database
014 0.10: ...Check session 2800365259756461 owner
015 0.10: ...Metadata: Fetch Page, Computation, Process, and Branch
016 0.10: Session: Fetch session header information
017 0.10: ...Metadata: Fetch page attributes for application 202, page 1
018 0.10: ...Validate item page affinity.
019 0.10: ...Validate hidden_protected items.
020 0.10: ...Check authorization security schemes
021 0.10: Session State: Save form items and p_arg_values
022 0.10: ...Session State: Save Item "P1_X" newValue="RENDER ITEM P1_X DEFAULT POST-CALCUL" "escape_on_input="N"
023 0.10: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE POST_CALCUL"
024 0.10: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
025 0.11: {color}{color:#ff9900}> PROC PROC Gamma CONDITION{color}{color:#999999}
026 0.11: ...Process "Gamma": PLSQL (ON_SUBMIT_BEFORE_COMPUTATION) wwv_flow.debug('> PROC PROC Gamma SOURCE');
027 0.11: {color}{color:#ff9900}> PROC PROC Gamma SOURCE{color}{color:#999999}
028 0.11: Branch point: BEFORE_COMPUTATION
029 0.11: Computation point: AFTER_SUBMIT
030 0.11: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
031 0.11: {color}{color:#ff9900}> PROC CALCUL P1_Y CONDITION{color}{color:#999999}
032 0.11: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
033 0.11: ...Performing function body computation
034 0.12: {color}{color:#ff9900}> PROC CALCUL P1_Y SOURCE{color}{color:#999999}
035 0.12: ...Session State: Saved Item "P1_Y" New Value="PROC CALCUL P1_Y SOURCE"
036 0.12: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_X
037 0.12: {color}{color:#ff9900}> PROC CALCUL P1_X CONDITION{color}{color:#999999}
038 0.12: ...Perform computation of item: P1_X, type=FUNCTION_BODY
039 0.12: ...Performing function body computation
040 0.12: {color}{color:#ff9900}> PROC CALCUL P1_X SOURCE{color}{color:#999999}
041 0.12: ...Session State: Saved Item "P1_X" New Value=""
042 0.12: Tabs: Perform Branching for Tab Requests
043 0.12: Branch point: BEFORE_VALIDATION
044 0.12: Perform validations:
045 0.12: {color}{color:#ff9900}> PROC VALIDATION Delta CONDITION{color}{color:#999999}
046 0.12: ...PL/SQL "function body returning boolean" Validation: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN :REQUEST 'GOERRNULL';
047 0.12: {color}{color:#ff9900}> PROC VALIDATION Delta SOURCE{color}{color:#999999}
048 0.13: Branch point: BEFORE_PROCESSING
049 0.13: Processing point: AFTER_SUBMIT
050 0.13: {color}{color:#ff9900}> PROC PROC Epsylon CONDITION{color}{color:#999999}
051 0.13: ...Process "Epsylon": PLSQL (AFTER_SUBMIT) wwv_flow.debug('> PROC PROC Epsylon SOURCE');
052 0.13: {color}{color:#ff9900}> PROC PROC Epsylon SOURCE{color}{color:#999999}
053 0.13: Branch point: AFTER_PROCESSING
054 0.13: ...Evaluating Branch: AFTER_PROCESSING type: "REDIRECT_URL" button: (No Button Pressed) branch: wwv_flow.debug('> PROC BRANCH P1 C5NDITION'); RETURN TRUE;
055 0.14: {color}{color:#ff9900}> PROC BRANCH P1 CONDITION{color}{color:#999999}
0.00:
0.00: S H O W: application="202" page="1" workspace="" request="" session="2800365259756461"
0.00: Language derived from: FLOW_PRIMARY_LANGUAGE, current browser language: en-us
056 0.00: alter session set nls_language="AMERICAN"
057 0.00: alter session set nls_territory="AMERICA"
058 0.00: NLS: CSV charset=WE8MSWIN1252
059 0.00: ...NLS: Set Decimal separator="."
060 0.00: ...NLS: Set NLS Group separator=","
061 0.00: ...NLS: Set date format="DD-MON-RR"
062 0.01: ...Setting session time_zone to -05:00
063 0.01: NLS: Language=en-us
064 0.01: Application 202, Authentication: CUSTOM2, Page Template: 2204612885682472
065 0.01: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
066 0.01: ...ok to reuse builder session for user:APEX_PUBLIC_USER
067 0.01: ...Application session: 2800365259756461, user=APEX_PUBLIC_USER
068 0.01: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
069 0.01: Session: Fetch session header information
070 0.01: ...Metadata: Fetch page attributes for application 202, page 1
071 0.01: Fetch session state from database
072 0.01: Branch point: BEFORE_HEADER
073 0.01: Fetch application meta data
074 0.02: Computation point: BEFORE_HEADER
075 0.02: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
076 0.02: {color}{color:#ff9900}> RENDER CALCUL P1_Y CONDITION{color}{color:#999999}
077 0.02: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
078 0.02: ...Performing function body computation
079 0.02: {color}{color:#ff9900}> RENDER CALCUL P1_Y SOURCE{color}{color:#999999}
080 0.02: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE"
081 0.02: Processing point: BEFORE_HEADER
082 0.02: {color}{color:#ff9900}> RENDER PROC Beta CONDITION{color}{color:#999999}
083 0.02: ...Process "Beta": PLSQL (BEFORE_HEADER) wwv_flow.debug('> RENDER PROC Beta SOURCE');
084 0.02: {color}{color:#ff9900}> RENDER PROC Beta SOURCE{color}{color:#999999}
085 0.02: Show page template header
086 0.03: Computation point: AFTER_HEADER
087 0.03: Processing point: AFTER_HEADER
088 0.03: Computation point: BEFORE_BOX_BODY
089 0.03: Processing point: BEFORE_BOX_BODY
090 0.03: Region: Alpha
091 0.03: {color}{color:#ff9900}> RENDER REGION Alpha CONDITION{color}{color:#999999}
Alpha
092 0.03: {color}{color:#ff9900}> RENDER BUTTON Go CONDITION{color}{color:#999999}
093 0.03: {color}{color:#ff9900}> RENDER BUTTON Go invalid CONDITION{color}{color:#999999}
094 0.03: {color}{color:#ff9900}> RENDER BUTTON Reset CONDITION{color}{color:#999999}
Go Go invalid Reset cache
095 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X CONDITION{color}{color:#999999}
096 0.03: > P1_X=""
097 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X READ_ONLY CONDITION{color}{color:#999999}
098 0.03: Item: P1_X TEXT
099 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X SOURCE{color}{color:#999999}
100 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X DEFAULT{color}{color:#999999}
X RENDER ITEM P1_X DEFAULT POST-CALCUL
101 0.03: {color}{color:#ff9900}> RENDER ITEM P1_Y CONDITION{color}{color:#999999}
102 0.03: > P1_Y="RENDER CALCUL P1_Y SOURCE"
103 0.04: {color}{color:#ff9900}> RENDER ITEM P1_Y READ-ONLY CONDITION{color}{color:#999999}
104 0.04: Item: P1_Y TEXT
Y RENDER CALCUL P1_Y SOURCE POST_CALCUL
105 0.04: {color}{color:#ff9900}> RENDER REGION Alpha SOURCE{color}{color:#999999}
106 0.04: Computation point: AFTER_BOX_BODY
107 0.04: Processing point: AFTER_BOX_BODY
108 0.04: Computation point: BEFORE_FOOTER
109 0.04: Processing point: BEFORE_FOOTER
110 0.04: Show page tempate footer
111 0.04: Computation point: AFTER_FOOTER
112 0.04: Processing point: AFTER_FOOTER
113 0.04: Log Activity:
114 0.04: Execute Count=0
115 0.04: End Show:{color}
Here is the debug output when we click on "Go invlid". (a line number was added for easy refence)
{color:#999999}201 0.14: A C C E P T: Request="GOERRNULL"
202 0.19: Metadata: Fetch application definition and shortcuts
203 0.19: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
204 0.19: alter session set nls_language="AMERICAN"
205 0.19: alter session set nls_territory="AMERICA"
206 0.19: NLS: CSV charset=WE8MSWIN1252
207 0.19: ...NLS: Set Decimal separator="."
208 0.20: ...NLS: Set NLS Group separator=","
209 0.20: ...NLS: Set date format="DD-MON-RR"
210 0.20: ...Setting session time_zone to -05:00
211 0.24: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
212 0.24: Session: OK to reuse builder session for user:APEX_PUBLIC_USER
213 0.24: Fetch session state from database
214 0.29: ...Check session 2800365259756461 owner
215 0.29: ...Metadata: Fetch Page, Computation, Process, and Branch
216 0.29: Session: Fetch session header information
217 0.29: ...Metadata: Fetch page attributes for application 202, page 1
218 0.30: ...Validate item page affinity.
219 0.30: ...Validate hidden_protected items.
220 0.30: ...Check authorization security schemes
221 0.30: Session State: Save form items and p_arg_values
222 0.31: ...Session State: Saved Item "P1_X" New Value="RENDER ITEM P1_X DEFAULT POST-CALCUL"
223 0.31: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE POST_CALCUL"
224 0.31: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
225 0.32: {color}{color:#ff9900}> PROC PROC Gamma CONDITION{color}{color:#999999}
226 0.32: ...Process "Gamma": PLSQL (ON_SUBMIT_BEFORE_COMPUTATION) wwv_flow.debug('> PROC PROC Gamma SOURCE');
227 0.32: {color}{color:#ff9900}> PROC PROC Gamma SOURCE{color}{color:#999999}
228 0.33: Branch point: BEFORE_COMPUTATION
229 0.33: Computation point: AFTER_SUBMIT
230 0.33: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
231 0.34: {color}{color:#ff9900}> PROC CALCUL P1_Y CONDITION{color}{color:#999999}
232 0.34: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
233 0.34: ...Performing function body computation
234 0.34: {color}{color:#ff9900}> PROC CALCUL P1_Y SOURCE{color}{color:#999999}
235 0.34: ...Session State: Saved Item "P1_Y" New Value="PROC CALCUL P1_Y SOURCE"
236 0.34: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_X
237 0.34: {color}{color:#ff9900}> PROC CALCUL P1_X CONDITION{color}{color:#999999}
238 0.34: ...Perform computation of item: P1_X, type=FUNCTION_BODY
239 0.34: ...Performing function body computation
240 0.35: {color}{color:#ff9900}> PROC CALCUL P1_X SOURCE{color}{color:#999999}
241 0.35: ...Session State: Saved Item "P1_X" New Value=""
242 0.35: Tabs: Perform Branching for Tab Requests
243 0.35: Branch point: BEFORE_VALIDATION
244 0.35: Perform validations:
245 0.75: {color:#ff9900}> PROC VALIDATION Delta CONDITION{color}{color:#999999}
246 0.76: ...PL/SQL "function body returning boolean" Validation: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN FALSE;
247 0.78: {color}{color:#ff9900}> PROC VALIDATION Delta SOURCE{color}{color:#999999}
248 0.78: ...{color}{color:#ff0000}Validation did NOT pass{color}{color:#999999}
249 0.78: ...{color}{color:#ff0000}Inline validation error count = 1{color}{color:#999999}
250 0.86: Show current page with inline validations
251 0.87:
252 0.87: S H O W: application="202" page="1" workspace="" request="" session="2800365259756461"
253 0.87: NLS: Language=en-us
254 0.87: Application 202, Authentication: CUSTOM2, Page Template: 2204612885682472
255 0.88: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
256 0.88: ...ok to reuse builder session for user:APEX_PUBLIC_USER
257 0.88: ...Application session: 2800365259756461, user=APEX_PUBLIC_USER
258 0.88: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
259 0.88: ...Metadata: Fetch page attributes for application 202, page 1
260 0.88: Branch point: BEFORE_HEADER
261 0.88: Fetch application meta data
262 0.88: Computation point: BEFORE_HEADER
263 0.88: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
264 0.92: {color}{color:#99cc00}> RENDER CALCUL P1_Y CONDITION{color}{color:#999999}
265 0.92: Processing point: BEFORE_HEADER
266 0.92: ......Do not perform process because inline validation condition found.
267 0.92: ...Do not run process "Beta", process point=BEFORE_HEADER, condition type=FUNCTION_BODY, when button pressed=
268 0.92: ...Recompute field lables for fields in error.
269 0.97: Show page template header
270 1.20: Computation point: AFTER_HEADER
271 1.20: Processing point: AFTER_HEADER
1 error has occurred
* Error msg
272 1.20: Computation point: BEFORE_BOX_BODY
273 1.20: Processing point: BEFORE_BOX_BODY
274 1.21: Region: Alpha
275 1.23: {color}{color:#ff9900}> RENDER REGION Alpha CONDITION{color}{color:#999999}
Alpha
276 1.25: {color}{color:#ff9900}> RENDER BUTTON Go CONDITION{color}{color:#999999}
277 1.25: {color}{color:#ff9900}> RENDER BUTTON Go invalid CONDITION{color}{color:#999999}
278 1.28: {color}{color:#ff9900}> RENDER BUTTON Reset CONDITION{color}{color:#999999}
Go Go invalid Reset cache
279 1.30: {color}{color:#ff9900}> RENDER ITEM P1_X CONDITION{color}{color:#999999}
280 1.30: > P1_X=""
281 1.30: {color}{color:#ff9900}> RENDER ITEM P1_X READ_ONLY CONDITION{color}{color:#999999}
282 1.30: Item: P1_X TEXT
X POST-CALCUL
Error msg
283 1.30: {color}{color:#ff9900}> RENDER ITEM P1_Y CONDITION{color}{color:#999999}
284 1.30: > P1_Y="PROC CALCUL P1_Y SOURCE"
285 1.31: {color}{color:#ff9900}> RENDER ITEM P1_Y READ-ONLY CONDITION{color}{color:#999999}
286 1.31: Item: P1_Y TEXT
Y PROC CALCUL P1_Y SOURCE POST_CALCUL
287 1.32: {color}{color:#ff9900}> RENDER REGION Alpha SOURCE{color}{color:#999999}
288 1.32: Computation point: AFTER_BOX_BODY
289 1.32: Processing point: AFTER_BOX_BODY
290 1.32: Computation point: BEFORE_FOOTER
291 1.32: Processing point: BEFORE_FOOTER
292 1.32: Show page tempate footer
293 1.32: Computation point: AFTER_FOOTER
294 1.32: Processing point: AFTER_FOOTER
295 1.32: Log Activity:
296 1.32: Execute Count=0
297 1.32: End Show:{color}
Looking at those debug output, I was able to find a workaround. Look at the line 264 and compare that to the lines 076 to 080. What I did is put the computation in the condition. This way, I'm garanteed that the calculation is always done. Here is an exemple:
A Computation (in the Page Rendering part)
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: RETURN :P1_Y; -- Never executed. Look in the condition for computation
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: :P1_Y := COMPUTE(); RETURN FALSE;
This works but totally break the semantics created in APEX.
Suggestion:
In the Page rendering phase, when a validation fails, the source compution found in a Item (in that case the value is taken from the session state), in a Computation or in Process is never executed.
This should revised.
Their should be a way for the programmer to choose what behavior the rendering phase will have when a validation fails other than using a workaround that might break in futur versions of APEX.
Edited by: user4591233 on Nov 19, 2008 6:32 AM
Edited by: user4591233 on Nov 19, 2008 6:34 AM

Dominique,
Thank you for the detailed problem description. Although you posted it some ten hours ago I have just now finished reading it.
Form pages must be built so they can operate correctly when inline validation errors are displayed. The assumption (by the engine) is that session state (and package state) as it exists at the point the validations are performed is sufficient (and correct) to support the redisplay of the page without the need to fire on-load processes or computations. Session state or package state changes made by after-submit computations or after-submit/before computations/validations processes that prevent correct page behavior on the "validation redisplay" must be avoided.
The condition types Inline Validation Errors Displayed/No Inline Validation Errors Displayed can be used for on-load events/controls (processes, computations, regions, items, ...) for which you need finer control over this behavior.
Also, you can forgo the use of after-submit computations when the resulting alteration of session state would be inimical to proper "validation redisplay" behavior and use On Submit - After Computations and Validations processes instead.
I hope I have understood your situation and that this answer adequately answers your questions.
Scott

Report output not using full page.

I have a report that does not use the full screen to display. The output display on about a 1.5 to 2 inch section of the page and the rest is white space. How do I get it to use the full page?

Hi Raymist123,
If I understand correctly, the issue which you occurred is that the report content only displayed about 1.5 to 2 inch. As per my understanding, I think this issue is caused by the report content including all the report items (table, matrix, list, chart,
gauge, text boxes etc.) is only occupied 1.5 to 2 inch on the report design surface. If in this case, we can try to expand the sizes of all the report items to fix the issue. And please make sure that the PageSize of the report have set to 8.5 x 11.
If this issue is still existed, could you please post the screenshot about the design surface and the all the size properties? Then we can make further analysis.
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Report cannot print in full page

Hi all,
I have generated the report and when view on screen, the format is ok but when submitted to printer, the report output does not show in full page, right hand side of the paper is blank off.
I am using report v.6.0.8.25.0
Rgds
Lim

Hi,
Under Report Builder directory you will find one directory which contains printers file with extensions of PRT, check the setting their.
Thanks
Shishu Paul

Unable to print full page to 1 specific printer while other computers can.

I have 1 computer (Windows 7, 64 bit) which is unable to print full page to a Xerox Phaser 7760GX. I have other computers (Windows 7 64 bit and Mac OSX Mavericks) which are able to print perfectly fine to the same printer. This only happens in Adobe Acrobat XI Pro, not in other software I have tested. The same PDF's also print to other printers without problem.
So far I have:
Re-installed drivers (including the Xerox Generic Drivers)
Set it to print as image (which makes it full screen, but also greyscale)
What happens when I try to print normally, is assume the page is portrait. It will print it landscape, on the right side of the page (so it takes up half the page). It will also send out a blank page after it. Has anyon else experienced this and come up with a different solution?

Glad you solved your problem. On Aperture 3.02 I find no expansion slider. Where is it in 3.01?

How can I scroll one full page at a time using the mouse wheel?

I've had this problem for 3 years now. When I nudge my scroll wheel (IntelliMouse Optical) one notch forward or back, Safari moves 1/4 of a page up or down. How can I get one nudge of the scroll wheel to move one full page up or down? Firefox has an add-on, SmoothWheel, that can be set to a full page. Are there any options for doing this in Safari, without having to go to the keyboard? I tried Smart Wheel, no setting for that.
Any ideas? thanks
p.s. Please don't tell me to get another mouse, I've tried dozens of them and the old IntelliMouse Optical is the best one for me. (I'm also stuck on an ancient Apple M2980 keyboard. I love those old keyboards.)
Mac Pro 2X-Quad-Core Intel Xeon 2.8 GHz MA970LL/A
OS X 10.8.3
Memory: 10 GB
ATI Radeon HD 2600 XT
Safari 6.03

I can't use the keyboard to scroll. I need to keep my hand on the mouse, otherwise I'd never get anything done. Since I have no problem getting Firefox to scroll one page at a time, and I'm constantly jumping between 3 browsers, it would be nice to be able to scroll a full page at a time in Safari, just like I can in Firefox. Thanks.

Full Page Rendering?

Similar Messages

Maybe you are looking for