PJ41299: ATTACHDOC WILL NOT ATTACH DOCUMENT TO THE BPF CASE IF THE ASSOCIATED WORK ITEM DOES NOT EXIST OR IN THE DELAY QUEUE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Description of Problem (full details)
    After applying BPF 4.1.0-FP9, the attachDoc operations will not
    attach the document to the BPF Case when the work item no longer
    exists, locked by other , or in Delay Queue
    
    This is due to the fix in PJ40274, which will remove the
    document off the BPF Case in CE, if the associated work items
    can't be found.
    
    This is the DEBUG log for the attachDoc operation in FP9, which
    shows when attach the work item failed, it will also delete the
    Bp8Attachment object
    =======
    2013-05-21 15:17:15,469 ERROR operations.Bp8Operations - Work
    Object is null or it is tracker work object, or it is in Delay
    Queue
    2013-05-21 15:17:15,469 DEBUG operations.Bp8Operations -
    Deleting Bp8Attachment objects for Case ID=252034
    
    2013-05-21 15:17:15,562 DEBUG operations.Bp8Operations - No Case
    object found.
    2013-05-21 15:17:15,562 DEBUG operations.Bp8Operations -
    result[0]=0
    2013-05-21 15:17:15,562 DEBUG operations.Bp8Operations - leaving
    attachDoc
    =======
    
    How long has the problem been occurring (recent changes)? :
    Since BPF 4.1.0-FP9
    
    Does this occur on more than one station / server? : Y
    
    Is there a workaround? :N
    
    What is the impact to the customer/system? : Break their
    business logic as they do not expect the documents should be
    attached to the work items.  It was working like that before
    until FP 9
    
    Can the problem be replicated on an internal system?  Y
    By Who (L3, Support, etc..)
    
    
    Steps to Reproduce:
    1/ Using BPF_Operations::attachDoc operation in the Workflow map
    2/ For an existing BPF case, either move the associated work
    item to Delay map or terminate it
    3/ Process the work item through the attachDoc operation on the
    BPF Case in (2)
    
    Actual Results: The attachDoc operation will not attach the
    document to the BPF Case.  From the bp8operations.log, you will
    see that the attachment will be removed off the Case object when
    the work item can't be found or in Delay queue
    
    
    Expected Results: Should leave the document attached to the BPF
    Case
    
    Are there any similar or related Defects? If Y provide ECMDB #s
    PJ40274: BPF_OPERATIONS::ATTACHDOC CAN ATTACH DOCUMENTS TO CE
    CASE OBJECT BUT FAIL TO PE WORK ITEM IN DELAY QUEUE WITHOUT
    LOGGING ERRORS.
    
    What logs were collected and where are they located?
    bp8operations.log
    
    Configuration/Environment : BPF 4.1.0-FP9
    Server OS : Windows
    Client OS : Windows
    Database :
    Network:
    App Server : WebSphere
    Browser :
    Note if non US Language:
    Other Product Component Versions:
    
    Non Web Environment  Y or N
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * BPF Operations users                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Bp8Operations::AttachDoc will not attach document to the BPF *
    * Case if the associated work item does not exist or in the    *
    * Delay Queue.                                                 *
    ****************************************************************
    * 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

    PJ41299

  • 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-06-05

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

FileNet Business Process Framework

Software version:

4.1

Reference #:

PJ41299

Modified date:

2014-01-23

Translate my page

Machine Translation

Content navigation