Automatic height adjustment does not work

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

  1. iFbA: Browser hangs after uploading documentSymptom You locally save an interactive form from a Web Dynpro ABAP application; you fill out the form offline and then upload it into a Web Dynpro ABAP application. When you display...
  2. Quarterly Adjustment-Street sections changes not updatedSymptom Whenever the street sections are changed and the postal code is redetermined using the SR transactions, this results in a deletion of existing street sections and an insertion of a new...
  3. iFbA: Conversion exits and read-only formsSymptom This note repairs various problems for the “SAP interactive Forms by Adobe” solution for Web Dynpro ABAP: ABAP Dictionary conversion exits are ignored during the data transfer of interactive forms to...
  4. iFbA: Firefox 3 support and additional correctionsSymptom 1. If you start a Web Dynpro ABAP application that uses the solution “SAP Interactive Forms by Adobe” in Firefox 3, it hangs during the session and then terminates shortly afterwards....
  5. Adobe LiveCycle Designer 8.1 – PatchSymptom You want to apply a patch for Adobe LiveCycle Designer 8.1. Other terms Adobe LiveCycle Designer, patch, ADS, Adobe Document Services, SAP Interactive Forms Reason and Prerequisites You have installed Adobe...
  6. Adobe LiveCycle Designer 8.0 – PatchSymptom You want to apply a patch for Adobe LiveCycle Designer 8.0. Other terms Adobe LiveCycle Designer, patch, ADS, Adobe Document Services, SAP Interactive Forms Reason and Prerequisites You have installed Adobe...
  7. Currency or quantity amounts are not issuedSymptom The system does not issue fields with currency fields or quantity fields for the form output. Other terms Decimal point, user default values, IFbA, Interactive Forms by Adobe, Adobe Reason and...
  8. Form not being disappeared when closing InsideTraySymptom Form not being disappeared when closing InsideTray Other terms Adobe, PDF, ADS, Web Dynpro ABAP, InteractiveForm. Reason and Prerequisites This is caused by a program error. Solution Implement the correction instructions....

Symptom

Your application has problems with the height adjustment in the browser. The following symptoms may occur:
Your Web Dynpro ABAP application does not use the maximum height of the browser or iView.You run your application in an iView of the Enterprise Portal. After several interactions, the system no longer adjusts the height of the iView correctly.An SAP Interactive Form by Adobe with a height of 100% turns into a line or does not use 100% of the height in the browser.In a TransparentContainer, Tray, and so on, you have set the height to 100%. However, in Firefox, this user interface (UI) element does not have the full height. This is unexpected.Your application runs in an iView of the Enterprise Portal with automatic height adjustment and seems to be too large. The application becomes visible only after scrolling, or it has an unnecessary scroll bar.After the appplication has started, the browser displays an empty light-blue space or a thin line.

Other terms

Web Dynpro ABAP, portal, height, Adobe, interactive form, SAP Interactive Forms by Adobe, Firefox
Reason and Prerequisites

These problems are caused by a program error.
Solution

First of all, here is some general information if you develop your own Web Dynpro ABAP applications that are to contain UI elements with a height of 100% (especially the InteractiveForm UI element). Such an application must adhere to the following rules for ALL layouts and container-type UI elements (TransparentContainer, Group, Tray, and so on), which contain a UI element with a height of 100%:
The height of container-type UI elements (for example, TransparentContainer, Group, Tray, and so on) must be set to 100%. This applies especially to the ROOTUIELEMENTCONTAINER.You may use only layouts of the type MatrixLayout or GridLayout. Here, set the indicator stretchedVertically to true.The property “vAlign” of all instances of GridData and Matrix(Head)Data must be set to “top”.The property “height” of all instances of GridData and MatrixData must be set to “100%”.

If you have installed SAP_BASIS 7.00 and the problems described above occur in Internet Explorer and Firefox, this is probably because the application did not adhere to the rules specified above.
If you have installed SAP_BASIS 7.00 and the problems described above occur for active contents only in Firefox, see Note 1347454.
If you have installed SAP_BASIS 7.01 and the problems described above occur, import 7.01 Support Package 4 or implement the attached correction instructions.
If you have installed SAP_BASIS 7.01 and have implemented this note and the problems described above occur in a popup, you must also implement Note 1351822.

Note that you must execute certain manual steps if you use the correction instructions. These steps are described in the pre- and post-implementation steps of two correction instructions.
Note the following important points with regard to this correction.
The developers of a Web Dynpro application must decide whether or not the application is to always use the maximum height. Depending on this, the application parameter WDSUPPORTSFULLHEIGHT, which is introduced by this note, must be set to 0, 1, or 2. The default value is 0.
In the standard case, the correct setting is made automatically for most applications. It is only for applications that run in the portal and which display the UI elements with a height of 100% and whose ROOTUIELEMENTCONTAINER of the initial topmost view does not have a height of 100% that you must manually set the application parameter WDSUPPORTSFULLHEIGHT to 2.
The following explains the three values for WDSUPPORTSFULLHEIGHT in detail:
If you set WDSUPPORTSFULLHEIGHT to the value 1, the application does not use the full height of the browser. This is the correct setting if the following criteria are met:The application is to run in an iView with automatic and fixed height adjustment (this means: in the property category “Appearance – Size” of the iView, the value “AUTOMATIC” or “FIXED” is set for “Height Type”).The application does not contain any UI elements with a height of 100%.
If an application contains UI elements with a height of 100% (for example, SAP Interactive Forms by Adobe) and WDSUPPORTSFULLHEIGHT is set to 1, the system may display the UI elements too small, may not display them at all, or may only display them as a line. This effect occurs regardless of whether or not the application runs in the portal or separately and regardless of the iView height setting.If WDSUPPORTSFULLHEIGHT is set to the value 2, the application can use the full 100% height of the browser. This is the correct setting if the following criteria are met:The application is to run in an iView with fixed height adjustment or in FULL_PAGE mode (this means: in the property category “Appearance – Size” of the iView, the value “FIXED” or “FULL_PAGE” is set for “Height Type”).The application contains UI elements with a height of 100%.
We do not recommend that you run an application with WDSUPPORTSFULLHEIGHT = 2 in an iView with automatic height adjustment because the application may use up too much space as a result, and unnecessary scroll bars may be displayed.If WDSUPPORTSFULLHEIGHT is set to the value 0, the system uses a default logic:If the application does not run in the portal, WDSUPPORTSFULLHEIGHT is set to 2. As a result, applications that have UI elements with a height of 100% are displayed correctly.If the application runs in the portal, WDSUPPORTSFULLHEIGHT is set to 2 if ROOTUIELEMENT of the initial topmost view has a height of 100%. Otherwise, WDSUPPORTSFULLHEIGHT is set to 1.

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 701 SAPKB70103 – SAPKB70103 |
————————————————————————
1. Use transaction SE11 to create the domain WDR_APP_PROP_FULL_HEIGHT in the package SWDP_RUNTIME_CORE with the following data:
Description: Application Height
Data Type: INT1
Value range: 0: Automatic: 1 or 2 is Used in the Portal
1: Height Corresponding to Content
2: Application Uses Entire Possible Height
Activate this domain.
2. Use transaction SE11 to create the data element WDR_APP_PROP_FULL_HEIGHT in the package SWDP_RUNTIME_CORE with the following data:
Description: Application Height
Field Labels: Height / Application Height / Application Height / Application Height.
Domain: WDR_APP_PROP_FULL_HEIGHT
Activate the data element.
3. Call transaction SE16 for the table WDY_APP_PROP_DEF.
Create the following new entry:
SET_NAME: STANDARD
PROPERTY_NAME: WDSUPPORTSFULLHEIGHT
ALIAS_NAME: wdSupportsFullHeight
DEFAULT_VALUE: 0
IS_MANDATORY:
PROPERTY_KIND: 0
MIN_LEVEL: 1
MAX_LEVEL: 1
URL_PARAMETER: SAP-WD-SUPPORTSFULLHEIGHT
SEPARATOR:
PORTAL_DEFAULT:
ABAP_TYPE: WDR_APP_PROP_FULL_HEIGHT
DESCRIPTION: Application Uses 100% of Possible Height
Save this entry.

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 701 SAPKB70103 – SAPKB70103 |
————————————————————————
After you implement the correction instructions, you must also delete the following programs:

SWDR_DO_LS_ACFAPISWDR_DO_LS_ACFWRAPPERSWDR_DO_LS_ACF_PLUGIN

Use transaction SE38 to do this.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment