IBM Support

PJ41216: DATE/TIME IN BPF CASE ARE NOT SYNC WITH THE DATE/TIME IN SEARCH RESULTS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ***PLEASE PROVIDE THE FOLLOWING INFORMATION
    THIS FIELD IS REQUIRED.***
    
    Description of Problem (full details)
    
    OCBC encountered the same issue reported in another CRM
    20444,140,702 (Tieto Finland Oy).
    
    Scenario:
    User (Location Bangkok (Thailand) or any other country) is
    creating a case. After it when user search the case through BPF
    web application "search" link, then he finds the field value of
    "Date of Case Creation" is showing in GMT time zone. But it
    should show as his local time zone.
    
    Problem: Other country users are not able to view "date-time
    field" value in their own time zone.
    
    OCBC requested this PMR/CRM as High Priority, because it is a
    production issue.
    
    BPF Versions: In SIT BPF Version is 4.1.0-008, in UAT is
    4.1.0-008 and PRD is 4.1.0-004.
    
    Steps of the Scenario:
    (1) If a user is in Bangkok, and access the application (all the
    application servers in SG time zone).
    (2) User access the BPF Web application, inside the BPF web
    application (in all in-baskets), date-time field value is shown
    in SG time zone
    (3) But when user access the search templates and search the
    case
    (4) In search results, user see the date-time field value in GMT
    time zone.
    
    I suggested the customer try following tests.
    
    (1) Please try to set the value useEnhancedTimeZoneDetection to
    true in both AE and BPF bootstrap.properties files. You need to
    restart AE and BPF after you finished editing the files.
    (2) Please logon to Workplace and browse to Admin -> Site
    Preferences -> Time Zone. There you can set the time zone to
    'Browser Time Zone', 'AE Server Time Zone' or you can pick a
    specific time zone to use. Please let us know your test result.
    (3) Please try to search the case in Workplace, and let us know
    your test result.
    
    The customer tried above steps in their SIT Environment, but the
    problem was still there.
    
    We asked the customer to collect DEBUG level bp8.log along with
    some screenshot shots of this scenario.
    
    Before settings change (many screenshots):
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.Before_settings_change.zip
    
    After settings change (BPF log file and many screenshots):
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.After_settings_change.zip
    
    Search directly through Workplace (screenshot):
    
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.Search_directly_through_Wo
    rkplace.JPG
    
    I can see from the log snippet below that Case ID 73235 was
    created:
    
    2013-03-29 21:13:32,205 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8TxDataStoreImpl (createCase:464) -
    Case object created with Case ID 73235
    2013-03-29 21:13:32,705 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8TxDataStoreImpl
    (createAttachment:1138) - creating attachment ...
    2013-03-29 21:13:32,923 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8TxDataStoreImpl
    (createAttachment:1143) - ... attachment created
    2013-03-29 21:13:33,283 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8CaseManagerImpl (createCase0:904) -
    Creating workflow object for Case ID 73235
    2013-03-29 21:13:33,298 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8ProcessDataStoreImpl (launch:168) -
    Creating workflow object. Case XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <Object WFClassName="WFI_TFO_DocFlow"><Fields CaseTypeID="10"
    DocumentObjectStore="OCBCMYDOC"><Field Name="WFI_BranchEntity"
    Type="1" WFFieldName="WFI_BranchEntity">Hong Kong</Field><Field
    Name="WFI_Entity" Type="1"
    WFFieldName="WFI_Entity">B</Field><Field
    Name="WFI_ProductTypeMYTF" Type="1"
    WFFieldName="WFI_ProductTypeMYTF">Bankers
    Acceptance</Field><Field Name="WFI_TransactionTypeMYTF" Type="1"
    WFFieldName="WFI_TransactionTypeMYTF">Acceptance</Field><Field
    Name="WFI_CustomerName" Type="1"
    WFFieldName="WFI_CustomerName">XYZ</Field><Field
    Name="WFI_Currency" Type="1"
    WFFieldName="WFI_Currency">SGD</Field><Field Name="WFI_Amount"
    Type="1" WFFieldName="WFI_Amount">1</Field><Field
    Name="WFI_TempRemarks" Type="1"
    WFFieldName="WFI_TempRemarks"/><Field Name="WFI_Origin" Type="1"
    WFFieldName="WFI_Origin">896</Field><Field Name="Bp8CaseType"
    Type="2" WFFieldName="Bp8CaseType">10</Field><Field Type="2"
    WFFieldName="Bp8CaseID">73235</Field></Fields></Object>
    2013-03-29 21:13:33,408 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8ProcessDataStoreImpl (launch:224) -
    Workflow object created for Case ID
    {883F6730-DECA-4EAF-B880-9473280E8037}
    2013-03-29 21:13:38,252 INFO [WebContainer : 3]
    com.filenet.bp8.api.impl.Bp8TxDataStoreImpl
    (getInbasketCasesDOM:1342) - found cases in inbasket: 25
    
    How long has the problem been occurring (recent changes)? :
    About one week
    
    Does this occur on more than one station / server? :
    Yes
    
    Is there a workaround? :
    No
    
    What is the impact to the customer/system? :
    This is a production issue. Other country users are not able to
    view "date-time field" value in their own time zone.
    
    Can the problem be replicated on an internal system? Yes
    
    Are there any similar or related Defects? If Y provide ECMDB #s
    No
    
    What logs were collected and where are they located?
    Before settings change:
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.Before_settings_change.zip
    
    After settings change:
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.After_settings_change.zip
    
    Search directly through Workplace:
    https://ecurep.mainz.de.ibm.com/rest/download?filepath=90256%2C0
    00%2C834%2F2013-03-29%2F90256.000.834.Search_directly_through_Wo
    rkplace.JPG
    
    Configuration/Environment:
    Operating System: Microsoft Windows Server 2008 R2 X64, 64-bit
    Standard Editions SP1
    Database: SQL Server 2008, SP1 Standard Edition
    Application Server: Websphere 7 FP21
    FileNet Software Patch Version:
    FileNet AE 4.0.2.13-P8AE-FP013
    FileNet CE 4.5.1.7-P8CE-FP007
    FileNet PE 4.5.1.3-P8PE-FP003
    FileNet BPF 4.1.0.8-P8BPF-FP008
    FileNet IS IS 4.1.2 FP10
    ISRA 3.4.0.5
    FileNet PA FNPA 4.5.1 Base Release
    Capture 5.2
    IDM Web 4.0.3
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * BPF web application users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Date/Time in BPF Case are not sync with the Date/Time in     *
    * Search.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the BPF-4.1.0-010 GA FixPack.                          *
    ****************************************************************
    

Problem conclusion

  • The issue is fixed in BPF-4.1.0-010.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ41216

  • Reported component name

    BUS PROC FRAMEW

  • Reported component ID

    5724R7500

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-09

  • Closed date

    2014-01-23

  • Last modified date

    2014-01-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BUS PROC FRAMEW

  • Fixed component ID

    5724R7500

Applicable component levels

  • R410 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNVLC","label":"FileNet Business Process Framework"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 January 2014