Product Readmes
Abstract
This document describes how to download and install IBM FileNet Business Process Framework Version 4.1.0 Fix Pack FP006
Content
Document Information
Readme for: IBM Business Process Framework
Release: Version 4.1
Update name: Fix Pack 6
Fix ID: 4.1.0.6-P8BPF-FP006. This Fix ID applies to all platforms.
About the fix pack
The IBM FileNet Business Process Framework 4.1.0.6-P8BPF-FP006 fix pack includes updates to BPF Explorer, BPF operations, and BPF Web application.
The fix pack is intended for installation on an existing BPF-4.1.0 GA, BPF-4.1.0-001, BPF-4.1.0-002, BPF-4.1.0-003, BPF-4.1.0-004, or BPF-4.1.0-005 system that is running in a FileNet P8 4.0.x, 4.5.x, or 5.0.x environment. If you have not yet installed Business Process Framework, you must install the BPF-4.1.0 GA software before installing this fix pack. For instructions, see the IBM FileNet Business Process Framework Installation and Upgrade Guide.
New in this fix pack
For details about the problems that were resolved in this release, see Problems solved.
Introduced in fix pack BPF-4.1.0-002
For details about the problems that were resolved in this fix pack, see Problems solved.
Fix pack BPF-4.1.0-002 includes the following new features:
- "Hide Inbaskets when opening Case" option restored
- New settings for Dialog windows in BPF Explorer
- Add Workplace Command 3010, ShowProperties, into the Attachment context menu in BPF
- Multilingual resources added into this fix pack
"Hide Inbaskets when opening Case" option restored
This fix pack restores the BPF 3.5.2 Preferences option "Hide Inbaskets when opening Case" in the BPF Web application.
A BPF user can enable this option only in the default layout - that is, if the BPF user's role has not been assigned a different layout using the BPF Layout Designer.
If the "Hide Inbaskets when opening Case" option is enabled, the BPF Web application behaves as follows when a user opens a case either automatically in GetNext/Sequential mode or by double-clicking a case record in Browse mode:
- The Logo, Filters and Inbaskets List Web modules, which typically appear on the left side of the Web page, are hidden.
- The Case detail area is expanded to occupy the entire Web page.
- An Inbaskets drop down list, which contains all available Inbaskets, is displayed after the Roles drop down list in the Status bar. The user can change to another Inbasket by selecting the Inbasket from this list.
When the user closes the case and returns to the Cases list, the Logo, Filters and Inbaskets List modules reappear and the Inbaskets drop down list is hidden.
New settings for Dialog windows in BPF Explorer
Setting | Default | Description |
---|---|---|
Action Dialog Window Dimensions in px | 350*550 | This setting configures the height and width dimensions of the Action Dialog window that appears when a user of the BPF web application selects an Action on which one or more Reasons have been configured. |
Whether Action Dialog Window can be resizable | False | If set to True, Action Dialog Window can be resized. Otherwise, Action Dialog Window cannot be resized. |
Whether Action Dialog Window can be scrollable | True | If set to True, a scroll bar is displayed in the Action Dialog window if the window cannot display all of the Reasons and buttons. If set to False, no scrollbar is displayed in the Action Dialog window. |
Add Workplace Command 3010, ShowProperties, into the Attachment context menu in BPF
This fix pack adds the ShowProperties (Workplace Command 3010) action into the Attachment context menu. By selecting this action, users can review the properties of attachments.
Multilingual resources added into this fix pack
Starting with this fix pack, multilingual resources are added to the BPF fix pack instead of being provided in separate language packs. The fix pack includes the following locales: de, es, fi, fr, it, ja, ko, pl, pt-BR, zh-CN, and zh-TW.
BPF language resources are contained in the following files:
- <bpf-app>\WEB-INF\lib\bpfLangResources.jar
- <bpf-app>\WEB-INF\lib\bpfCustomLangResources.jar.
Localized Content Engine manifest XML files are located in the Translation folder of the fix pack. You can import the files of languages that you need into Content Engine by using Enterprise Manager.
Introduced in fix pack BPF-4.1.0-001
For details about the problems that were resolved in this fix pack, see Problems solved.
Fix pack BPF-4.1.0-001 includes the following new features:
- Support multiple Case tabs in BPF Web application
- Enhancements to the display order of an Inbasket which belongs to multiple roles
- "Display Inbasket tools in CASEQUERY Inbasket" option restored
- Enhancements to custom JavaScript EventHandlers
Support multiple Case tabs in the BPF Web application
This fix pack adds support for allowing multiple Case tabs in the BPF Web application.
It is now possible to configure multiple Case tabs and spread your inbasket case fields among them. Nevertheless, some configuration and custom coding (in the EventHandlers.js::onCaseDisplay method) is required. Refer to the IBM FileNet Business Process Framework Developer Guide for more information.
Enhancements to the display order of an Inbasket which belongs to multiple roles
Beginning with 3.6, BPF introduced a feature that allows users to assign multiple roles to a single inbasket. However, if you adjusted the display order of inbaskets for one role, the display order for other roles sharing the inbasket role were also changed.
This fix pack enhances the support for inbaskets that are shared by multiple roles by enabling you to set the inbasket display order for each role without affecting the display order for other roles.
"Display Inbasket tools in CASEQUERY Inbasket" option restored
This fix pack restores the BPF 3.5.2 behavior that the Inbasket Toolbar displays when opening a Case in the CASEQUERY Inbasket from the Search Results.
In addition, a new CASEQUERY Inbasket layout template file, Bp8CaseQueryLayout_TwoLines.xml, is provided to address the problem that caused the Toolbar to overlap the Case area if there were too many tools to be displayed on one line. Refer to Install new and changed files for information on using this file.
This change resulted from fixes to resolve defect 750011.
Enhancements to custom JavaScript EventHandlers
This fix pack introduces a new event, onBeforeDoLookupSearch, and enhances the event, onBeforeProcessLookupItem, by providing one more parameter, valueList, which is the handle to an XML DOM Node list object containing the values for whatever record. These two events are related to custom Lookups.
The onBeforeDoLookupSearch event is raised before a custom lookup URL is called. This allows the case field values passed to the custom lookup URL to be validated and/or formatted in a custom fashion to handle differences between the DATE or MONEY format in use on the BPF client, for example, and those expected by the lookup JSP or other resource.
For more information, please refer to the following:
- FileNet Business Process Framework (BPF) Developer Guide and the FileNet
Business Process Framework (BPF) Code Samples for BPF v4.1. These documents are available on the Product Documentation for Business Process Framework page.
This enhancement resulted from fixes to resolve APAR PJ34522.
Downloading the fix pack
To download the fix pack:
- Navigate to Fix Central (www.ibm.com/eserver/support/fixes/) and log in.
- Make the following selections and then click Continue:
- From the Product Group list, select Information Management.
- From the Product list, select FileNet Business Process Framework.
- From the Installed Version list, select 4.1.0.
- From the Platform list, select Windows.
- Select Browse for fixes and click Continue.
- Select 4.1.0.6-P8BPF-FP006 and click Continue.
- Select either Download using Download Director or Download using your browser (HTTP) and click Continue.
The fix pack now downloads.
Prerequisites
The 4.1.0.6-P8BPF-FP006 fix pack supports FileNet P8 5.0, P8 4.5.x and P8 4.0.x. At a minimum, the following components must be installed before you install this fix pack:
- P8CE-4.0.1 or later
- PE4.0.3.3 or later, PE4.5.1.1 or later, PE5.0 or later
- P8AE-4.0.1 with interim fix P8AE-4.0.1-000.001 or later
- P8 eForms 4.0.1 or later (Optional. Required only if you are using eForms with Business Process Framework.)
In P8 5.0 and 4.5.x, the Component Manager (CE_Operations) is optional. However, BPF 4.1 requires the Component Manager. For more information, see "Configuring and starting the Component Manager (on an Application Engine server)" in the IBM FileNet P8 Platform Installation and Upgrade Guide.
Compatibility
For information, see the IBM FileNet P8 Hardware and Software Requirements and the FileNet P8 4.5.x or P8 5.0 Fix Pack Compatibility Matrix or FileNet P8 4.0.x Dependency/Compatibility Matrix.
Certifications
- As of BPF-4.1.0-001, SQL Server 2005 is supported.
- As of BPF-4.1.0-003:
- DB2 V9.5 and Oracle 11g are supported.
- WebSphere 7.0, JBoss 4.2.3, and WebLogic 10 are supported.
- As of BPF-4.1.0-004:
- Microsoft Windows Server 2008 R2(x86, 64-bit) and Microsoft Window 7 (x86, 32/64-bit) are supported.
- Microsoft Windows Server 2008 R2 Active Directory Lightweight Directory Services is supported.
- Microsoft SQL Server 2008 is supported.
- WebLogic Server 10.3.0 is supported.
- As of BPF-4.1.0-005:
- Microsoft SQL Server 2008R2 are supported.
- Oracle WebLogic Server 10.3.3 and JBoss 4.3EAP are supported.
- Oracle 11g R2 is supported.
- As of BPF-4.1.0-006, Oracle Directory Server Enterprise Edition 11g (formally Sun Java Directory Server 7.x) is supported.
NOTE For information about FileNet P8 Platform certification support, refer to FileNet P8 Hardware and Software Requirements, FileNet P8 Release Notes, and the fix pack readme documentation.
Installing the fix pack
New and changed files
This fix pack includes new and changed files for your BPF Web application. You need to install the files in the installation location and deployment location for your BPF Web application. For information about installing these files, see Installing the new and changed files.
Important: If you use JBoss 4.2.3 and above version, copy serializer.jar, xalan.jar and xercesImpl.jar to the Jboss install folder <JBoss_HOME>/jboss-as/lib/endorsed and remove serializer.jar, xalan.jar, xercesImpl.jar and xml-apis.jar from WEB-INF/lib folder in BPF deployment location and BPF installation location.
BPF web application folder | File name | New as of ... |
---|---|---|
root | About.jsp | |
Bp8AttachIFrameEntry.jsp | ||
Bp8Dialog.jsp | ||
Bp8Editor.jsp | ||
Bp8SSOSignout.jsp | -001 | |
Bp8ViewerDocs.jsp | ||
Bp8ViewerFrameset.jsp | ||
Bp8ViewerModule.jsp | ||
Bp8WPDefaultAnswer.jsp | ||
Lookup.jsp | ||
SaveLayoutPopUp.jsp | ||
UserPreferences.jsp | ||
UserPrefs.jsp | ||
\css | Bp8Styles.css | |
\dtd | case.dtd | |
\img\mime | Bmp16.gif | |
Bmp32.gif | ||
Default16.gif | ||
Default32.gif | ||
Doc16.gif | ||
Doc32.gif | ||
Gif16.gif | ||
Gif32.gif | ||
Htm16.gif | ||
Htm32.gif | ||
Jpg16.gif | ||
Jpg32.gif | ||
Modca16.gif | -003 | |
Msg16.gif | ||
Oft16.gif | ||
Pdf16.gif | ||
Pdf32.gif | ||
Pep32.gif | ||
Ppt16.gif | ||
Ppt32.gif | ||
Tif16.gif | ||
Tif32.gif | ||
Txt16.gif | ||
Txt32.gif | ||
Una16.gif | ||
Una32.gif | ||
Vcf16.gif | ||
Vcs16.gif | ||
Xls16.gif | ||
Xls32.gif | ||
Xml16.gif | ||
Xml32.gif | ||
\inc | InitUserPreferences.inc | |
\js | Bp8BusinessObjects.js | |
Bp8CaseOperation.js | ||
Bp8ContextMenu.js | ||
Bp8Errors.js | ||
Bp8InitMain.js | ||
Bp8Util.js | ||
CreateCase.js | ||
RemoteFunctions.js | ||
RemoteScripting.js | ||
FormUtil.js | ||
\js\layout | assignRoles.js | |
BPFLayoutInitMain.js | ||
\plugins\custom | EventHandlers.js.template | |
\plugins\tabs\attachment | Bp8AttachmentsTab.jsp | |
\plugins\tabs\attachment\ui | Bp8AttachmentsTab.jsp | |
\plugins\tabs\attachment\xsl\include | Bp8FavoriteAttachDocsIcons.xsl | |
Bp8GetItemLinkURL.xsl | ||
ListViewContextMenu.xsl | ||
Bp8GetFormattedValue.xsl | ||
\plugins\tabs\attachment\xsl\list | Bp8AttachTabSelectableListView.xsl | |
\plugins\tabs\eForms | Bp8DocumentForm.jsp |
-005 |
SaveEFormDataMessage.jsp | -005 | |
\plugins\tabs\table | TableTab.jsp | |
grid.htc | ||
\plugins\tabs\table\xsl | list.xsl | |
\plugins\tools\add_document\ui | Bp8AddDocument.jsp | |
\plugins\tools\create_browse | CreateCase.jsp | |
\plugins\tools\create_case | Bp8CreateCase.jsp | |
\plugins\tools\reactivate_case | Bp8ReactivateCase.jsp | |
\UI-INF\jsp\modules\apps | Bp8MainModuleJSP.jsp | |
Bp8SignInModuleJSP.jsp | ||
\UI-INF\jsp\ui | Bp8AttachIFrameEntry.jsp | |
Bp8Main.jsp |
||
Bp8RemoteCallSingIn.jsp | ||
Bp8SignIn.jsp |
||
Bp8ViewerDocs.jsp | ||
\vbs | Bp8Util.vbs | |
\WEB-INF | Bp8Actions.xml | |
Bp8CaseQueryLayout.xml | ||
Bp8CaseQueryLayout_TwoLines.xml | -001 | |
Bp8ExtCommands.xml | ||
Bp8ExtTasks.xml | ||
Bp8Layout.xml | ||
user-preferences.xml | ||
\WEB-INF\lib |
bpfCM.jar | |
bpfCMResources.jar | ||
bpfCustomLangResources.jar | ||
bpfLangResources.jar | ||
bpfWA.jar | ||
serializer.jar |
||
xalan.jar | ||
xercesImpl.jar | ||
xml-apis.jar | ||
\WEB-INF\xsl\list | Bp8AttachDocsSelectableListView.xsl | |
Bp8CustomSearchSelectableListView.xsl | ||
Bp8FavoriteAttachDocsSelectableListView.xsl | ||
\WEB-INF\xsl\include | Bp8AdoTransform.xsl | |
Bp8AttachmentsPaging.xsl | -003 | |
Bp8AttachmentsSorting.xsl | -003 | |
Bp8CustomSearchIcons.xsl | ||
Bp8FavoriteAttachDocsIcons.xsl | ||
Bp8GetItemLinkURL.xsl | ||
ListViewContextMenu.xsl | ||
\xsl | Bp8CaseProps.xsl | |
Bp8Cases.xsl | ||
Bp8Filters.xsl | ||
Bp8MergeCase.xsl | ||
Bp8ReclassifyCase.xsl | ||
Bp8SplitCase.xsl | ||
Bp8Tool.xsl |
Installing the fix pack
To install the fix pack, complete the following tasks
- Install new and changed files.
- Install the updated BPF Explorer.
- Update the BPF Web application configuration.
- Apply eForms changes.
- Update the BPF operations.
- Validate the BPF Web application.
- Install inventory marker files.
Installing the new and changed files
To install the new and changed files:
- Replace the following JAR files for the Content Engine, Process Engine, Application Engine,
and eForms components:
Component JAR Files Content Engine Jace.jar
javaapi.jarProcess Engine pe.jar
peResources.jarApplication Engine aeeforms.jar
listener.jar
mailapi.jar
p8ciops.jar (renamed as ContentExtendedOps.jar in P8 4.5.x)
p8toolkit.jar
soap.jar
p8webappLogging.jar
commons-fileupload-1.*.jareForms eforms-resources.jar
eforms.jar
itext-1.5.2.jar
jai_codec.jar
commons-httpclient-2.0.2.jar
You can find the new versions of these files in the Workplace WEB-INF\lib folder. By default the Workplace WEB-INF\lib folder is in the following location:
- Windows: C:\Program Files\FileNet\AE\Workplace
- UNIX: /opt/FileNet/AE/Workplace
- Copy one of the following files to the bpfops/lib folder in the BPF installation location:
- p8ciops.jar from the Workplace WEB-INF/lib folder
- ContentExtendedOps.jar from the C:\Program Files\FileNet\AE\router\lib folder on Windows or the /opt/FileNet/AE/router/lib folder on UNIX
- Copy all other JAR files from Workplace WEB-INF/lib folder to the WEB-INF/lib folder in the BPF installation location.
- Windows: C:\Program Files\FileNet\BPF
- UNIX: /opt/FileNet/BPF
Important: You will also need to copy these JAR files to your BPF Web application deployment location as described in step 7. - Download the fix pack and extract the files to a temporary folder on your local system.
- Copy the files to the appropriate folders in the BPF installation location. For a list of these files and the folders in which they belong, see New and changed BPF Web application files.
- Stop the application server on which your BPF Web application is running.
- Use the Export Manifest option in BPF Explorer to back up
the BPF Metastore configuration information. To access the Export Manifest
option:
- Right-click Export and Import Management and select All tasks > Add All Objects to Export List.
- Right-click Export and Import Management again and select All tasks > Export XML Manifest.
- Back up all files in the BPF Web application deploy location.
Typically, the deploy location is different from the BPF install home
directory.
If your application is deployed as a WAR or EAR file, back up the WAR or EAR file. - Update the BPF Web application files in deploy location with the new and changed
files from the fix pack.
Folder structure
- Replace the files in the folder structure with the changed BPF Web application files, and add the new files from the fix pack to the appropriate folders. For a list of the files and the folders in which they belong, see New and changed BPF Web application files.
- Copy any JAR files you replaced in step 1 to the /WEB-INF/lib folder in the deployment folder structure.
- Copy the WAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_war.
- Open a command window.
- Navigate to C:\temp_war and then run the following
command to
extract the WAR file contents:
jar -xvf bpf_app.war
- Delete the WAR file from the C:\temp_war folder.
- Replace the files in the C:\temp_war folder structure with the changed files,
and add the new files from the fix pack to the appropriate folders. For
a list of the files and the folders in which they belong, see New and changed BPF Web application files.
- Copy any JAR files you replaced in step 1 to the C:\temp_war\WEB-INF\lib folder.
- Copy the EAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_ear.
- Open a command window.
- Navigate to the C:\temp_ear folder and then run the following command to extract
the WAR file and META-INF folder contents to the C:\temp_ear folder:
jar -xvf bpf_app.ear
- Delete the EAR file from the C:\temp_ear folder.
- Copy the WAR file from the C:\temp_ear folder to another temporary folder. In this procedure, the second temporary folder is assumed to be C:\temp_war.
- Navigate to C:\temp_war and then run the following command to
extract the WAR file contents:
jar -xvf bpf_app.war
- Delete the WAR file from the C:\temp_war folder.
- Replace the files in the C:\temp_war folder structure with the changed files, and add the new files from the fix pack to the appropriate folders. For a list of the files and the folders in which they belong, see New and changed BPF Web application files.
- Copy any JAR files you replaced in step 1 to the corresponding folders in the C:\temp_war\WEB-INF\lib folder.
- If you have the issue addressed by APAR PJ37750, and if
you are upgrading from BPF-4.1 GA, BPF-4.1.0-001, BPF-4.1.0-002, BPF-4.1.0-003 or BPF-4.1.0-004: when
eForms form data is created in one time zone and later displayed in a
different time zone, the date that is displayed is incorrect. This problem can occur:
- The server on which BPF is running is in a different time zone from the clients accessing BPF.
- The clients are scattered in a wide range of time zones.
- Ensure that you've applied the AE test fix 4.0.2.6-P8AE-TF002(or later patch) to Workplace (set eFormsMapDateToGMTNoon=true) and copy the aeeforms.jar file to the BPF Web application.
- Add the following property to the bootstrap.properties file
under the BPF configuration folder:
eFormsMapDateToGMTNoon=true
By default, the BPF configuration folder is in the following location:
- Windows: C:\Program Files\FileNet\Config\bpf
- UNIX: /opt/FileNet/Config/bpf
- Update the web.xml file for your BPF Web application.
If your application is deployed to a Folder structure, update the web.xml file in the <bpf-app>\WEB-INF folder.
If your application is deployed as an EAR or WAR file, update the web.xml file you extracted to a temporary folder in step 7.- If upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, add the following elements after the last
<servlet-mapping> element and before the
<welcome-file-list> element:
<servlet-mapping> <!-- mime-mappings below --> <mime-mapping> <extension>doc</extension> <mime-type>application/msword</mime-type> </mime-mapping> <mime-mapping> <extension>docx</extension> <mime-type>application/msword</mime-type> </mime-mapping> <mime-mapping> <extension>xls</extension> <mime-type>application/vnd.ms-excel</mime-type> </mime-mapping> <mime-mapping> <extension>xlsx</extension> <mime-type>application/vnd.ms-excel</mime-type> </mime-mapping> <mime-mapping> <extension>xlsb</extension> <mime-type>application/vnd.ms-excel</mime-type> </mime-mapping> <mime-mapping> <extension>xlsm</extension> <mime-type>application/vnd.ms-excel</mime-type> </mime-mapping> <mime-mapping> <extension>ppt</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> </mime-mapping> <mime-mapping> <extension>pptx</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> </mime-mapping> <mime-mapping> <extension>ppsx</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> </mime-mapping> <mime-mapping> <extension>svg</extension> <mime-type>image/svg+xml</mime-type> </mime-mapping> <mime-mapping> <extension>xfdl</extension> <mime-type>application/vnd.xfdl</mime-type> </mime-mapping> <mime-mapping> <extension>xfdd</extension> <mime-type>application/vnd.xfdl.design</mime-type> </mime-mapping> </servlet-mapping>
- If AE 4.0.2.7 or higher version is used, add the following setting after
the last <context-param> element and (1) before the first
<servlet> element if SSO is not configured OR (2) before
the <filter> section if SSO is configured:
<!-- secureAuthenticationParameters: Remove sensitive authentication parameters from the sign-in page. The value is numeric (and not true/false) so that the functionality can be expanded to address more parameters in the future. Here are the current supported values: 0 = Don't secure anything (default). 1 = Remove the sessionId parameter. Numbers deemed invalid will result in default "0" behavior. --> <context-param> <param-name>secureAuthenticationParameters</param-name> <param-value>1</param-value> </context-param>
NOTES
- This setting was new in BPF 4.1.0-004. Before BPF 4.1.0-004, BPF contained a sessionId parameter in a URL. Beginning in BPF 4.1.0-004, this setting is provided to allow you to EITHER keep sessionId parameter in the URL by setting its value to 0 OR remove this parameter from the URL by setting its value to 1. This setting should be set to 1 by default.
- This setting will only take effect when AE 4.0.2.7 or higher version is applied. If the AE version is lower than 4.0.2.7, you do not need to add this setting to BPF web.xml, because this setting will be ignored by BPF if it is added to web.xml. You can refer to APAR PJ37346 fixed in AE 4.0.2.7 for more information.
- If you are upgrading from BPF-4.1 GA or BPF-4.1.0-001 and your BPF Web
application needs to support clients with double-byte character sets,
add the following code after the <context-param> sections:
<filter> <filter-name>encoding</filter-name> <description>utf-8 filter</description> <filter-class>com.filenet.bp8.apps.server.filter.EncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> </filter> <filter-mapping> <filter-name>encoding</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
- If upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, add the following elements after the last
<servlet-mapping> element and before the
<welcome-file-list> element:
- If you have more tools than can fit into the Toolbar area in the BPF Web application, perform the following steps to prevent the tools from overlapping the Case area:
CASEQUERY inbasket
Back up the Bp8CaseQueryLayout.xml file and then rename the Bp8CaseQueryLayout_TwoLines.xml file as Bp8CaseQueryLayout.xml. These files are in the <bpf-app>\WEB-INF\ folder.
Standard inbasket
After you install the fix pack, use Layout Designer to increase the vertical space for the top Toolbar area in the layout that you are using. - WAR or EAR file deployment: Repackage the updated file structure into a new WAR or EAR file:
WAR file
- Repackage the WAR file with the updated files in the
C:\temp_war folder by executing the following command:
jar -cvf bpf_app.war *
- Copy the WAR file to the BPF Web application deployment location.
- Repackage the WAR file with the updated files in the
C:\temp_war folder by executing the following command:
- Repackage the WAR file with the updated files in the
C:\temp_war folder by executing the following command:
jar -cvf bpf_app.war *
- Copy the WAR file generated in the previous step from the C:\temp_war folder to the C:\temp_ear folder.
- Repackage the EAR file by executing the following
command:
jar -cvf bpf_app.ear *
- Copy the EAR file to the BPF Web application deployment location
- JBoss and WebSphere only: Delete all the cache folders for the BPF Web application.
The default location of the cache folders for the BPF Web application is
- JBoss: <JBoss_HOME>\server\default\work\jboss.web\localhost\<bpf-app>
- WebSphere 5.x: <WAS_Home>\AppServer\temp\<Node_Name>\servers\server1\bpf
- WebSphere 6.x and 7.x: <WAS_Home>\AppServer\profiles\default\temp\<Node_Name>\server1\bpf
- JBoss and WebSphere only: Restart the application server on which BPF Web application is running.
- WebLogic only: Redeploy the BPF Web application.
WAR file
EAR file
EAR File
Install the updated BPF Explorer
- Run the filenet_bpf_explorer_setup.exe program in the 4.1.0.6-P8BPF-FP006 fix pack to uninstall BPF Explorer.
- Run the filenet_bpf_explorer_setup.exe program in the 4.1.0.6-P8BPF-FP006 fix pack again to install the updated BPF Explorer. For information about the setup program, see "BPF Explorer installation" in the IBM FileNet Business Process Framework Installation and Upgrade Guide.
Update your BPF Web application configuration
- Upgrade the BPF Metastore schema.
TIP Before you upgrade the schema, review the following topics in the Business Process Framework Installation Guide:- "Database Security Considerations" in the "Installation Planning Considerations" section, to determine if you need to edit the database scripts that are used to update the Metastore schema.
- "Load BPF Metastore" in the "Install and Configure BPF Explorer and Metastore" section, for information on running the database scripts.
In prior releases before BPF-4.1.0-002, you could delete a company object (BUSINESS_UNIT_ID) even if user objects (USER_UNITS) still referenced that company. the 4.1.0.6-P8BPF-FP006 fix pack includes a fix to prevent you from deleting a company object that is referenced by a user object. As part of this fix, the Step3 script that you run to upgrade the Metastore schema removes references to any deleted companies from user objects. If you haven't done this before, you must manually reassign companies to these users after you apply the fix pack.
- Run the following SQL query against the BPF Metastore to obtain a list of
the users for whom the Step3 script will delete the company assignment:
select * from USER_UNITS where BUSINESS_UNIT_ID not in (select BUSINESS_UNIT_ID from BUSINESS_DATA)
- Edit the 4.1.0.6-P8BPF-FP006 Step3 script to match your
environment as needed:
- If your BPF Metastore is on DB2, edit the
Step3.DB2.Bp8.Metabase.1.0.sql script.
Important: You must replace all<BPF_SCHEMA>
,<BPF_PROC_SCHEMA>
and<BPF_FUNC_SCHEMA>
with the real schemas of tables and views, stored procedures and functions of your BPF Metadatabase respectively.
- If your BPF Metastore is on Microsoft SQL Server, edit the Step3.mssql.Bp8.Metabase.1.0.sql script. If the collation name of BPF Metastore database is set to SQL_Latin1_General_CP1_CI_AI, search "SQL_Latin1_General_CP1_CI_AS" in the Step3.mssql.Bp8.Metabase.1.0.sql script and replace it with "SQL_Latin1_General_CP1_CI_AI".
- If your BPF Metastore is on Oracle, edit the
Step3.oracle.Bp8.Metabase.1.0.sql script.
Important: If you run this script using SQL*Plus Worksheet, you must search and replace all&&BPF_SCHEMA
with the real schema of your BPF Metadatabase. Otherwise, if using SQL*Plus, you need to enter the real schema when it prompts "Enter value for bpf_schema:".
- If your BPF Metastore is on DB2, edit the
Step3.DB2.Bp8.Metabase.1.0.sql script.
- Run the Step3 script. For information on running this script, refer to "Loading the BPF Metastore" in the IBM FileNet Business Process Framework Installation and Upgrade Guide.
If you run the script on Oracle, the following error might occur:
ORA-01460: unimplemented or unreasonable conversion requested ORA-06512: at "BP8.UPDATE_SETTINGS", line 16
If you receive this error, replace the following line in the 4.1.0.6-P8BPF-FP006 Step3.oracle.Bp8.Metabase.1.0.sql script:
CALL UPDATE_SETTINGS (N'WEB', N'DIALOG_WINDOW_RESIZABLE',N'False',N'Whether Action Dialog Window can be resizable (Default:False)');
with the following line:
CALL UPDATE_SETTINGS (N'WEB', 'DIALOG_WINDOW_RESIZABLE',N'False',N'Whether Action Dialog Window can be resizable (Default:False)');
Rerun the script. - If your BPF Metastore is on DB2, run the 4.1.0.6-P8BPF-FP006 Recreate.DB2.Bp8.Metabase.Triggers.sql file to fix logic problems in the BPF triggers (refer to APAR PJ37412):
- Open the DB2 Command Editor and log on using the BPF Metastore user.
- Change the Statement Termination Character to @. You can change this character at the bottom of the Command Editor window.
- Click the Add button and select the Bp8Metastore database to be corrected.
- Clear the "User implicit credential," enter the username and password for the DB2 user who is the schema owner of your Bp8Metastore, and click OK.
- Open the Recreate.DB2.Bp8.Metabase.Triggers.sql file in the Command Editor using Selected > Open
- Run the script using Selected > Execute
- Log into BPF Explorer.
- If upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, update the Adhoc search definition options:
- In the console tree, expand the Application Settings node and click Web Application.
- Right-click Attachments tab - Adhoc search definition, click
Properties, and add the following text after the select keyword:
a.Bp8ObjectClass as ObjectClassID,
The value is case sensitive, so enter the new text exactly as shown. - Right-click Viewer documents list - Adhoc search definition, click Properties, and
add the following text after the select keyword:
a.Bp8ObjectClass as ObjectClassID,
The value is case sensitive, so enter the new text exactly as shown.
- If you are upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, and
you customized the Attachment Panel Document List SQL statements for
any inbaskets, perform the following steps for each of these inbaskets:
- In the console tree, expand the Inbasket Configurations node.
- Right-click the inbasket that you want to update and click Properties.
- Click the General tab.
- In the Attachment Panel Document List SQL field add the
following text after the select keyword:
a.Bp8ObjectClass as ObjectClassID,
The value is case sensitive, so enter the new text exactly as shown.
- If you are upgrading from BPF-4.1 GA or BPF-4.1.0-001 and you are using the sample Case Management application, change the inbasket type for the Indexer role:
- In the console tree, expand Inbasket Configuration node.
- Right-click the Matching Inbasket of the Indexer role and click Properties.
- Click the General tab.
- From the Inbasket type list, select STANDARD.
Apply eForms changes
If you upgrade eForms to eForms V4.0.2.3 or higher, you must synchronize the eForms JavaScript that is used by Business Process Framework. For information on synchronizing the eForms JavaScript, refer to the Manual_Instruction_Sync_eForms_Script.htm file that is included in this fix pack.
Update the BPF Operations
- Stop Component Manager by using Process Task Manager on the Application Engine.
- Back up the bp8ciops.jar file. By default, this file is in the following folder:
- Windows: C:\Program Files\FileNet\BPF\bpfops
- UNIX: /opt/FileNet/BPF/bpfops
- Extract the bp8_config.xml and log4j.xml files from the bp8ciops.jar file.
- If you use Oracle for your Bp8Metastore database, edit the bp8_config.xml file to use the Oracle database service name instead of the Oracle database SID.
- Optional: Encrypt the password of BPF Metastore database that is configured in the bp8_config.xml file
at the node of <Bp8Operations>/<JDBC>/<Password>:
- Launch the Command Prompt (Windows 2000/XP/2003/7/2008) or shell console (Linux or UNIX platform on AIX, Solaris, and HP-UX), and then change the current directory to the folder that contains the bp8ciops.jar that are delivered with the fix pack.
- Ensure that your PATH environment variable is set to provide access to the java command.
- Run the following command to generate the encrypted password:
java -jar bp8ciops.jar
Input and verify the following passwords when you are prompted:
- the password of the user that is configured to start BPF_Operations in Component Manager
- the password of the BPF Metastore database user .
Then the encrypted password will be displayed in Command Prompt/shell console, in the formatencrypted{xxxxxxxxx}
. - Copy the encrypted password, including the prefix
encrypted{
and suffix}
, and paste it into the extracted bp8_config.xml file to replace the password in plaintext.
NOTE Due to a limitation of Java versions prior to 6, two minor problems can occur when you run this tool:
- The character you input blinks, displaying and disappearing quickly.
- When you input the password for the second time, you are prompted to enter the password again.
You can ignore both issues.
- Use WinZip or an equivalent utility to replace the bp8_config.xml and log4j.xml files in the bp8ciops.jar that was delivered with the fix pack with the files you extracted in step 3.
- Replace the bp8ciops.jar that is currently installed on the BPF application server with the file that you updated in step 6.
- If you installed P8PE-4.0.2-001.001 test fix or a later P8PE fix pack,
navigate to the Connection Point that is used in your system and add
the following text in the JRE Parameters field on the Advanced page:
-Dfilenet.pe.cm.adaptor.single.dispatcher.BPF_Operations=true ‑Dfilenet.pe.cm.buffer.size=50 -Dfilenet.pe.eventlog.level=WARNING
- Restart the Component Manager.
- Verify that the BPF operations work correctly.
If you use the sample Case Management application and have created a workflow subscription on the Content Engine Case Management Documents document class, please refer to the "Creating workflow subscription on the Content Engine Case Management Documents document class (optional)"section in the BPF 4.1 Installation Guide). You can ensure that the BPF operations are working correctly as follows:
- In Workplace or FileNet Enterprise Manager, add a new document to the Case Management Documents document class.
- Set the DocEntryStatus and DocType values to 1.
If the BPF operations are working correctly, BPF creates a new case and you can see it in the Index Inbasket.
Important: If you set the encrypted password in step 5, you must repeat steps 1 through 10 to refresh the encrypted password whenever the following passwords are changed:
- The password of the BPF Metastore database user
- The password of the user that is configured to start BPF_Operations in Component Manager
Validate the BPF Web application
Before users access the BPF Web application, validate that the application is working:
- Clear Internet Explorer caches by deleting Temporary Internet Files with all offline content on all BPF clients.
- Launch BPF Web application and validate that the application is working correctly. For information about validating the BPF Web application, see "Logging on to a sample Business Process Framework Web application" in the IBM FileNet Business Process Framework Installation and Upgrade Guide.
Install inventory marker files
Starting with BPF-4.1.0-004, BPF provides two inventory marker files, also called tag files. The first tag file identifies the product name and the version number. In this release the file is named IBM_FileNet_Business_Process_Framework.4.1.0.swtag. The second tag file identifies the fix pack number, if applicable. In this release the file is named BPF.4.1.0.6.fxtag.
- Go to the <BPF_installation_location> directory. By default, the <BPF_installation_location>
is:
- Windows: C:\Program Files\FileNet\BPF
- UNIX: /opt/FileNet/BPF
- Under the <BPF_installation_location> directory, create a directory named properties, if it is not created yet.
- Under the <BPF_installation_location>/properties directory, create a directory named version, if it's not created yet.
- Under the <BPF_installation_location>/properties/version directory, copy the two tag files. These files are included in this fix pack:
IBM_FileNet_Business_Process_Framework.4.1.0.swtag
BPF.4.1.0.6.fxtag
Important: Since BPF uninstaller does not uninstall files that are not laid down by BPF installer, to uninstall these two files, you need manually remove the <BPF_installation_location>/properties directory, including all subdirectories and files, after uninstalling the BPF product using BPF uninstaller.
Removing the fix pack
You cannot uninstall the this fix pack.
Known problems and issues
Refer to the following technotes for information on known problems and their solutions:
- Configuring the Reactivate Case (reactivate_case) tool for Business Process Framework (BPF)
- Errors occur when logging into Business Process Framework (BPF) with FileNet P8 5.0
- Data
sources for a BPF Metastore database and Process Engine database
created by the BPF Installer do not work with WAS 7.x and Microsoft SQL
Server
- The Business Process Framework Lookup results page fails to display, or displays incorrectly, when running on IE 8 on a Windows 7 64-bit client
- Manually importing Business Process Framework (BPF) Metastore Manifest (bpf_cm_oracle.xml), when installing the Case Management sample application with BPF 4.1 GA on Oracle, causes BPF Explorer to hang
- Image attachment of a Case is displayed incorrectly when Business Process Framework (BPF) is deployed on Oracle WebLogic Server 10.3.3
- Importing a big Business Process Framework (BPF) Manifest using BPF Explorer can be very slow when the BPF metastore database is on DB2
- "Failed to load servlet Class" exceptions occur in the stderr log file when starting the Business Process Framework (BPF) web application on Weblogic Server 10.0.2 or later
- Duplicate DEBUG level log messages for Business Process Framework (BPF) Operations (BPF_Operations) are logged in both the bp8operations.log file and the adaptor.log file when DEBUG level logging is enabled for both.
Problems solved
The following section describes all the APARs fixed in IBM Business Process Framework Version 4.1 Fix Pack 6.
To search for detailed information about an APAR, enter the APAR number in the Search field at the top of the page or click on the links below. If a link does not work, the details of the APAR are not available through the product Support Portal.
APAR | Type | Product area | Description |
---|---|---|---|
PJ38693 | Fix | BPF Web application | If a browse field name contains "From", BPF returns the error "Could not get workobject list" when the user clicks Next Page in browse mode. An example of a browse field name that causes this error is NotificationFrom. |
PJ38321 | Fix | BPF Web application | BPF creates duplicate cases when more than one user clicks on the Reactivate tool to reactivate the same case at the same time. |
PJ38241 | Fix | BPF Explorer | The following error can occur when you use the reserved word "order" in the Inbasket Filter: "Oracle error ORA-01756: quoted string not properly terminated". |
PJ38201 | Fix | BPF Web application | Case sorts in browse mode fail if the sort field name contains "desc". |
PJ38126 | Fix | BPF Web application | Table Tab row custom objects are deleted, not saved, when a boolean field is displayed and the user selects Save. |
PJ38102 | Fix | BPF Web application | BPF lookup list does not scroll properly when using the cursor keys. |
PJ38098 | Fix | BPF Web application | Lookup fails on the create_case tool with multiple CaseTypes when the second CaseType has extra fields updated by lookup. |
PJ37476 | Fix | BPF Explorer | The SORT_ORDER PE/WF field in the BPF configuration is not updated when the case field mapped to a browse field is changed in BPF Explorer. |
PJ37412 | Fix | BPF Installation Script | Multiple issues must be corrected in the BPF-4.1.0 Step1.DB2.Bp8.Metabase.1.0.sql SQL script for a metastore install on DB2. |
PJ38465 | Fix | BPF Web application | The Table Tab is writeable/editable only when the LDAP group names are the same as the Access Role names. If they are not the same, the Table Tab is read only. |
PJ38477 | Fix | BPF Operations | The BPF Operations CreateCase operation reports an error in the Content Engine logs if the attached document does not have a Bp8CaseId property. |
APAR | Type | Product area | Description |
---|---|---|---|
PJ37985 | Fix | BPF Web application | Slowness when accessing attachments tab and document list at the bottom of the Case screen. |
PJ37921 | Fix | BPF Web application | Attempting to create a TableTab object for a Case on one object store can result in an error relating to another object store. |
PJ37916 | Fix | BPF Web application | An E_OBJECT_NOT_FOUND error can occur in BPF logs when saving or submitting an eForms Case if the eForms Tab page is cached incorrectly. |
PJ37873 | Fix | BPF Web application | The attachment viewer can intermittently display the incorrect attachment.
To fix APAR PJ37873, the Apache Xalan-Java, v2.7.0 and Apache Xerces2 Java Parser, v2.7.1 listed under "Excluded Components" in the License Information for Program IBM FileNet Business Process Framework v3.6, v4.0, and v4.1 are replaced by Apache Xalan-Java, v2.7.1 and Apache Xerces-Java 2 XML Parser 2.9.0, which are excluded components for this fix pack. |
PJ37789 | Fix | BPF Web application | You cannot open a Case with apostrophe(') characters in any input field if using a picklist which includes the apostrophe(') characters in the code. |
PJ37788 | Fix | BPF Web application | When no columns are configured for display in BPF Explorer, the Attachments Tab can fail to display . |
PJ37774 | Fix | BPF Web application | CE_Operations::setDateProperty does not update the latest form data after the BPF 410-1022 patch is applied. |
PJ37766 | Fix | BPF Web application | If you attempt to save or submit an eForms Case and you make changes on the eForms Tab and switch to another Tab without saving, an E_OBJECT_NOT_FOUND error will be logged. |
PJ37765 | Fix | BPF Web application | The Workplace Integration Menu can display intermittently in other languages . |
PJ37751 | Fix | BPF Operations | The user should be prompted to input the BPF_Operations user password without echoing the characters the user types. |
PJ37750 | Fix | BPF Web application | The date field value of an eForms Case is changed after the time zone is modified on a client machine. |
PJ37741 | Fix | BPF Web application | When you open an eForms Case, an error can occur stating that the form template is running in read-only status, and that you can not continue processing in this eForms Case. |
PJ37716 | Fix | BPF Web application | If you apply a time zone offset from GMT more than once in the compiled Java code on the Attachment Tab, the value displays incorrectly. |
PJ37644 | Fix | BPF Web application | The ReactivateCase tool can generate NullPointerException error. |
PJ37642 | Fix | BPF Web application | A runtime exception occurs when you try to save a completed Case from the CaseQuery Inbasket if the Bp8Case object is not in the BPF default object store. |
PJ38170 | Fix | BPF Database Script | The ATTR_* fields are not copied from the template user to the actual users created for the role of this template user. |
PJ38208 | Fix | BPF Web application | An
error message of "Changes made to Case will be lost. Press OK or
Cancel" pops up when you close the saved Case with updated lookup
fields. |
APAR | Type | Product area | Description |
---|---|---|---|
PJ37265 | Fix | BPF Translation | Some critical strings in BPF 4.1.0-003 are not translated correctly into Finnish. |
PJ37119 | Fix | BPF Web application | Out of memory(OOM) when populating
200 000 case to BPF. |
PJ37224 | Fix | BPF Operations |
Bp8AuditLogItem not deleted when BPF_Operations::attachDoc fails and is rolled back due to locked work item error. |
PJ37225 | Fix | BPF Operations | BPF_Operations::attachDoc errors when it encounters a 'Lock work object failed: Work object already locked' error instead of returning 0. |
PJ37182 | Fix | BPF Web application | Incorrect handling of nested groups leads to long login time with direct LDAP integration. |
PJ37182 | Fix | BPF Web application | Circular group membership causes BPF to hang (loop over processGroups) when a user logs in (using direct LDAP integration). |
PJ36642 | Fix | BPF Web application | Case Operation: VWAttachments are not forwarded. |
PJ36935 | Fix | BPF Web application | InbasketsCombo fails to display within custom layout. |
PJ36936 | Fix | BPF Web application | Add multi-value field to eform but not associate to equivalent BPFfield causes issue. |
PJ36965 | Fix | BPF Web application | After upgrade P8 eForm to 4.0.1-005 save and close button appear in eForm tab in BPF. |
PJ37065 | Fix | BPF Web application | BPF field not updated from eform field if only one field is modified and the cursor remains in the field. |
PJ37168 | Fix | BPF Database Script |
Database user IDs are hardcoded in the BPF4.1.0-002 patch SQL script files. |
PJ37174 | Fix | BPF Web application | Error "Unsupported Call" completing a column field in a table on an eForm. |
PJ37330 | Fix | BPF Web application | Receives error "Invalid Parameter" when trying to access Bp8Attachment value for case created using split case tool. |
PJ37386 | Fix | BPF Web application | Get Error 500 while try to view the document from BPF case when users do not have permission to the Major Version 1 of the document. |
PJ37583 | Fix | BPF Web application | "Object Required"
error occurred
when clicking X button to close web application in IE8. |
PJ37584 | Fix | BPF Web application | Problem occurred when selecting item in drop-down list using IE8. |
PJ37780 | Fix | BPF Web application | Unable to remove case attachment from Attachments Tab or Panel on BPF-4.1.0-1022+ when attachment versioning is disabled. |
APAR | Type | Product area | Description |
---|---|---|---|
None | Enhancement | BPF Web application |
Provides support for the case-insensitive views feature that was introduced in Process Engine 4.0.3. The Oracle and DB2 database views generated by default by the Process Engine cannot be used by BPF. Instead, the view names must be manually updated each time a new queue is defined, a queue definition is updated, or a workflow is transferred. The procedure for updating the view names is described in the BPF Installation Guide. As of Process Engine 4.0.3, the Process Engine can be configured to generate an additional set of case insensitive views. To generate a case-insensitive set of views, use the
Process
Engine administrative tool vwtool with the createDBviewsCI
command. Information about this command is provided in the P8
documentation under System Administration > Process
Administration
> Administrative Tools > vwtool > commands
>
createDBviewsCI. Once the case-insensitive views have been generated,
use the Configuration > Queues option in BPF Explorer to update
the
object name of each Workflow queue to match the name generated by
vwtool. |
PJ36796 | Fix |
BPF Web application |
Additional security profiles are listed for some users when the users log in to the BPF Web application. |
PJ36315 | Fix |
BPF Web application |
BPF does not update the value of the Bp8CaseID property in documents that are attached to BPF cases. |
PJ35374 | Fix |
BPF Explorer |
An exception occurs when users attempt to start the Case Tab Designer tool. |
PJ36291 | Fix |
BPF Web application |
After a user upgrades from BPF 3.6 to BPF 4.1, an exception occurs when users open cases that are associated with workflows that do not expose the Bp8CaseType field on the inbasket steps. |
PJ36152 | Fix |
BPF Operations |
BPF does not update the bp8case_bp8attachment property in a case if the user creates a case by adding a document of the Case Management type in the workflow subscription. |
PJ35339 | Enhancement |
BPF Web application |
Users can now configure the display format of individual case fields of type DATE. A user can use BPF Explorer to configure a DATE case field to display the date, the time, or both the date and time. |
PJ35284 | Fix |
BPF Web application |
The Add Document incorrectly displays the case type ID in the Case Type field. This field should display the name of the case type. |
PJ35761 | Fix |
BPF Web application |
If the BPF Web application is configured to use multiple object stores, an exception occurs when users attempt to open documents in the Document Viewer. |
PJ35945 | Fix |
BPF Web application |
BPF incorrectly saves and displays the values of DATE case fields for dates entered during daylight savings time (DST). |
PJ36641 | Fix |
BPF Web application |
An error 403 occurs if a user submits an eForms case more than once. |
PJ36797 | Fix |
BPF Web application |
The Create Case tool incorrectly starts the workflow before creating the Bp8Attachment objects that are associated with the new case. |
PJ36798 | Fix |
BPF Web application |
The lookup feature does not handle Unicode characters correctly. As a result, a search containing a Unicode character returns "no match found." |
PJ35946 | Fix |
BPF Web application |
If the BPF Web application is configured to use multiple object stores, a Content Engine security error occurs if a user attempts to add a document, but does not have access rights to all the domain object stores. |
PJ36036 | Fix |
BPF Web application |
The following problems can occur in the BPF integration
servlet when the 9010 command is used:
|
PJ35608 | Fix |
BPF Operations |
The BPF updateCase operation always attempts to update mapped attachment fields. If the attachment field does not exist, the updateCase operation returns an error and rolls back the entire update. |
PJ36799 | Fix |
BPF Web application |
If a user attempts to save a case without completing the required fields, BPF prompts the user to complete the fields. However, the order in which the prompts are given does not match the order in which the fields are displayed. |
PJ36199 | Fix |
BPF Operations |
If users are creating cases while the Content Engine server is experiencing problems, BPF can create cases with duplicate case IDs. |
PJ36472 | Fix | BPF Web application | If users enable the case count feature, DB2 experiences deadlocks when running heavy loads. |
APAR | Type | Product area | Description |
---|---|---|---|
PJ35189 | Fix | BPF Web application | If the Bp8CaseType in the Case Management Sample workflow is changed from Integer to String, a java.lang.ClassCastException: java.lang.String error occurs when a user opens an existing case. |
PJ35525 | Fix | BPF Web application | A validation error occurs when the user attempts to enter a time in a date/time field. |
PJ35526 | Fix | BPF Web application |
Users are not warned that cases are not locked if the cases are opened from a CASEQUERY (9000) inbasket that contains no editable fields. |
PJ35527 | Enhancement | BPF Web application BPF Explorer |
Added application settings in BPF Explorer to control the size and behavior of the Reasons dialog in the BPF Web application. |
PJ35528 | Fix | BPF Web application |
If the Application Engine is in a different HTTP domain than the BPF Web application, users receive a "Permission Denied" error when they open or close eForms form data attachments. |
PJ35529 | Fix | BPF Web application | If a user saves or performs an action on a case, the following error occurs: Unable to convert that value to a boolean. |
PJ35532 | Fix | BPF Web application | The Close button does not close the Attachment List window if a user opened the window by clicking the Attachment icon on the Attachments tab. |
PJ35533 | Fix | BPF Web application | If the BPF Metastore is in MS SQL 2005, the Case tabs order in the BPF Web application is not consistent with the order configured for the tabs in BPF Explorer. |
PJ35466 | Fix | BPF Web application BPF Explorer |
If the BPF Metastore is in MS SQL 2005, the inbasket filter order in the BPF Web application is not consistent with the order configured for the filter in BPF Explorer. |
PJ35467 | Fix | BPF Web application | If the cache is set to 1 (_cache=1) for the Table tab, data is not displayed when a user clicks the Table tab a second time. |
PJ35468 | Fix | BPF Explorer | A user can delete a company in BPF Explorer even though that company has been assigned to a user. |
PJ35469 | Enhancement | BPF Web application | Added multilingual resources to the BPF Web application. |
PJ35470 | Fix | BPF Operations | The BPF_Operations::logEventWithCaseType method stores the Content Engine Bp8AuditLogItem object in the default Content Engine object store if the Bp8CaseType is an invalid value and does not notify the user. |
PJ35471 | Fix | BPF Explorer | The layout in the property panel of BPF Explorer and the cells for the Case fields tab data are incorrect in Japanese. |
PJ35472 | Fix | BPF Explorer | If the user does not select Browse mode in the New Tool wizard, BPF saves tools with a NULL value instead of 0 for the BROWSE_MODE. |
PJ35473 | Enhancement | BPF Web application | The option to hide inbaskets and filters when a user opens a case has been restored. |
PJ35474 | Fix | BPF Explorer | BPF Explorer import fails with error 457 if there are duplicate settings in the XML file. |
PJ34790 | Fix | BPF Web application | A new user whose username contains uppercase letters cannot sign onto the BPF Web application if the BPF Metastore is on DB2. The user is told that no Role is assigned. |
PJ35475 |
Fix | BPF Web application | When a user moves the cursor to a submenu of the Create Case menu, the submenu disappears immediately. |
PJ35476 | Fix | BPF Web application |
When new LDAP users log on to the BPF Web application, multiple instances of an integrity constraint error are entered in the Bp8.log file. |
PJ35477 | Fix | BPF Web application | The default labels in the BPF Web application and the key values in the strings.en.txt file are not consistent. |
PJ35478 | Enhancement | BPF Web application | Added the Workplace command 3010 ShowProperties to the Attachment context menu in the BPF Web application. |
PJ35479 | Enhancement | BPF Web application | The BPF build number, build day and Copyright information are now updated automatically. |
PJ35480 | Fix | BPF Web application | The width for text area fields is not set as configured. |
PJ35481 | Fix | BPF Operations | If an invalid roster name is passed to the BPF_Operations::detachFolderWithRoster method, BPF detaches a folder instead of returning an error. |
PJ35482 | Fix | BPF Web application | There are no scrollbars on the Case tab attachments panel, so BPF cannot display all attachments if the document titles are too long. |
PJ35493 | Fix | BPF Web application | After a BPF session expires in a TAM/Kerberos SSO environment, a blank page is displayed when the user clicks an attachment. |
PJ35494 | Fix | BPF Web application | After a BPF session expires in a TAM/Kerberos SSO environment, some BPF actions cause a NULL exception. |
PJ35495 | Fix | BPF Web application |
After a BPF session expires in a TAM/Kerberos environment, when a user selects the Open Documents action from a case with attached documents, BPF displays a message stating that there are no documents. |
PJ35523 | Fix | BPF Web application | A java.lang.NumberFormatException occurs during user email notification if the Enable Open Case event is enabled for the inbasket. |
PJ35524 | Fix | BPF Web application |
BPF displays an error message when a Merge Case or Split Case operation completes successfully. |
PJ35483 | Fix | BPF Documentation | An error occurs when a user uses the WFImport.exe application to import a PEP file to a BPF Metastore on DB2 and the wfdef4.dtd is not in the same location as the PEP file. |
PJ35484 | Fix | BPF Documentation |
An error occurs when a user attempts to log on to Content Engine from the Application Data Properties window in BPF Explorer. |
PJ35485 | Fix | BPF Documentation | The Close and Save buttons on eForms attachments do not work. |
PJ35486 | Enhancement | BPF Documentation | Added information about the impact of various SQL syntax options for Inbasket Filter Templates in the IBM FileNet Business Process Framework Explorer Handbook. |
PJ35487 | Fix | BPF Documentation | The requirements for using shared BPF 4.0.0 and 4.1.0 instances is not documented. |
PJ35488 | Enhancement | BPF Documentation | Added information about WebSphere requirements for BPF to the IBM FileNet P8 Hardware and Software Requirements. |
PJ35489 | Fix | BPF Documentation | An error occurs during installation of the BPF Metastore installation on DB2 9.5. |
PJ35490 | Fix | BPF Documentation | Corrected the description of the Disable updating attachment properties option in the IBM FileNet Business Process Framework Explorer Handbook. |
PJ35492 | Enhancement | BPF Documentation | Added instructions in the "Customizing the BPF Toolbar" topic for using the Security-profile node in Toolbar.xsd. |
PJ35491 | Enhancement | BPF Documentation | Added thread tuning recommendations for BPF Operations in the IBM FileNet Business Process Framework Performance Tuning Guide. |
APAR | Type | Product area | Description |
---|---|---|---|
PJ34519 | Fix | BPF Web application | The wrong attachment is displayed when opening an item from the attachment panel. |
PJ34520 | Fix | BPF Web application | When a user clicks a custom tab, the BPF Web application briefly displays content from a previously displayed case before refreshing the view with the correct content. |
PJ34521 | Fix | BPF Web application |
Null values for BPF fields designated as "Read from Workflow" are not updated when a user saves a case. |
PJ34522 | Fix |
BPF Web application BPF Documentation |
The display value of a Date/Time parameter is passed to lookup functions instead of the standardized format. |
PJ34524 | Fix | BPF Web application | Tools are not displayed for the CASEQUERY inbasket when the inbasket is opened from a search. |
PJ34525 | Fix | BPF Web application | The path to spacer.gif in the Bp8SignInModuleJSP.jsp page is not correct. |
PJ34526 | Fix | BPF Web application | The toolbar displays tools on two lines even after the BPF window is resized or enlarged. |
PJ34589 | Fix | BPF Documentation | No documentation is available for adding and configuring the system properties that were introduced in P8PE-4.0.2-001.001. There properties must be added and configured in vwtaskman.xml before a user starts the Content Manager instance for BPF_Operations. |
PJ34527 | Fix |
BPF Web application BPF Explorer |
The order in which inbaskets are displayed in the BPF Web application is not consistent with the order configured for the inbaskets in BPF Explorer. |
PJ34528 | Fix |
BPF Web application |
If the bootstrap object store name contains special characters, an error occurs when the user clicks Search in the toolbar. |
PJ34529 | Fix |
BPF_Operations |
The BPF_ Operations::updateCaseWithRoster method fails if the RosterName parameter is an empty string (" "). |
PJ34588 | Fix |
BPF_Operations |
The BPF_Operations::updateCaseWithMultiOS method cannot retrieve or update properties for an attachment document that is not located in the same object store as the case. |
PJ34530 | Fix |
BPF Web application BPF Explorer |
Users cannot sort inbaskets for a role if multiple roles can access the same inbaskets. |
PJ34531 | Fix |
BPF Web application |
A BPF case field that is configured as a lookup field is displayed on the Case tab even if the field is configured as hidden (Visible=NO) for the inbasket. |
PJ34533 | Enhancement |
BPF Web application |
Added support for SSO/TAM in BPF 4.1. |
PJ34534 | Fix |
BPF Documentation |
The BPF Attachment Tab help does not correctly describe the URL parameter _showatt. |
PJ34535 | Fix |
BPF Web application |
Attachment visibility does not work as expected if the attachment visibility is set to no for an inbasket, the content URL parameter _showatt is set to 1 for a tab, and the Web application setting for attachments visibility is set to true. |
PJ34537 | Fix |
BPF Web application |
If the URL _showatt parameter for a custom tab is set to 1 or is missing, BPF displays attachments on the tab even though the Web application setting for attachments visibility is set to false. |
PJ34562 | Fix |
BPF Web application |
If log4j.xml is set to the debug level, the BPF Web application does not log the SQL statement for the Inbasket CaseCount function in the bp8.log file. |
PJ34563 | Fix |
BPF Web application |
Under certain conditions, BPF Web application incorrectly displays tools in two rows when they can fit in a single row. |
PJ34566 | Fix |
BPF Explorer |
Fixes a problem whereby the following fields need to be
set as
follows - CASE_FIELDS.DB_REF=0, CASE_FIELDS.INDEX_REF=0,
CASE_FIELDS.Workflow_REF=0 and CUSTOM_FILTERS.REF=0 |
PJ34567 | Fix |
BPF Web application |
The Split Case tool does not populate fields in a new case correctly if both the original case and the new case contain a field that is populated using the lookup service URL feature. |
PJ34568 | Fix |
BPF Web application |
BPF behaves differently if a user pastes a value into a lookup field and then immediately dispatches the case with a selected action than if the user types the value into the lookup field and then dispatches the case. |
PJ34569 | Fix |
BPF Web application |
If a code for a picklist contains a space (' '), the associated inbasket filter does not work correctly. |
PJ34570 | Fix |
BPF Web application |
The Attachments tab cannot display a document name that is too long. |
PJ34571 | Fix |
BPF Web application |
The Split Case tool displays an error message that is not localized when a property that does not exist is exposed. |
PJ34572 | Fix |
BPF Web application |
BPF logs a Case Open event for other activities when a user selects the Enable Open Case event option for an Inbasket. |
PJ34573 | Fix |
BPF Web application |
BPF incorrectly displays the code and description of a picklist when the user configures the picklist to display only the description. |
PJ34574 | Fix |
BPF Web application |
The Add Document tool fails to display a picklist correctly after the user switches to a different case type. |
PJ33536 | Fix |
BPF Web application |
BPF logs a large number of the error "User 'xxxxxxx' does not have a default security profile assigned" in the bp8.log under normal conditions. |
PJ34575 | Fix |
BPF Web application |
The BPF "Use web server time zone for date field calculation" setting does not work for Inbasket Filters. |
PJ34576 | Fix |
BPF Web application |
In certain conditions, BPF takes more than 7 minutes to save and retrieve a layout. |
PJ34443 | Enhancement |
BPF Web application |
Users can now configure multiple Case tabs. |
PJ34577 | Fix |
BPF_Operations |
The BPF_Operations::updateCase method encounters a database access error if the BPF Metastore resides on an Oracle RAC. |
PJ34578 | Fix |
BPF Web application |
BPF custom tabs do not consistently display the message "please wait..." when the content of the tabs is being loaded. |
PJ33555 | Fix |
BPF_Operations |
An error occurs if the BPF_Operations::attachDoc(WithRoster) method attempts to update a property that does not exist for an attachment. |
PJ34582 | Fix |
BPF Web application |
Elements that are located at the extreme right elements of the configurable Toolbar do not display properly. |
PJ34583 | Fix |
BPF Web application |
When a user navigates through BPF fields by using a mouse, BPF does not put focus back into a lookup field after a "no matching records" message is displayed. |
PJ34584 | Fix |
BPF Web application |
Case field updates that have user picklist values configured as inbasket operations on Actions/Responses in BPF Explorer are not working in Bulk Processing. |
PJ34585 | Fix |
BPF Documentation |
The BPF Tuning Guide does not document the need to set the case ID reservation size to 1000 to avoid having cases lock in GetNext mode under load. |
PJ34586 | Fix |
BPF Web application |
Long Bp8Reason values that contain spaces do not display correctly in the BPF Reasons window. |
PJ34587 | Fix |
BPF Web application |
Using an & (ampersand) in the code of a picklist causes the associated inbasket filter to fail. |
PJ34058 | Fix |
BPF Web application |
The {CLASS_ID} macro that is configured in the Bp8Actions.xml file always has the value of { } at runtime. |
PJ34579 | Fix |
BPF Web application |
An error occurs when a user who has the Japanese language set in Internet Explorer attempts to use the lookup interface in the BPF Web application. |
History | Date | Change |
---|---|---|
Release | DD Month YYYY | Created for IBM Business Process Framework Version 4.1 Fix Pack 6 |
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27020661