FileNet Business Process Framework (BPF) Fix Pack Readme: BPF-3.6.0-007
©Copyright IBM Corporation 2009. All Rights Reserved.

About this fix pack
New in this fix pack
New in BPF-3.6.0-006
New in BPF-3.6.0-005
New in BPF-3.6.0-004
New in BPF-3.6.0-003
New in BPF-3.6.0-002
New in BPF-3.6.0-001
Compatibility
Installation, migration, upgrade, and configuration
Requirements
Certifications
New and changed BPF Web application files
Installing this fix pack
Uninstalling this fix pack
Product fix history
Contact IBM support
Accessing IBM FileNet documentation, compatibility matrices, and fix packs
Notices
Trademarks

About this fix pack

The IBM® FileNet® Business Process Framework BPF-3.6.0-007 fix pack includes updates to BPF Explorer, BPF operations, and BPF Web application.

The BPF-3.6.0-007 fix pack is intended for installation on an existing BPF-3.6.0 system that is running in a FileNet P8 3.5 or later environment. The system can be running BPF-3.6.0 GA or any of the earlier BPF-3.6.0 fix packs. If you have not yet installed Business Process Framework, you must install the BPF-3.6.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 resolved defects in this fix pack, see Product fix history.

New in BPF-3.6.0-006

This fix pack introduces the following new features:

New settings for Action Dialog windows in BPF Explorer

Support multiple Case tabs in the BPF Web application

This fix pack adds support for using multiple Case tabs in the BPF Web application. You can configure multiple Case tabs and spread the inbasket case fields among the pages.

Use of this features requires some configuration and custom coding in the EventHandlers.js::onCaseDisplay method. Refer to the IBM FileNet Business Process Framework Developer Guide for more information.

New in BPF-3.6.0-005

This fix pack introduces the following new feature:

Support for MS SQL Server 2005 as the BPF Metastore database

This fix pack adds support for Microsoft SQL Server 2005 as the database type of the BPF Metastore.

New in BPF-3.6.0-004

This fix pack introduces the following new feature:

Enhancements to the display order of shared Inbaskets which belong to multiple roles 

Starting in BPF 3.6, you can 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 so you can set the inbasket display order for each role without affecting the display order for other roles.

New in BPF-3.6.0-003

This fix pack introduces the following new features:

Ability to display Inbasket tools in a CASEQUERY inbasket 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 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 743855.

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 BPF Developer Guide and the code samples. You can find them on the Information Management support page (www.ibm.com/software/data/support). Select FileNet Business Process Manager from the "Select a category" list. Click Documentation under FileNet Business Process Manager Support, click Business Process Framework under Product documentation, and then click the links of FileNet Business Process Framework (BPF) Developer Guide and FileNet Business Process Framework (BPF) Developer Guide Code Samples for v3.6.

This enhancement resulted from fixes to resolve defect 748639.

SQL Script Changes to Handle Upgrading BPF 3.5.x Systems to Take Advantage of Enhanced Pick List Display Behavior

As documented in the IBM FileNet Business Process Framework Release Notes, the Inbasket Filters Properties dialog box has been updated in BPF 3.6 to include the new Pick List Display Behavior drop-down list box. You can use this box to indicate whether pick list items for an inbasket filter are to be presented to the user by using either the code or description.

Previously, this behavior was achieved using the Use ID check box on either the Application Fields Properties dialog box or the Inbasket Filter Properties dialog box. These check boxes have been removed from the dialog boxes in BPF 3.6.

In BPF 3.5.2, the Use ID functionality set the values of specific fields in the CASE_FIELDS and CUSTOM_FILTERS tables to 1. Therefore, prior to BPF-3.6.0-003, if you were upgrading from BPF 3.5.2 to BPF 3.6, you had to reset the values associated with these fields to 0 (zero) manually. You had to use either a SQL script or standard database administration tools for the specific RDBMS in which the Bp8Metastore resides to reset this value for the following fields:.

This manual procedure is unnecessary starting with BPF-3.6.0-003 because the BPF Explorer Import feature automatically sets each of these fields to 0 whenever it imports a BPF configuration manifest. You can achieve the same effect by running the Step3 SQL script when you upgrade to the BPF-3.6.0-003 fix pack or a subsequent fix pack.

New in BPF-3.6.0-002

This fix pack introduces the following new features:

"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.

You can enable this option only in the default layout. You cannot enable this option if your role was assigned to a different layout in the BPF Layout Designer.

If the "Hide Inbaskets when opening Case" option is enabled, the BPF Web application behaves as follows when you open a case in the GetNext/Sequential mode or by double-clicking a case record in Browse mode:

When you close the case and return to the Case list, the Logo, Filters, and Inbaskets List modules are displayed again and the Inbaskets drop-down list is hidden.

Enhancements to opening cases from Workplace search result

This fix pack enhances the methodology used to open a case for viewing or processing from Workplace search results. These enhancements fix defect 740231, "Read only attribute for locked cases has been removed when opened from BPF Case Search."

The enhancements for viewing a case, that is, opening a BPF case from Workplace search results when command 9000 is configured, are as follows:

The enhancements for processing a case, that is, opening a BPF case from Workplace search results when command 9010 is configured, are as follows:

Changes in opening case attachments

This fix pack introduces a change in BPF behavior when a user opens a case attachment that is not a Bp8Case custom object. Previously, BPF attempted to open such an attachment in the BPF Integration Servlet, which resulted in an error "Invalid Case ID(xxxxxx)." With this fix pack, BPF now opens a case attachment that is not a Bp8Case custom object through Workplace and displays the properties information page for the attachment.

This change resulted from fixes to resolve defect 742603.

Enhancements to the BPF Web application

This fix pack introduces the following minor enhancements to the BPF Web application:

New in BPF-3.6.0-001

This fix pack did not introduce any new features.

Compatibility

For information, see the IBM FileNet Business Process Framework Hardware and Software Requirements and the P8-3.5.x Fix Pack Dependency/Compatibility Matrix.

Installation, migration, upgrade, and configuration

Requirements

The BPF-3.6.0-007 fix pack supports FileNet P8 3.5.x. At a minimum, the following components must be installed before you install this fix pack:

Certifications

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.

New and changed BPF Web application files

This fix pack includes the following changed and new files for your BPF Web application. You will need to install these files in the installation location and deployment location for your BPF Web application. For information about installing these files, see Install new and changed files.

BPF Web application folder File New as of...
root About.jsp  
Bp8Dialog.jsp  
Bp8SSOSignout.jsp -003
Bp8ViewerFrameset.jsp  
RegisterModulePopUp.jsp  
UserPreferences.jsp  
Bp8BulkIFrameEntry.jsp  
\forms\misc formsCustom.js
\css Bp8Styles.css  
\inc InitUserPreferences.inc  
\js Bp8BusinessObjects.js  
Bp8Errors.js  
Bp8ContextMenu.js  
Bp8InitMain.js  
Bp8Util.js  
CreateCase.js  
RemoteFunctions.js  
RemoteScripting.js  
\js\layout BPFLayoutInitMain.js  
\plugins\custom EventHandlers.js.template  
\plugins\tabs\attachment Bp8AttachmentsTab.jsp  
\plugins\tabs\attachment\ui Bp8AttachmentsTab.jsp  
\plugins\tabs\attachment\xsl\include Bp8GetFormattedValue.xsl  
Bp8GetItemLinkURL.xsl  
ListViewContextMenu.xsl  
\plugins\tabs\attachment\xsl\list Bp8AttachTabSelectableListView.xsl  
\plugins\tabs\table TableTab.jsp  
\plugins\tools\add_document\ui Bp8AddDocument.jsp  
\plugins\tools\create_browse AddAttachmentCallback.jsp  
AttachmentList.jsp  
CreateCase.jsp  
\plugins\tools\create_case Bp8CreateCase.jsp  
\UI-INF\jsp\modules\apps Bp8MainModuleJSP.jsp  
Bp8SignInModuleJSP.jsp  
\UI-INF\jsp\ui Bp8AttachIFrameEntry.jsp  
Bp8ViewerDocs.jsp  
\vbs Bp8Util.vbs  
\WEB-INF Bp8Actions.xml  
Bp8CaseQueryLayout.xml  
Bp8CaseQueryLayout_TwoLines.xml -003
Bp8ExtCommands.xml  
Bp8ExtTasks.xml  
Bp8Layout.xml  
user-preferences.xml  
\WEB-INF\lib bpfCM.jar  
bpfCMResources.jar  
bpfLangResources.jar  
bpfWA.jar  
commons-httpclient.jar -005
\WEB-INF\xsl\list Bp8FavoriteAttachDocsSelectableListView.xsl  
\WEB-INF\xsl\include Bp8AdoTransform.xsl  
Bp8GetItemLinkURL.xsl  
ListViewContextMenu.xsl  
\xsl Bp8CaseProps.xsl  
Bp8Filters.xsl  
Bp8Inbaskets.xsl  
Bp8CaseAudit.xsl  

Install this fix pack

To install this fix pack:

  1. Install new and changed files.
  2. Install the updated BPF Explorer.
  3. Update the BPF Web application configuration.
  4. Update the BPF operations.
  5. Validate the BPF Web application.

Install new and changed files

To install the new and changed files for this fix pack:

  1. If you installed any fix pack that is later than the minimum required version, for the Content Engine, Process Engine, Application Engine, or eForms, replace the following JAR files for that component:

    Component JAR Files
    Content Engine javaapi.jar
    Process Engine pe.jar
    peResources.jar
    Application Engine mailapi.jar
    p8ciops.jar
    p8toolkit.jar
    soap.jar
    commons-fileupload-1.*.jar
    eForms eForms.jar
    eFormsResources.jar
    forms.js

    You can find the new versions of these files in the Workplace WEB-INF\lib folder. By default the WEB-INF folder on the Application Engine is in the following location:

    To replace the JAR files:

    To replace the forms.js file:

    By default, the BPF installation location is

    Important: You will also need to copy these JAR files and the forms.js to your BPF Web application deployment location as described in step 7.

  2. Download the fix pack and extract the files to a temporary folder on your local system.
  3. 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.
  4. Stop the application server on which your BPF Web application is running.
  5. Use the Export Manifest option in BPF Explorer to back up the BPF Metastore configuration information. To access the Export Manifest option:
    1. Right-click Export and Import Management and select All tasks > Add All Objects to Export List.
    2. Right-click Export and Import Management again and select All tasks > Export XML Manifest.
  6. 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.

  7. Update the BPF Web application files with the new and changed files from the fix pack.

    Folder structure

    1. 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.
    2. Copy any JAR files and the forms.js file that you replaced in step 1 to the /WEB-INF/lib folder in the deployment folder structure.

    8. WAR file

    1. Copy the WAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_war.
    2. Open a command window.
    3. Navigate to C:\temp_war and then run the following command to extract the WAR file contents:

      jar -xvf bpf_app.war
    4. Delete the WAR file from the C:\temp_war folder.
    5. 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.
    6. Copy any JAR files and the forms.js file that you replaced in step 1 to the C:\temp_war\WEB-INF\lib folder.

    EAR file

    1. Copy the EAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_ear.
    2. Open a command window.
    3. 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
    4. Delete the EAR file from the C:\temp_ear folder.
    5. 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.
    6. Navigate to C:\temp_war and then run the following command to extract the WAR file contents:

         jar -xvf bpf_app.war

    7. Delete the WAR file from the C:\temp_war folder.
    8. 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.
    9. Copy any JAR files and the forms.js file that you replaced in step 1 to the corresponding folders in the C:\temp_war\WEB-INF\lib folder.
  8. 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.

  9. WAR or EAR file deployment: Repackage the updated file structure into a new WAR or EAR file:

    WAR file

    1. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command:

      jar -cvf bpf_app.war *
    2. Copy the WAR file to the BPF Web application deployment location.

    10. EAR File

    1. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command:

      jar -cvf bpf_app.war *
    2. Copy the WAR file generated in the previous step from the C:\temp_war folder to the C:\temp_ear folder.
    3. Repackage the EAR file by executing the following command:

      jar -cvf bpf_app.ear *
    4. Copy the EAR file to the BPF Web application deployment location
  10. 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

  11. JBoss and WebSphere only: Restart the application server on which BPF Web application is running.
  12. WebLogic only: Redeploy the BPF Web application.

Install the updated BPF Explorer

  1. Run the filenet_bpf_explorer_setup.exe program in the BPF-3.6.0-007 fix pack to uninstall BPF Explorer.
  2. Run the filenet_bpf_explorer_setup.exe program in the BPF-3.6.0-007 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

  1. If upgrading from BPF-3.6 GA, change the width specified for the Bp8Reason and Bp8Description properties by performing the following steps:
    1. Open Enterprise Manager.
    2. In the BPF object store, browse Other Classes > Custom Object > Bp8Object > Bp8AuditLogItem.
    3. Right-click Bp8AuditLogItem and then click Properties.
    4. On the Property Definitions tab, select Bp8Reason and then click Edit.
    5. On the More tab, change the Maximum String Length value to 256, and then click OK.
    6. On the Property Definitions tab, select Bp8Description and then click Edit.
    7. On the More tab, change the Maximum String Length value to 256, and then click OK.
  2. Upgrade the BPF 3.6.0 metastore schema.

    Review the following topics in the Business Process Framework Installation Guide Release 3.6 (for P8 3.5.x):

    In prior releases, you could delete a company object (BUSINESS_UNIT_ID) even if user objects (USER_UNITS) still referenced that company. The BPF-3.6.0-007 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. You must manually reassign companies to these users after you apply the fix pack.

    1. 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)
    2. Edit the BPF-3.6.0-007 Step3 script to match your environment as needed:
      • If your BPF Metastore is on Microsoft® SQL Server, edit the Step3.mssql.Bp8.Metabase.1.0.sql script.
      • If your BPF Metastore is on Oracle, edit the Step3.oracle.Bp8.Metabase.1.0.sql script.
    3. Run the Step3 script. For information on running this script, refer to "Load BPF Metastore" in the IBM FileNet Business Process Framework Installation Guide.
  3. Log into BPF Explorer.
  4. If upgrading from BPF-3.6 GA or BPF-3.6.0-001, Update the Adhoc search definition options:
    1. In the console tree, expand the Application Settings node and click Web Application
    2. 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.
    3. 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.
  5. If you customized the Attachment Panel Document List SQL statements for any inbaskets, perform the following steps for each of these inbaskets:
    1. In the console tree, expand the Inbasket Configurations node.
    2. Right-click the inbasket that you want to update and click Properties.
    3. Click the General tab.
    4. 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.
  6. If you are upgrading from BPF-3.6 GA or BPF-3.6.0-001 and you are using the sample Case Management application, change the inbasket type for the Indexer role:
    1. In the console tree, expand Inbasket Configuration node.
    2. Right-click the Matching Inbasket of the Indexer role and click Properties.
    3. Click the General tab.
    4. From the Inbasket type list, select STANDARD.
  7. If upgrading from BPF-3.6 GA , import the BPF-3.6.0-007 qcreate_base.xml file by performing the following steps:
    1. Log in to Workplace as the Process Engine Administrator.
    2. Launch Process Configuration Console from the Workplace Admin tab.
    3. Right-click the router and click Export to XML file to create a backup file containing your workflow region information.
    4. Stop Component Manager by using Process Task Manager on the Application Engine.
    5. Run the wfutil utility that is provided with the BPF 3.6 media to import the qcreate_base.xml file from the fix pack.

      Refer to "Base Or Solution-Specific Workflow Object Creation" in the "Troubleshooting" section of the IBM FileNet Business Process Framework Installation Guide Release 3.6 (for P8 3.5.x) for information on using the wfutil utility.

    6. Restart Component Manager.

Update the BPF Operations

Perform the following steps to update BPF Operation:

  1. Stop Component Manager by using Process Task Manager on the Application Engine.
  2. Back up the bp8ciops.jar file. By default, this file is in the following folder:
  3. Extract the bp8_config.xml and log4j.xml files from the currently installed bp8ciops.jar file.
  4. 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.
  5. Replace the bp8ciops.jar that is currently installed on the BPF application server with the file that you extracted in step 4.
  6. Restart the Component Manager.
  7. Verify that the BPF operations work correctly.

    If you use the sample Case Management application, you can ensure that the BPF operations are working correctly as follows:
    1. In FileNet Enterprise Manager, add a new document to the Case Management Documents document class.
    2. Set the DocEntryStatus and DocType values to 1.

    If the BPF operations are working correctly, BPF creates a new case.

Validate the BPF Web application

Before users access the BPF Web application, validate that the application is working:

  1. Clear Internet Explorer caches by deleting Temporary Internet Files with all offline content on all BPF clients.
  2. 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.

Uninstalling this fix pack

You cannot uninstall the BPF-3.6.0-007 fix pack.

Product fix history

BPF-3.6.0-007

Defect ID APAR Name Type Area/
Sub-system		 Description
845773 PJ36875 Fix BPF Web Application Fixes a problem where metadata cache corruption occurred when a case was processed from the search result window.
845206 PJ36964 Fix BPF Web Application Fixes a problem where the onAfterInbasketLoad event fired several times when loading a bulk operation enabled inbasket for the first time.
841732 PJ36733 Fix BPF Web Application Fixes a problem where the LockUser column in the Inbasket browse list is blank in some environments.
840969 PJ36738 Fix BPF Web Application Fixes a problem where the Edit Layout tool is not displayed in the BPF toolbar when the LDAP repository is not Active Directory.
830926 PJ36518 Fix BPF Web Application Fixes a problem where BPF encountered locking problems on the Process Engine database.
828928 PJ35265 Fix BPF Web Application Fixes a problem where the create_case tool creates the Bp8Attachment CE objects after the workflow is launched instead of before.
825564 PJ36430 Fix BPF Web Application Fixes a problem where the role drop down does not display the current role.
815584 PJ35683 Enh BPF Documentation Added instructions for estimating the size of the BPF metadata cache to the IBM FileNet Business Process Framework Performance Tuning Guide.
811015 PJ36149 Fix BPF Operations and BPF Web Application Fixes a problem which caused BPF_Operations to create cases with duplicate Bp8CaseIDs.
800473  PJ35807
/PJ36043		 Fix BPF Web Application Fixes a problem where Integration Command 9010 opens cases with the Master Role regardless of the actual current role of the user.
797336 PJ37151 Fix BPF Web Application Fixes a problem where no cell boundaries are displayed for HTML "input" controls in IE 7.
797273 PJ35806 Fix BPF Web Application Fixes a problem that the Lookup feature uses escape() instead of the appropriate Javascript URI method to encode URL parameters.
794115 PJ35574 Fix BPF Web Application Fixes a problem where clicking on the OK or Cancel buttons on a Warning message from a Java CommitCaseEventHandler plugin does not leave the current case open for corrections.
793817 PJ37153 Fix BPF Web Application Fixes a problem where Lookups are not triggered when tabbing out of the field if the mouse happens to be just over the lookup button.
792059 PJ35555 Fix BPF Web Application Fixes a problem where BPF does not save date values correctly when Daylight Savings Time is in effect.
788292 PJ35251 Fix BPF Web Application Fixes a problem when using Novell eDirectory in which the security permission settings on the custom object used for each table row in the BPF Table Tab is effective only in the case of individual users.
786662 PJ37154 Fix BPF Operations Fixes a problem where attachDoc() from Bp8Operations fails to update the Bp8Attachment[] field when it is trying to attach a document to the current workflow.


BPF-3.6.0-006

Defect ID APAR Name Type Area/
Sub-system		 Description
770939 PJ34299 / 35821837 Fix BPF Explorer Fixes a problem where the BPF Explorer UI hangs after sorting Responses in inbaskets when two Responses have the same Order number.
769230, 769240 PJ35166 / 35966966, PJ35201 / 35968341 Fix BPF Web Application Fixes a problem where the case tabs' order displayed in the BPF Web Application is not consistent with the BPF Explorer settings when the Bp8Metastore is deployed on MSSQL 2005.
755008 PJ34109 / 35714643 Fix BPF Explorer Fixes a problem with BPF Explorer in which the 'New Tool' wizard saves tools with a NULL value for BROWSE_MODE (instead of '0') when 'Browse mode' is left unselected.
 779728 PJ34702 / 35888477 Fix BPF Web Application

Fixes a problem with the Table tab where when the cache is set to 1 (_cache=1), the data is not showing when clicking on the tab a second time.
751164 PJ35202 / 35968346
 Fix BPF Explorer Fixes a problem where the length of field 'Code' within the table 'PICK_LISTS_ITEMS' in BP8MetaStore was too short and needed to be increased.
776234 PJ34484 / 35851409 Fix BPF Metastore Fixes a problem that errors occur when executing the MSSQL Step 3 script as part of installing on BPF 3.6.0-005.
757434 PJ35203 / 35968350 Fix BPF Web Application Implements an enhancement to allow multiple Case Tabs in BPF by modifying EventHandlers.js::onCaseDisplay to pass TabContent.
752374 PJ34248 / 35814216
 Fix BPF Web Application Fixes a problem that viewing attachments does not work in a multidomain Windows environment.
761623
 PJ34110 / 35780127 Fix BPF Web Application Fixes a problem that users are not warned that the case is not locked when opened from CASEQUERY (9000) with no editable fields.
767066 PJ35204 / 35968354 Fix BPF Web Application Fixes a problem that the BPF case Audit tab shows the GUID of the attached document instead of the document title.
772305 PJ35205 / 35968358 Enh
BPF Web Application
 Implements an enhancement by adding application settings to BPF Explorer to control the size and behavior of the Reasons dialog in the BPF Web application.
782443 PJ34797 / 35912658 Fix BPF Web Application Fixes a problem in which Bp8Actions on the Attachments tab and in the Viewer receive runtime JS errors after you apply BPF-3.6.0-005.
767864 PJ34058 / 35791081 Fix BPF Web Application Fixes a problem that the CLASS_ID macro configured in Bp8Actions.xml always has the value of { } at runtime. 
759975 PJ35206 / 35968365
 Fix BPF Operation Fixes a problem that caused the updateCaseWithRoster to fail with the parameter sRosterName as "" (empty string).
759977 PJ35207 / 35968372 Fix BPF Operation Fixes a problem that the detachFolderWithRoster method with an invalid roster name does not return an error.
781792 PJ34897 / 35907640 Fix BPF Web Application Fixes a problem that scroll bars are missing from BPF Actions while viewing Properties.
782769 PJ34898 / 35923550 Fix BPF Web Application Fixes a problem that it is not possible to view all attachments when DocumentTitles are too long (no scrollbars on Case tab attachments panel).
371646 PJ35208 / 35968395 Fix BPF Documentation Updates the WebSphere installation instructions by removing the information that "PARENT_LAST" should NOT used for Class loader mode.
387310 PJ35209 / 35968413 Fix BPF Documentation Updates the documentation to indicate that CredentialsProtection/UserToken=Clear should not be used.
390926 PJ35214 / 35968418 Fix BPF Documentation Clarifies the descriptions of the CE security settings.
553451 PJ35210 / 35968421 Fix BPF Documentation Updates the procedures for upgrading from BPF 3.5.2 to 3.6.0.
662027 PJ35211 / 35968429 Fix BPF Documentation Adds information about using cases that  involve shared BPF 3.5.2 and 3.6.0 instances.
677566 PJ35212 / 35968433 Fix BPF Documentation Corrects the Priority filter template information in the BPF 3.6 Install Guide.
744728 PJ35213 / 35968450 Fix BPF Documentation Documents the workaround to fix "NULL error while trying to view document from the Attachment Tab" when the host names in the BPF and AE URLs are different.
767194 PJ35190 / 35792925 Fix BPF Documentation Documents how to avoid an error that can occur when opening a case from CASEQUERY if a Step name is assigned for the CASEQUERY Inbasket.


BPF-3.6.0-005

Defect ID APAR Name Type Area/
Sub-system		 Description
751305 PJ33704 / 35741568 Fix BPF Web Application Fixes a problem that an exception pops up when clicking the PDF icon inside the eForms tab.
755013 PJ33434 / 35706029 Fix BPF Web Application Fixes a problem that the ampersand (&) character in the code of a picklist causes the associated inbasket filter to fail.
755427 PJ33702 / 35741532
 Fix BPF Web Application Fixes a problem that there inconsistencies between the BPF Web UI and the key values in the strings.en.txt file.
756560 PJ33703 / 35741554 Enh BPF Web Application

BPF Explorer

BPF Operation		 Adds support for SQL Server 2005 as the Metastore database.
751425
PJ33705 / 35741591 Fix BPF Explorer Fixes a problem that allows a new company to be deleted even though it has a relationship with a parent table.
753682 PJ33706 / 35702186 Fix BPF Explorer Fixes a problem that the import function fails when the inbasket filters use picklists that have empty values for 'Width' or 'Max chars'.
757427 PJ33708 / 35741620 Fix BPF Explorer Fixes a problem that the order of the inbasket role list changes if the order of the tabs is changed.
391127 PJ33709 / 35741638 Fix BPF Web Application Fixes a problem that the document window which is opened by the 'Open Document' action is not closed when the relevant case is closed.
751417 PJ33710 / 35741717 Fix BPF Web Application Fixes a problem that the document title value entered on the tool UI is not applied to attached documents.
751466
PJ33711 / 35741730 Fix BPF Web Application Fixes a problem that an error message pops up when clicking "OK" button on the create new case screen after the session has expired.
754022 PJ33712 / 35704913    Fix BPF Web Application Fixes a problem that a validation error pops up when you enter a time value in a date/time field.
755001 PJ33447 / 35704616  Fix BPF Web Application Fixes a problem that it takes more than 7 minutes to  save and retrieve a layout .
386608 PJ33698 / 35741379 Fix BPF Documentation Corrects the transfer workflow information in the eForms Integration Guide.
754141 PJ33700 / 35741477 Fix BPF Documentation Clarifies the information on  configuring the Operations at the Response Tab for an Inbasket, if the type of the Case Field is date/datetime and "Constant" is the Builtin Property, the value will be the milliseconds since January 1, 1970, 00:00:00 GMT.

BPF-3.6.0-004

Defect ID APAR Name Type Area/
Sub-system		 Description

384565

 PJ33535 / 35712755
 Fix BPF Web Application Fixes a problem that if two different Web modules of the same type are registered they are both assigned the same URL.

750360

PJ33536 / 35671046

 Fix BPF Web Application Fixes a problem that bp8.log is flooded with the error "User 'xxxxxxx' does not have a default security profile assigned".

751169

PJ33537 / 35713946
 Fix BPF Web Application Fixes a problem that BPF "Use web server time zone for date field calculation" setting is not working for Inbasket Filters.

751410

 PJ33538 / 35713963
 Fix BPF Web Application Fixes a problem that "Open viewer when case is open" general preference should not open the Viewer if the case has no attachments.

751159

 PJ33540 / 35713986
 Fix BPF Web Application Fixes a problem that when adding a document that has a long name, the attachment tab table width is too small.

751464

 PJ33541 / 35714002
 Fix BPF Web Application Fixes a problem that when there is a large number of case fields the user cannot see all the fields because there is no scroll bar.

748196

PJ33534 / 35655923

Fix BPF Explorer Fixes a problem that the path to spacer.gif in the bp8signinmodule.jsp page is incorrect.

751162

PJ33542 / 20035875
 Fix BPF Explorer Fixes a problem that caused a Java Script error when tabbing through fields.

747732

PJ33096 / 35622414 Fix BPF Explorer Fixes a problem that inbaskets could n ot be sorted when multiple roles could access the same inbaskets.

751414

 PJ33543 / 35714029
 Fix BPF Explorer Fixes a problem that when inbasket template name is empty, error message is not correctly.
746567 PJ32782 / 35608553
 Fix BPF Explorer Fixes a problem that  BPF Import fails with error 457 when using BPF Explorer for 3.6.0-001 or -002.

751439

 PJ33550 / 35714918
Fix BPF Explorer & BPF Web Application Fixes a problem that the calendar icon does not show up when configuring case field with date type.

751467

 PJ33551 / 35720569
 Fix BPF Explorer Fixes a problem that attachment visibility has only two options: Yes and No, should has not the third option in BPF Explorer.

751170

 PJ33552 / 35720762
 Fix BPF Web Application Fixes a problem that the extreme right elements of the configurable Toolbar do not display correctly.

751427

 PJ33553 / 35720771 Fix BPF Web Application Fixes a problem that when using a custom tool, an error message is received.

751161

 PJ33554 / 35720786
 Fix BPF Web Application Fixes a problem that when the Inbasket settings = no, _showatt=1, and Web application setting=true: attachments do not work as expected.

751148

PJ33555 / 35678474

 Fix BPF Operation Fixes a problem that when updating a case, the component is trying to update the 'DocsAttached' property of the Bp8Case's subclass.

751288

  PJ32377 / 35537144 Enh BPF Operation Makes the BPF operation code thread safe.

751171

 PJ33547 / 35722118 Fix BPF Web Application Fixes a problem that the custom tab should display the "please wait..." message until the content of the custom tab is loaded.

555371

 PJ33548 / 35722122 Fix BPF Web Application Fixes a problem that the value of a user picklist configured with a response is not passed to the configured case field when executing a bulk response.
751415
 PJ33549 / 35722129 Fix BPF Web Application Fixed a problem that the image viewer can not be closed after processing the last case in the BPF Web application.
752919 PJ33334 / 35692503 Fix BPF Web Application Fixes a problem that BPF is hanging if a custom object is not associated with a case.
752950 PJ33332 / 35696274 Fix BPF Web Application Fixes a problem that causes the toolbar to display on two lines even after the BPF window is resized to allow all tools to appear on one line.
753934 PJ33546 / 35720794
 Fix BPF Web Application Fixes a problem that causes an error to display when Case fields are configured with user lookup.

 

BPF-3.6.0-003

Defect ID APAR Name Type Area/
Sub-system		 Description

743010

 PJ33404 / 35703989
 Fix BPF Web Application Fix a problem that null values are not updated when you save a case.

748639

PJ32663 / 35581253 Enh BPF Web Application Enables 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.

744823

PJ32530 / 35570316 Fix BPF Web Application Fixes a problem that the wrong attachment displays when opening the attachment from the attachment panel.

743855

 PJ33406 / 35570441 Enh BPF Web Application

Enhances the product so that the Inbasket Toolbar displays when opening a Case in the CASEQUERY Inbasket from Search Results.

743013

PJ32361 / 35520548 Fix BPF Web Application Fixes a problem with BPF custom tab rendering.

747020

PJ32711 / 35596401 Fix BPF Web Application Fixes an issue with lookup options, such that hidden Data fields are visible.

746094

 PJ33405 / 35595048 Fix BPF Explorer Fixes a problem in which hidden attributes are not exported.

746090

PJ33407 / 35595034 Fix BPF Explorer Fixes a problem that pick list icons are not correctly added to the export manifest.

745950

PJ32623 / 35582441 Fix BPF Explorer Fixes a problem that the 'Use ID' option has been removed from BPF Explorer but the metadata is still there and still used.

748926

 PJ33409 / 35537131 Fix BPF Web Application Fixes a problem that caused an incorrect Inbasket toolbar layout in the BPF Web application.

748642

PJ32691 / 35456945 Fix BPF Web Application  Fixes a problem in which the 'AddDocument' tool fails to display a picklist correctly after switching from one case type to another.

743007

PJ33410 / 35164512 Fix BPF Web Application Fixes a problem that the 'Case Open' event is logged for other activities when 'Enable Open Case event' is selected for the Inbasket.

748632

 PJ32545 / 35572217 Fix BPF Web Application Fixes a problem in which the error 'User does not have a default security profile assigned' occurs when logging in to the BPF web application for the first time.

748634

 PJ32553 / 35571474 Fix BPF Web Application Fixes a problem that the Inbasket filter items display the picklist 'code+description' instead of just 'description'.

742263

 PJ32399 / 35546630 Fix BPF Web Application Fixes a problem that the sorting of Cases fails in browse mode if the field name used for the sort contains 'desc'.

745905

PJ33196 / 35593540 Fix BPF Web Application Fixes a problem that an error occurs when changing to Last Case mode when there is no case available in the Inbasket.

748638

PJ32590 / 35581286 Fix BPF Web Application Fixes a problem that the behavior of values pasted in a lookup field is not consistent with the behavior when the values are typed into the same field.

748839

PJ32835 / 35609471 Fix BPF Web Application Fixes a problem that if the picklist code contains a space (' '), the associated inbasket filter doesn't work properly.

743941

PJ33403 / 35703970 Fix BPF Web Application Fixes a problem that when the eForms case is updated, the value cannot be saved.

748436

PJ32733 / 35524500 Fix BPF Web Application

Fixes a problem that extensible Authentication(SSO) fails in BPF.
745038
 PJ32623 / 35582441  Fix BPF Documentation

Addresses the additional step required when upgrading from 3.5.2 to 3.6 and when the 'Use ID' option is used.

 

BPF-3.6.0-002

Defect ID APAR Name Type Area/
Sub-system		 Description

686377

 PJ32451 / 35568554 Fix BPF Web Application Restore the option to hide inbaskets and filters when opening a case.

556431

 PJ32453 / 35568742 Fix BPF Web Application Fixes a problem that BPF cases are locked in "GetNext" mode after being Saved and Closed.

661003

 PJ32454 / 35568787 Fix BPF Web Application Fixes a problem that on the Attachment tab, sort only works on the Title column.

556427

 PJ32456 / 35568813 Fix BPF Web Application Fixes a problem that caused BPF to truncate the last character in a field value if the length of the value equalled the maximum length of the field.

556824

 PJ32458 / 35568850 Fix BPF Web Application Fixes a performance issue in Bp8TxDataStoreImpl.

556540

 PJ32459 / 35568866 Fix BPF Web Application Fixes a problem that the User Name is not indicated while showing the message "case is locked".

661811

 PJ32460 / 35568906 Fix BPF Web Application Fixes a problem that the BPF Attachment tab still shows "Inbasket <Inbasket ID> doesn't exist for this profile" when SSL is enabled with alias/redirect.

390175

 PJ32461 / 35568926 Fix BPF Web Application Fixes a problem that Float and Money values are garbled in the Browse List display.

661792

 PJ32463 / 35568970 Fix BPF Web Application Fixes a problem that the vertical scrollbar disappears when there are too many audit log items to fit on one page.

556452

 PJ32464 / 35568995 Fix BPF Web Application and BPF Operations Fixes a problem that the array element "VWAttachment" in BPF can be assigned the incorrect property.

362990

 PJ32466 / 35569017 Fix BPF Web Application Fixes a problem that errors occur when adding or removing cases for bulk processing in DB2-based PE.

742603

 PJ32467 / 35569031 Enh BPF Web Application BPF now opens a case attachment that is not a Bp8Case custom object through Workplace and displays the properties information page for the attachment.

740231

 PJ32457 / 35568837 Fix BPF Web Application Fixes a problem that the "Read only' attribute for locked cases is removed when opening the case  from BPF Case Search.

BPF-3.6.0-001

Defect ID APAR Name Type Area/
Sub-system		 Description
198941 None Fix BPF Web Application Fixes a problem that required resizing of the BPF Viewer window in order to access the scroll bars when viewing an eForms document larger than the window.
200724 None Fix BPF Web Application Fixes a problem that caused BPF to set the ClassificationStatus document property to 3 (failed) if the BPF Web Application Create Case Tool was used to add a  document to a new case.
203128 None Fix BPF Web Application and BPF Explorer Fixes a problem that caused incorrect alignment and wrapping of text in the Reason and Comments columns on the Audit tab.
203935 None Fix BPF Web Application

Fixes a problem that occurred in the BPF Web Application when you changed from your default role and then the session expired. This problem caused BPF to return to your default role when you logged in again and to display the message "Inbasket <Inbasket ID> doesn't exist for this profile.”
205491 None Fix BPF Web Application Fixes a problem that caused blank pages or unexpected browse list contents to be displayed if you clicked next, previous, first, or last when using Inbasket Filters in Browse mode.
207728 None Fix BPF Web Application Fixes a problem that caused an "Invalid data provided" error to be returned when a user whose locale was set to German entered a comma (,) in a currency field or a dash (-) in a Date/Time field.
208125 None Fix BPF Operations Fixes a problem in which the updateCaseWithRoster method had the wrong signature in the BPF_Operations component step.
209514 None Fix BPF Web Application Fixes a problem in the AddDocument and the CreateCase tools that caused zero-byte attachments to be created when an invalid path was given to a local file.
209685 None Fix BPF Operations Fixes a problem that prevented the detachFolderWithRoster method in BPF_Operations from working.
209688 None Fix BPF Operations Fixes a problem that prevented the AttachDocWithRoster method in BPF_Operations from working.
209692 None Fix BPF Operations Fixes a problem that prevented BPF from returning the case ID when the BPF Operation Attach Doc method was used to add the same document a second time to a case.
213010 None Fix BPF Web Application Fixes a problem that occurred when an inbasket contained a large number of items.

Contacting IBM support

For information about contacting IBM support:

  1. Navigate to the Information Management support page ( www.ibm.com/software/data/support ).
  2. On the Information Management Support page, search for: How to get support for IBM FileNet products.

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Documentation and compatibility matrices

To access documentation and compatibility matrices for IBM FileNet products:

  1. Navigate to the Product Documentation for FileNet P8 Platform support page.

    http://ibm.com/support/docview.wss?rs=3247&uid=swg27010422

  2. Select a PDF or a Doc Link, whichever is appropriate.

Fix packs

To access fix packs for IBM FileNet P8 Platform products:

  1. Navigate to the IBM Fix Central page (http://ibm.com/support/fixcentral/).
  2. Select Information Management .
  3. Select FileNet Business Process Framework.
  4. Select the Installed Version.
  5. Select the Platform and click Continue.
  6. Select Browse for fixes and click Continue.
  7. Select the fix pack you want to download and click Continue.
  8. Select Download using your browser (HTTP) and click Continue.
  9. Click the download like next to the file and save the file to your system.

Notices

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.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.