This document provides information about the IBM® FileNet® 4.0.2.12-P8eF-FP012 fix pack.
Documentation
To access documentation for IBM FileNet eForms related products, go to http://www.ibm.com/support/docview.wss?uid=swg27009986.
Compatibility matrices and fix packs
To access compatibility matrices and fix packs for IBM FileNet eForms, go to http://www-01.ibm.com/support/docview.wss?uid=swg27010126.
NOTE Contact customer support for information about accessing fix packs. For more information, see Contact customer support.
For compatibility information, see the:
The above regression was introduced in the 4.0.2.12-P8eF-FP012. The fix for this issue is to check Archived Real Path Enabled under Web Applications after installation on WebLogic.
A new eForms Java API command for use with IBM Forms:
| API command | Function |
| Form.destroyForm() | New eForms Java API to be consumed by IBM Forms for destroying Form Object. |
Support has been added for modal dialogs for Firefox version 3 and higher.
Changes made to enable right-clicking by use of either the eforms-preferences.xml file or the eforms-integration.xml file. Right-click can be enabled from either of the two files. To enable right-click for eForms using the new parameter, set one of the following:
The above regression was introduced in the 4.0.2.11-P8eF-FP011 and the fix for the issue is included in 4.0.2.11-P8AE-FP011 and XT1.1.5.
If you install eforms 4.0.2.11-P8eF-FP011 on WorkplaceXT 1.1.4.x or Application Engine 4.0.2.x, the above mentioned regression will occur. In order to resolve this situation, if you install eForms fix pack 4.0.2.11-P8eF-FP011, you need to install WorkplaceXT 1.1.5 or Application Engine 4.0.2.11 or later versions.
Changes were made to the eForms installer to register the eForms platform information in the eForms-integration.xml configuration file. With this fixpack 4.0.2.11-P8eF-FP011 onwards, eForms is no longer the default forms platform. So eForms will be registered only when it is installed.
For details about how to register eForms platform, see Install this fix pack.
A current installation of the Signotec software must exist on the client PC prior to signing a form with the Signotec signature pad. The software is included with the device or by download from the Signotec website, (www.signotec.com).
Note for I-Sign(Ink) users
If the signing using I-Sign(Ink) is not successful after you install this test fix, search for and delete the old InkSign component, called eFormsWeb. The default location for eFormsWeb is:
C:/WINDOWS/Downloaded Program Files
You must remove eFormsWeb before you view and sign a form with an I-Sign(Ink) signature.
In order to create templates that can access the full range of I-Sign(Ink) signatures (Topaz, ePad, Signotec, and tablets using WinTab), install the latest eForms Designer fix pack: eFD-5.0.3.3-FP003 or newer. (It is not necessary to have a signature device connected to create an InkSign signature field in a form template.)
The eforms-preferences.xml file includes a parameter, strictNumberParsing, that will set eForms functionality to revert back to 3.5.1 behavior for not so strict number parsing if the parameter is set to "false". The default value for this parameter is "true". The parameter is required for a fix that is provided in this fix pack. For details about how to implement this parameter, see Install this fix pack.
Two new Java API commands for the HtmlFormRenderer Class have been added in this fix pack:
| API command | Function |
| getCustomPageTabOrdering | If a custom page tab ordering is specified, the tabVisibleattribute of each page will be ignored. The page tab will not be displayed if the associated page is not accessible.
|
| setCustomPageTabOrdering | If specified, the tabVisible attribute of each page will be ignored. However the page tab will not be displayed if the page is not accessible.
|
To organize form pages in the Step Map Advanced Options page:
You can change the order in which form page tabs are displayed in a form policy on a particular workflow step.
To change the display order of form pages:
Known issue
The Define Step Map - Advanced Options page in the IBM FileNet P8 help documentation does not identify all options available for the Advanced Options page. The available options are as follows:
| Field | Description |
| Page | ITX form pages that are available to display in the selected workflow. |
| Visibility | Display options for the pages at the steps listed in the workflow step of the selected workflow:
|
| Printable | Select this option to set the form pages as printable. |
| Start Page | Select the page you want to appear first when the policy is rendered. |
| Order Form Pages | Click Order Form Pages to access settings to change the order in which the form pages are displayed in the form policy. |
NOTE The Order Form Pages option was added as part of this fix pack.
For details about the enhancements and resolved defects in this fix pack, see Product fix history.
For information about FileNet P8 eForms new features and known issues, see the IBM FileNet P8 Release Notes.
eForms 4.0.2 introduced the Focus Rectangle. In some situations, the focus rectangle clips the data in cells. To address this issue, the eforms-preferences.xml file includes a new parameter (showFocusRectangle) that, when set to false, prevents the drawing of the focus rectangle. For details about how to implement this parameter, see Install this fix pack.
Known issue
eForms switches the month and day for a Date cell that has the format yyyy/mm/dd and the day is 10, 11, or 12. For example, for the date "2010/07/10" (July 10, 2010). eForms displays "2010/10/07." This issue is observed when the browser is set to Japanese. The issue will be addressed in the next eForms fix pack.
For details about the enhancements and resolved defects in this fix pack, see Product fix history.
For information about FileNet P8 eForms new features and known issues, see the IBM FileNet P8 Release Notes.
The eforms-preferences.xml file includes a new parameter (useCellDisplayName), which when set to true, eForms titles within the multi-lookup results dialog, use the display name rather than the field name to allow localization. For details about how to implement this parameter, see Install this fix pack.
This fix pack provides support for I-Sign(Ink). However, if you want to utilize existing templates, or create new templates, that use InkSign on IBM FileNet P8 eForms, you must use eForms Designer 5.0.2. A future fix pack release of eForms Designer 5.0.3 will include I-Sign(Ink) support.
Note for Topaz SigPlus users
If the Topaz signing is not successful after you install this interim fix, search for and delete the old InkSign component, called eFormsWeb. The default location for eFormsWeb is C:/WINDOWS/Downloaded Program Files/. You must remove eFormsWeb before you view and sign a form (with a Topaz device) using an I-Sign(Ink) signature.
Known Issue
A known issues exists, which is caused by the Internet Explorer versions 7.0 and 8.0 security setting.
When you sign a form for the first time, the system prompts you to download/install the eFormsWeb ActiveX control (which is identified simply as "IBM"). The system subsequently displays an alert warning that you are navigating away from the current page. You can ignore this warning. After you click Install, the system installs and activates the ActiveX control and the current form stays in view for you to complete and sign.
The eforms-preferences.xml file includes a parameter, showMaxPageScroll, that controls the display of the Max Page Scroll buttons. Setting this parameter to "true" enables the display of the Max Page Scroll buttons in the Form Template, and setting the parameter to "false" hides the display of the Max Page Scroll buttons. The default value for this parameter is "false". The parameter is required for a fix that is provided in this fix pack. For details about how to implement this parameter, see Install this fix pack.
Under some conditions, a thread on an application server might stop. The eforms-preferences.xml file includes a parameter, <httplookup timeout="x"/>, that allows you to specify a timeout value and prevent a "hung thread condition." For details about how to implement this parameter, see Install this fix pack.
The eforms-preferences.xml file now includes a disableButtonFor parameter that allows you to specify the length of time the toolbar is disabled after a button is clicked. For details about how to implement this parameter, see Install this fix pack.
The eforms-preferences.xml file now includes a canDeleteSelfSigned parameter that allows you to specify whether a signature cell can be deleted. For details about how to implement this parameter, see Install this fix pack.
The eforms-preferences.xml file now includes an formCalToTakePrecedence parameter for templates where you want the cell calculation to have precedence over the mapped WF data field values for that cell. When the parameter is set to true for a template, the system ignores the isModified flag in the code when invalidating the cells, and the user always sees the cell calculation as the end result. For details about how to configure the formCalToTakePrecedence parameter, see Install this fix pack.
In eForms 3.5.1, when the you have a form field configured for performing both lookup and holding the result data, the cell's value was not cleared when no matching records are returned. In eForms 4.0.2, this form field's data is cleared when no matching records are returned. To enable the 3.5.1 feature, the eforms-preferences.xml file now includes a clearLookupCells parameter that you set for each template of in-process documents. This parameter is by default "false" for all templates.
In eForms 3.5.1, Launch and Complete were Save Actions. In eForms 4.0.2, Launch and Complete are changed to Export Actions so that the Allow exporting data setting in Error Handling (set at the design time in eForms Designer) has effect on the Launch and Complete action.
The eforms-preferences.xml file now includes an allowExportingIncompleteData parameter that you set for each template of in-process documents. For details about how to configure the allowExportingIncompleteData parameter, see Install this fix pack.
The prefill mechanism is intended for internal IBM use only, and is deprecated for P8 eForms 4.0 and later versions. The " prefill using a parameter" mechanism does not operate exactly as it did in eForms 3.5.1. To provide prefill data to the form, use the "post" or "get" mechanism. With this new design, the prefill data must be in Canonical Format. Failing to pass the data in Canonical Format will cause exceptions, such as, for example, "Unable to convert that value to a date."
The eforms-preferences.xml file supports a new customer preference that applies customer-specific configuration at the Template Level. The new preference is:
The customer node is reserved for the customer preferences, and is used to apply the preferences to specific versions of the template.
For details about how to implement the new customer node structure, see Install this fix pack.
To prevent the processing of code within <script> tags for scripting code embedded in a template, enter the following in the ~/FileNet/Config/AE/eforms-preferences.xml file:
<customer removeScriptTag="true"/>
The above entry is required for the fixes provided in this fix pack.
To enable accessibility features, make the following entry in the ~/Config/AE/eforms-preferences.xml file:
<accessibility workaroundEnabled="true" />
The above entry is required for the fixes provided in this fix pack.
To enable removal of the <script> tag from the embedded script code, make the following entry in the ~/Config/AE/eforms-preferences.xml file:
<customer removeScriptTag="true" />
The above entry is required for the fixes provided in this fix pack.
Before installing this fix pack, verify that you have an installed copy of the latest IBM FileNet P8 Platform Documentation package. This documentation package contains additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.
NOTE Search is enabled in the help system only if you have installed the help system as a web site on a web server that supports Java™ applications.
The following component must be installed before installing this fix pack:
NOTE Application Engine (AE) and Workplace XT each have their own installer for each of the supported operating systems.
UNIX®: Log on as root.
Windows®: Log on as a member of the local administrators group or a user with equivalent permissions.
NOTE If the installation wizard displays the Replace Existing File dialog, and prompts you to replace the FNP8EF0400.SYS2 file, click Yes to All.
Important After this fix pack is installed for IBM FileNet P8 eForms, if you install a fix pack to WorkplaceXT 1.1.4.x or Application Engine 4.0.2.x, the changes added for 4.0.2.12-P8eF-FP012 will be overwritten. In order to resolve this situation, If you install a fix pack to WorkplaceXT 1.1.4.x or Application Engine 4.0.2.x after the eForms fix pack 4.0.2.12-P8eF-FP012 has been installed, you must run the eForms fix pack 4.0.2.12-P8eF-FP012 again to reinstate the changes for eForms 4.0.2.12-P8eF-FP012 to WorkplaceXT 1.1.4.x or Application Engine 4.0.2.x.
Alternatively, you can manually edit the "eforms-integration.xml" file (found under: <server deployment>/config/AE for Application Engine or under: <server deployment>/config/WebClient for WorkplaceXT) and include the following node under the <platforms> node
<platform platformID="filenet"
templateMimeType="application/x-filenet-itxformtemplate"
templateFilenameExtension="itx"
dataMimeType="application/x-filenet-formdata"
dataFilenameExtension="ifx"
readOnlySupported="true"
pageTabConfigurationSupported="true"
toolbarRelocationSupported="true"
offlineSupported="true">com.filenet.eforms.core.platforms.FactoryImpl</platform>
Follow the instructions in this section if you are upgrading from from eForms for P8 V3.5.1 or earlier.
In version 4.0 of IBM FileNet eForms for P8, a new Java API was introduced as well as additional, extensive error handling. While every effort was made to ensure smooth solution migration from eForms for P8 versions prior to 4.0, some situations may require modification of existing eforms templates and additions to the eForms preferences file. Because of new functionality in eForms for P8 4.0.2, a number of changes may be required to processes for creating new templates, depending on your implementation of eForms for P8. Use the following information to help you:
Implement the following solutions as appropriate for your configuration.
NOTE In some cases, you may need to migrate processes that are currently running (workflows that contain documents which are still processing) and, as such, modifications cannot be made to the associated form templates. These processes can be fixed by adding new preference settings to the eforms-preferences.xml file, outlined below, to ensure forms and related data process correctly in P8.
Condition
Embedded scripts are now supported in eForms for P8. Any scripts that were entered in the embedded script section of a form template in eForms for P8 3.5.1 were ignored. Scripting is now enabled and, as such, eForms for P8 will attempt to run any embedded scripts within your templates. When eForms for P8 encounters embedded scripts, errors are generated.Solution
To rectify this potential situation, review your templates for embedded scripts and remove them.In-process solution
Manually add the following preference setting to the eforms-preferences.xml file to correct potential issues, where appropriate, based on your specific IBM FileNet eForms for P8 3.5.1 configuration. For in-process templates, make any embedded scripts inactive by adding the removeScriptTag to the eforms-preferences.xml file and setting the parameter value to true.All embedded scripts, included within <script></script> tags, will then be ignored in eForms for P8 4.0.2 or later.
Example
<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer removeScriptTag="true">
</customer>
</preferences>
Condition
Use of the autoUrlEncoding feature to automatically encode all URLs is no longer supported in eForms for P8.Solution
If you used the autoUrlEncoding=true preference in your eForms for P8 3.5.1 form.properties file, to maintain this functionality you must modify each form template in eForms for P8 4.0.2 and later to use the external URLEncode feature for each cell where URL encoding is required.In-process solution
Manually add the following preference setting to the eforms-preferences.xml file to correct potential issues, where appropriate, based on your specific IBM FileNet eForms for P8 3.5.1 configuration. For in-process documents, you must add the following preference to the eformspreferences.xml file for each template containing a cell for which you want the value to be encoded:<template uri="p8:{object store ID}.{template ID}">
<autoUrlEncodingEnabled>true</autoUrlEncodingEnabled>
</template>You must add the template node entry multiple times, as appropriate, to specify multiple templates.
To obtain the object store ID for Workplace or Workplace XT, right-click the object store name and select Properties.
To obtain the template ID in Workplace:
- Right-click the template and select Properties.
- Click Show system properties.
To obtain the template ID in Workplace XT:
- Right-click the template and select More Information > All Properties.
- Click Show system properties.
Example
<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID1}.{template ID1}">
<autoUrlEncodingEnabled>true</autoUrlEncodingEnabled>
</template>
<template uri="p8:{object store ID2}.{template ID2}">
<autoUrlEncodingEnabled>true</autoUrlEncodingEnabled>
</template>
<template uri="p8:{object store ID3}.{template ID3}">
<autoUrlEncodingEnabled>true</autoUrlEncodingEnabled>
</template>
</templates>
</customer>
</preferences>NOTE Apply this setting only to correct in-process, problematic form templates. For all new form templates and policies, you must use the external URLEncode feature for each cell in which you want the value to be encoded.
Condition
If you designed a form for eForms for P8 3.5.1 and enabled the Allow saving data option under Actions allowed with invalid data section of the Error Handling settings window, the Launch and Complete actions, when filling out the form in P8, allowed exporting of data in cases where the form contained invalid data. In eForms for P8 4.0.2 and later, the Allow saving data option in the error-handling section of eForms Designer no longer has an effect on the Launch and Complete actions for the form.This change resulted because Launch and Complete actions have been changed from an isSaveAction in eForms for P8 3.5.1 to an isExportAction. For more details, see the Class Command section of the eForms Java API Reference help.
Solution
In eForms for P8 4.0.2 and later, you must now set the Allow exporting data error-handling option in the Error Handling settings window to allow data to be exported from forms which contain invalid data.In-process solution
Manually add the following preference setting to the eforms-preferences.xml file to correct potential issues, where appropriate, based on your specific IBM FileNet eForms for P8 3.5.1 configuration. For in-process documents, you must add the allowExportingIncompleteData entry to the eforms-preferences.xml file and set the value to true for each template in which you want error handling to allow the Launch and Complete action to export data when a form contains invalid data:<template uri="p8:{object store ID}.{template ID}>
<allowExportingIncompleteData>true</allowExportingIncompleteData>
</template>Example
You must add the template node entry multiple times, as appropriate, to specify multiple templates.<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID1}.{template ID1}>
<allowExportingIncompleteData>true</allowExportingIncompleteData>
</template>
<template uri="p8:{object store ID2}.{template ID2}>
<allowExportingIncompleteData>true</allowExportingIncompleteData>
</template>
<template uri="p8:{object store ID3}.{template ID3}>
<allowExportingIncompleteData>true</allowExportingIncompleteData>
</template>
</templates>
</customer>
</preferences>
Condition
In eForms for P8 3.5.1, no API was available to perform cell prefill activities for forms. Some clients implemented use of performing prefill activities such as through the parameter mechanism. In eForms for P8 4.0, Application Engine UI service command mechanisms (post and get) were introduced to handle prefills.Calls that do not adhere to the AEUI post and get mechanism requirements are not supported and must be removed. Non-standard calls will typically produce an error such as, Unable to convert that value to a date.
Solution
Change all the prefill calls that use the parameter mechanism to instead use the AEUIS commands, post and get. For details on the use of these commands, refer to the Application Engine UI Service Command Reference section of the P8 Platform Help.NOTE Any data returned to eForms for P8 will be in canonical format.
Condition
In eForms for P8 3.5.1, null values (empty strings) were treated as populated data fields. In eForms for P8 4.0 and later, null values are handled as unpopulated fields, which contain no data and, as such, null values are not mapped.Solution
If your eForms for P8 3.5.1 configuration uses mapped null (empty string) values from workflow data fields to form fields, to ensure continued support of this functionality, you must add the following entry to the bootstrap.properties file and set the value to true:eFormsDefaultMapNullValue=value
If the value is not set, eForms for P8 will default this value to false and will not map null values.
<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer>
<strictNumberParsing>false</strictNumberParsing>
</customer>
</preferences>
<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID}.{template ID}">
<clearLookupCells>true</clearLookupCells>
</template>
</templates>
</customer>
</preferences>
<?xml version="1.0" encoding="utf-8" ?>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID}.{template ID}">
<autoUrlEncodingEnabled>true</autoUrlEncodingEnabled >
</template>
</templates>
</customer>
</preferences>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID}.{template ID}">
<allowExportingIncompleteData>true</allowExportingIncompleteData>
</template>
</templates>
</customer>
</preferences>
<preferences>
<customer>
<templates>
<template uri="p8:{object store ID}.{template ID}">
<formCalToTakePrecedence >true</formCalToTakePrecedence>
</template>
</templates>
</customer>
</preferences>
To prevent the deletion of signature cells, set the canDeleteSelfSigned parameter to false.
<preferences>
<customer>
<signature canDeleteSelfSigned="false" />
</customer>
</preferences>
To display the Max Page Scroll buttons in a Form Template, set the showMaxPageScroll parameter to true.
<preferences>
<javascript showMaxPageScroll="true" />
</preferences>
If desired, set a timeout value for application server threads in the eforms-preferences.xml file.
<preferences>
<httplookup timeout="x"/>
</preferences>
<preferences>
<displaypdfinline>true</displaypdfinline>
</preferences>
<preferences>
<javascript useCellDisplayName="true" />
</preferences>
To prevent the drawing of the Focus Rectangle, set the showFocusRectangle parameter to false.
<preferences>
<customer>
<showFocusRectangle>false</showFocusRectangle>
</customer>
</preferences>
To set the length of time the toolbar will be disabled after a button is clicked, set the disableButtonFor paramter (in seconds). In the following example, the time is to 30 seconds. With this setting, when a toolbar button is clicked the toolbar will be disabled for 30 seconds.
<preferences>
<toolbar disableButtonFor="30"/>
</preferences>
Redeploy Workplace or Workplace XT on your application server. For instructions, refer to the FileNet P8 Platform Installation and Upgrade Guide for Application Engine or the Workplace XT Installation and Upgrade Guide.
This fix pack does not have an uninstall option. For support, see "Contact customer support".
The table below lists the fixes and features in this fix pack. The following abbreviations are used:
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
968129 |
Fix |
$defaultHandler is undefined error when opening form via AJAX in ICM. |
|
968130 |
Fix |
$.$frm is undefined error when loading form in ICM. |
|
968651 |
Fix |
With Firefox 4.0 and higher, we are able to resize a P8 eForm field. As a result, UI can be made messy. |
|
966688 |
Fix |
Performing a lookup from a non-visible row of a table generates an undefined null error. |
|
PJ38938 |
968184 |
Fix |
When a required validation error occurs, the cursor is placed on the last invalid cell of the template. |
PJ39139 |
968195 |
Fix |
CreationDate no longer works since upgrading to P8eF-4.02. |
965765 |
Fix |
New eForms Java API to be consumed by IBM Forms for destroying Form Object. |
|
PJ39067 |
962636 |
Fix |
Cannot launch eForm after selecting date on eForm. |
PJ39066 |
962638 |
Fix |
eForms Today button in the date picker doesn't work correctly. |
967159 |
Fix |
Errors and other dialogs are not modal when using Firefox even though modal dialogs are implemented in Firefox3.0. |
|
967267 |
Fix |
Go To button causes a JavaScript error when focusing a cell on another page. |
|
970116 |
Fix |
Cell cannot be committed unless it has been previously focused in ICM. |
|
PJ39384 |
970104 |
Fix |
Get INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified when saving the Form. |
969600 |
Fix |
When enabling a DateTime cell via an API, calendar control displays without mousing over the cell. |
|
972431 |
Fix |
Right-click of form fields is not enabled in ICM. |
|
972457 |
Fix |
The onForm button in P8 eForm template does not display the label in Internet Explorer 9. |
|
PJ39587 |
974841 |
Fix |
Choicelist value appears null when opening data documents created with P8eF-4.0.1-FP002. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
955515 |
Fix |
eForms installer changes made to register the eForms platform. |
|
PJ38964 |
958220 |
Fix |
User encounters "'$.$frm.fp.fCurentPage.number' is null or not an object" error when opening a form with custom load handlers in IE8. |
PJ38435 |
939189 |
Fix |
Required cell color doesn't get cleared after value is populated by a lookup result. |
PJ38542 |
942212 |
Fix |
PDF rendering results in a dark and unclear background. |
PJ38574 |
944028 |
Fix |
Get redundant warning message when clicking "Close" on version of form data document not associated with active workflow. |
PJ38658 |
946283 |
Fix |
Get "An error has occurred in the script on this page " error when printing PDF. |
PJ38433 |
939160 |
Fix |
When using IE 8, Work Data eForm widget takes a long time to merge data on table cells and render it. |
PJ38559 |
944019 |
Fix |
Using an external URL for the router region layout and typing in region text field causes permission denied error. |
PJ38430 |
939796 |
Fix |
Scrollable table does not show the scrollbar when user has only 'Content View' permission to the form document. |
PJ38543 |
942851 |
Fix |
When rendering to PDF an extra space is placed before a changed word in terms of its style, font, and color. |
PJ38544 |
944150 |
Fix |
eForm form data cannot be opened in WorkplaceXT if date field contains non-date characters. |
PJ38709 |
948018 |
Fix |
eForms Calendar is cut off when displayed. |
PJ38798 |
951112 |
Fix |
eForms custom javascript - Error Handler redirects to Browse page in IE. |
PJ38938 |
957028 |
Fix |
When a required validtion error occurs upon a toolbar button click the cursor is placed on the last invalid cell of the template. |
PJ38738/ PJ38434 |
948914/ 939746 |
Fix |
I-Sign(Ink) signature support has been extended to the Signotec Sigma-Pad signature device. |
PJ38918 |
955662 |
Fix |
When clicking on toolbar button on form policy receive error $.$previosCellFocus is null or not an object. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ38184 |
930511 |
Fix |
A number formatter cell does not parse a string value that has text in it as it did in eForms 3.5.1. |
904326 |
Fix |
Disabled radio buttons or checkboxes do not display correctly. |
|
928915 |
Fix |
In a Japanese browser, a date cell with a date format "yyyy/mm/dd" does not display correctly when the day is from 10 to 12. |
|
746683 |
Fix |
The exponent (^) function produces the wrong value when the form is loaded. |
|
788206 |
Fix |
DatePicker is not available in DateTime cell (both field and table cells) if a choicelist is configured to the cell. |
|
790342 |
Fix |
Opening a form with a TimeFormatted Choicelist cell throws an exception. |
|
906813 |
Fix |
Entering values in a table with a scrollbar beyond the visible rows results in an error. |
|
916566 |
Fix |
Check calculation in a CheckBox table cell shows two error messages when any other checkbox in another row in the same column is clicked. |
|
931677 |
Fix |
If the focus is taken away from a checkbox via JavaScript API, the checkbox state is updated only when the user tabs out of the cell. |
|
PJ38281 |
933628 |
Fix |
When warning checks are displayed, they appear in an Error web dialog message rather than in a more appropriate Warning web dialog message. |
PJ38304 |
936216 |
Fix |
Required eForms table cells are shown in color, to incorrectly indicate that the entire table cell data is required. |
PJ38364 |
937172 |
Fix |
A signature cell that is the current cell and is not tabbed out of will recommit its value if the user selects a toolbar command with the mouse, causing recalculation of dependent cells, overwriting data intentionally set via script or user action. |
937955 |
Fix |
eForms API introduced to support Page Ordering feature change. NOTE This fix requires the installation of 4.0.2.10-P8AE-FP010. For more detail, see New in this fix pack. |
|
PJ38299 |
938023 |
Fix |
When saving a form with Document Policy, the user receives the error: "InvalidCast - Unable to convert that value to a boolean." |
PJ38184 |
PJ38184 |
Fix |
A cell of format Number which has a calculation calling a text cell remains blank when the value entered in the text cell contains a letter. This fix requires the implementation of the strictNumberParsing parameter. For details about how to implement this parameter, see Install this fix pack. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ37240 |
909307 |
Fix |
The data clears from a cell when using CTRL+V keys to paste text that is greater in length than the limit of the cell. |
PJ37828 |
902450 |
Fix |
Arabic text disappears or becomes illegible after using the print to PDF option on eForms 4.0.2 patch 4. |
PJ37907 |
914158 |
Fix |
A second choice list does not update dynamically after the user changes the selection on the first choice list on which the second choice list is dependent. |
PJ37917 |
914428 |
Fix |
In an eForm Multi-line text field with Auto Shrink option enabled, the user cannot generate a PDF after inserting only ENTER in the text field. |
PJ37922 |
909237 |
Fix |
Clicking on the PDF button on a form with multiple validation errors generates two warning messages. |
PJ37957 |
913995 |
Fix |
Data is clipped at the bottom when typing into cells. This fix requires the implementation of the showFocusRectangle parameter. For details about how to implement this parameter, see Install this fix pack. |
PJ37977 |
914437 |
Fix |
When a user clicks the Launch button on a form, the system displays the checks from other pages that are not designed to be visible. |
PJ37999 |
913407 |
Fix |
The font size for text in some cells decreases when rendered to PDF. |
PJ38043 |
920115 |
Fix |
Moving the eForms window before it is fully rendered causes an Access Denied error. |
PJ38044 |
920114 |
Fix |
Not tabbing out of the cell prior to clicking Save in a multi-page eForm might not save the data in the cell. |
PJ38045 |
920124 |
Fix |
Quickly tabbing through multiple pages results in two error messages: Unable to convert that value to a number and this.cell.enabled is null or not an object. |
PJ38075 |
922281 |
Fix |
Hyperlink button with a transparent fill that overlaps with an adjoining cell blanks out the text on the adjoining cell. |
PJ38103 |
922971 |
Fix |
The user receives the error, "The format of the provided locale 'EN_x' does not resemble that defined in RFC 3066" when opening a form. |
PJ38129 |
925267 |
Fix |
When checks are displayed, the Error-Web dialog box appears blank until the user glides the mouse over the box. |
PJ38138 |
926363 |
Fix |
Clicking in the content of a single page or the last page of a form that is rendered to PDF causes Acrobat Reader version 8 or 9 to be unresponsive. |
PJ38159 |
928273 |
Fix |
The form.getCurrentCell() method returns the wrong cell name for the current checkbox. |
759204 |
Fix |
Calculated choice list in a scrollable table throws an error when a user scrolls the table or inserts a row. |
|
890682 |
Fix |
In a scrollable table, eForms does not display the error handling color in the correct row. |
|
910607 |
Enh |
Lookup data that contains extra spaces at the end when returned to a choice list of a cell does not get saved. |
|
915914 |
Fix |
Extra characters are appended to an alert message when a field is invalid. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ37721 |
001517 |
Fix |
I-sign(ink) is not supported since eForms version 4.0.2, but the Release Notes mention that it is still supported. |
PJ37722 |
896098 |
Fix |
An error occurs while opening an eForm case after the client locale is modified. |
PJ37723 |
903903 |
Fix |
The PDF generated from eForms shows missing space between the lines of text content. |
PJ37724 |
896924 |
Fix |
In P8eF 4.0.2, the CTRL+C keystroke does not work on a locked or signed cell. |
PJ37737 |
899362 |
Fix |
After LOOKUP is launched, the header of the multi-result lookup dialog shows field names instead of display names, and it cannot be localised. |
PJ37772 |
903466 |
Fix |
Using a call to HtmlFormRenderer.setReadOnly(true) to set all eForm fields to be read only does not take affect for checkboxes and radio buttons. |
PJ37636 |
903908 |
Fix |
Users cannot justify the text in eForms. |
PJ37812 |
904056 |
Fix |
A check mark does not appear in a checkbox when there is a check and JDBC lookup on the checkbox cell. |
PJ37822 |
903906 |
Fix |
The system displays an unnecessary Open/Save prompt with PDF print. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ32351 |
740921 |
Fix |
An optional cell with check calculation draws pink, which indicates a required cell. |
PJ36869 |
847002 |
Fix |
A value that does not exist in the database is not allowed in the JDBC Lookup returned field. |
PJ37392 |
864495 |
Fix |
Users can select disabled radio buttons. |
PJ37393 |
861733 |
Fix |
eForms cannot manage a timeout and halts a thread process on WebSphere Application Server. This fix requires implementation of <httplookup timeout= /> in the eforms-preferences.xml file. For details, see Install this fix pack. |
PJ37441 |
890601 |
Fix |
Choice list allows users to enter a value that is not from the drop-down menu, even though Allow Other Value is not selected. |
PJ37460 |
865696 |
Fix |
The Loop function does not work as expected. |
PJ37461 |
865750 |
Fix |
The system cannot disable the datetime field by using a script within an eForm. |
PJ37464 |
866399 |
Fix |
The system displays an alert message even when the column cell has a valid value, and appends extra characters to the alert message. |
PJ37625 |
893731 |
Fix |
The max scroll left and right buttons are not visible. This fix requires the application of the showMaxPageScroll parameter. See Install this fix pack. |
PJ37634 |
894349 |
Fix |
Required check box displays differently after an upgrade to eForms 4.0.2-006. |
PJ37662 |
867106 |
Fix |
When the user clicks on another tab before one is fully rendered, the system displays the error " this.bUp is null or not an object." |
PJ37753 |
895517 |
Fix |
When a user works on a form, the system displays the error "The callee (server not server application) is not available and disappeared; all connections are invalid. The call did not execute." |
PJ37756 |
891513 |
Fix |
A rectangle, with a double-line style on the master page, shrinks on subsequent pages when a PDF is generated. |
748525 |
Fix |
If a cell does not exist, the Submit response generates an error. |
|
748542 |
Fix |
When a user tabs into a date cell in a table with a scroll bar, the system does not display the date selector. |
|
753456 |
Fix |
A table with conditional tabbing does not function when it is deployed to IBM FileNet P8 Workplace. |
|
853710 |
Fix |
Users can change the value of a radio button after it is signed. |
|
860428 |
Fix |
Users can change the value of a check box after it is signed. |
|
862065 |
Fix |
User cannot change the content in the cell has a character limit and and the limit is reached. |
|
891542 |
Fix |
When a user checks a cell with a choice list and clicks into another cell, the system does not display an alert. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ37036 |
850910 |
Fix |
Signature cells can no longer be locked when locked by another Signature cell or itself. This fix requires the application of the canDeleteSelfSigned parameter. See Install this fix pack . |
PJ37042 |
851268 |
Fix |
Check does not trigger for a checkbox or a radio button boolean cell if it is preceded by a choice list cell. |
PJ37059 |
852969 |
Fix |
P8eF 4.0.2 - Internet Explorer memory leak causes slow response time. |
PJ37078 |
852967 |
Fix |
P8eF 4.0.2 is slower than 3.5.1 P8eF. |
PJ37079 |
852972 |
Fix |
Users encounter 30-second (or longer) delay when switching tabs for the first time in a BPF eForm case. |
PJ37093 |
852976 |
Fix |
Get error: 'Not Implemented' when calling the setChoiceList on a Cell. |
PJ37123 |
854361 |
Fix |
The timeout value for DisableToolbarBtnsFor property in P8 4.0.x is hard-coded and the setting is not configurable. |
PJ37126 |
854550 |
Fix |
The status bar is enabled on the eForm signature dialog. |
PJ37158 |
855511 |
Fix |
Lookup on a Column cell, and populating the lookup result on the current row of the table, do not work in eForms 4.0.x. |
PJ37240 |
857144 |
Fix |
The maximum character exceeded function does not work for a text field on a deployed eform. |
PJ37325 |
857380 |
Fix |
An error occurs when a user clicks on another tab before one is fully rendered. |
852637 |
Fix |
eForms - FF - Blank choiceList cell can be changed even when the form is signed. |
|
858880 |
Fix |
OutOfMemoryError: eForms continues to create a thread in the timer. |
|
860185 |
Fix |
eForms - Calculation works very slowly and leads to incorrect results. |
|
PJ37123 |
854361 |
Fix |
The timeout value for disabling toolbar buttons is now configurable. This fix requires the application of the disableButtonFor parameter. See Install this fix pack . |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ36700 |
842900 |
Fix |
Page controls do not display in a template with many page tabs when the browser window is maximized. |
PJ36736 |
842897 |
Fix |
A PDF that is generated from eforms shows overlapping data. |
PJ36854 |
845079 |
Fix |
When there is a mapped value from the PE data field and a form calculation on the same cell, the mapped value is kept. |
PJ36869 |
847002 |
Fix |
A value that does not exist in the database is not allowed in the JDBC Lookup returned field. |
PJ36909 |
847009 |
Fix |
Very slow page navigation response times. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ36529 |
833622 |
Fix |
On a form template, the system displays this error: "com.filenet.eforms.api.FormException: The PDF document cannot be rendered: cannot render this font." |
PJ36531 |
833618 |
Fix |
When auto-increment lookup returns values for cells that do not exist on the form template, the system generates an java.util.ConcurrentModificationException error. |
PJ36540 |
834279 |
Fix |
Users receive a chained exception with one form when attempting to render to PDF. |
PJ36546 |
829817 |
Fix |
Choice lists with 0 or 1 items are displayed with a drop-down menu. |
PJ36569 |
835930 |
Fix |
The error handling of an eForm with "allow data saving" enabled does not allow the launch of a form when the criteria for F_StepLaunch has been met. |
PJ36582 |
836715 |
Fix |
A cell that is defined as Boolean does not retain the choice list value that is defined as text. |
PJ36583 |
836956 |
Fix |
The Form launch step fails with an IndexOutOfBoundsException error. |
PJ36599 |
837895 |
Fix |
Check calculation, involving a table cell, starts unexpectedly. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ36300 |
819454 |
Fix |
Mapping fails from an eForms number cell to a Process Engine Float data field. |
PJ36379 |
823651 |
Fix |
The Submit response returns data to a cell that produces an error if the cell does not exist. |
PJ36380 |
823498 |
Fix |
The Cell[Row] contains the value of all of the cells in the table if the calculation includes '&'. |
PJ36386 |
823639 |
Fix |
HTTP lookup fails with "The HTTP request returned the unexpected status code 505" error. This fix requires the application of the autoUrlEncodingEnabled preference. See Install this fix pack . |
PJ36387 |
823641 |
Fix |
HTTP lookup fails with "The HTTP response data was formatted incorrectly." message. |
PJ36456 |
828690 |
Fix |
The Display option for the model tag does not function. |
PJ36457 |
828693 |
Fix |
Users are unable to set the column display order in the Multiple Lookup Results dialog box. |
PJ36458 |
828699 |
Fix |
Lookup fields that are not mapped to eForm template cells do not display in the Details list. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ34877 |
391743 |
Fix |
When a signature locks multiple cells, navigation through the signature cell is slow. |
PJ35627 |
784077 |
Fix |
Enabling MasterPage cells results in the following error: "$.$frm.$findPage(...).number is null or not an object". |
PJ34680 |
784800 |
Fix |
Users can open multiple I-Sign (Ink) signature screens. |
787611 |
Fix |
The page.OnLoad event does not function when the form is on loading (page is the default page1), and when the javascript event is defined in a sidebar html file. |
|
787861 |
Fix |
The OnBlur event does not execute when a user clicks on a cell in the form. The event handler fails to get the value of the OnBlur object cell. |
|
787904 |
Fix |
After a user enters data into Cell A, the value of Cell A does not commit and the OnFocus handler does not get the value of Cell1 when putting Cell B in focus by clicking on Cell B. |
|
788329 |
Fix |
A custom cell OnBlur event that causes a page change functions inconsistently when a user clicks other cells after entering data. | |
788419 |
Fix |
A user can change locked choice list cell values by using the arrow and Enter keys. | |
PJ35575 |
791253 |
Fix |
Publishing an eForm to PDF causes fields to appear misaligned. |
PJ35544 |
792132 |
Fix |
The Tokenize function in a table does not operate as expected under certain conditions. |
PJ35583 |
792568 |
Fix |
Embedded scripts within <script> and </script> tags, that were ignored in 3.5.1, are getting executed after 4.0.1 migration. |
PJ35673 |
794044 |
Fix |
An error occurs when a user enters a value of zero for a numeric field. |
PJ35719 |
794348 |
Fix |
Users can only select one YES/NO button for all rows, rather than select one on each row. |
PJ36143 |
795277 |
Fix |
Signatures in tables are not supported in P8 eForms. |
PJ35580 |
797404 |
Fix |
eForms can not find the expected choice list item and perform the auto-completion correctly. |
798732 |
Fix |
The Choice list floats at the top left corner of the browser's window on Firefox 3.0/ WindowsXP and Firefox3.0/Mac. | |
799198 |
Fix |
eForms displays an error message when a user tabs into a recommended or required cell. |
|
799755 |
Fix |
The OnBlur event executes unexpectedly when a user clicks a recommended or required cell after focusing on another recommended or required cell. |
| APAR Name | Defect # | Type | Description |
|---|---|---|---|
PJ33177 |
748550 |
Fix |
Selecting an item from a choice list field requires multiple mouse clicks. |
PJ33600 |
662199 |
Fix |
The SpellNumberTH function returns an incorrect spelling for numbers that that are greater than 10 and end in zero; for example 20, 100, or 2500. |
PJ35160 |
787097 |
Fix |
Customer cannot open an eForm with the <script> tag within Workplace. |
PJ34785 |
787223 |
Fix |
The eForms onBlur event gets triggered twice after a user clicks the mouse. |
PJ34854 |
787102 |
Fix |
The system displays a box around radio buttons and checkboxes. |
PJ34879 |
394352 |
Fix |
After a user sets a page as not printable with the API method Page.setPrintable(false), the page still prints. |
PJ34954 |
783825 |
Fix |
Some data on the expandable rows overflow page is missing after generating a PDF file. |
PJ34992 |
785409 |
Fix |
An out of bounds exception occurs while iterating through the Built-in commands collection. |
PJ35227 |
787332 |
Fix |
the I-Sign(link) signature time stamp shows that the time difference between AE and the client is doubled. |
PJ34855 |
787100 |
Fix |
The eForms text is not readable when High Contrast settings are used. |
PJ35337 |
787094 |
Fix |
The Internal URLEncode function in an eForm does not work. |
PJ35170 |
786014 |
Fix |
Some Calendar Menu functions do not work correctly. |
PJ35398 |
787258 |
Fix |
SpellCurrency does not display correct amount. |
PJ35253 |
782528 |
Fix |
The pointer does not focus on the salary small cell field after the user presses the Enter key. |
PJ35254 |
786431 |
Fix |
Users cannot insert PNG image files into a picture cell. |
PJ35255 |
782516 |
Fix |
Users cannot insert a BMP file into a policy. |
PJ35256 |
783387 |
Fix |
The Shift+Tab keystroke does not function properly while users navigate picture cells. |
PJ35257 |
782521 |
Fix |
An alert dialog box does not display when a user inserts a GIF file without an address into a policy. |
PJ35259 |
780896 |
Fix |
eForms does not update the picture value in copied cells. |
PJ35260 |
759211 |
Fix |
The check list does not function properly in Safari on Mac. |
PJ35262 |
783340 |
Fix |
The "Scroll Right" spin button does not function when a user resizes a form template horizontally to the left. |
PJ35739 |
754743 |
Fix |
ChoiceList does not work on Vista/Safari 3.0. |
782530 |
Fix |
The Close button does not close a form opened from a link in Firefox 3.x. |
For information about contacting customer support:
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.