IBM Support

JR44836: ENABLE TRIGGERING OF API EVENT HANDLER EVENTS FOR PARALLEL SUBTASKS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Some of the API event like postComplete will not be triggered
    while using Parallel SubTasks
    

Local fix

  • N/A
    

Problem summary

  • Problem Description:
    Enable triggering of all API Event Handler methods for tasks
    with parallel ownership.
    
    Problem Summary:
    Tasks with parallel ownership is an convenient way to create
    multiple identical tasks for scenarios like voting. Without
    this feature, client applications would need to use API calls to
    enable such scenarios. If using API calls, an API Event
    Handler would be invoked for each interaction. If tasks with
    parallel ownership are used, the interaction to create sub
    tasks, complete or terminate tasks is done internally. This does
    not trigger API Event Handlers.
    For certain scenarios, e.g. to keep a customer task table in
    sync with human tasks in the system, the current situation
    is not sufficient. They need API Event Handler calls to capture
    task changes.
    
    Problem Conclusion:
    After installing this interim fix, the customer might enable to
    get triggered for each interaction which happens for
    tasks with parallel ownership.
    To not change the behavior for current customers which might use
    the current limited set of API Event Handler triggers
    for their solution, this interim fix's changes need to be
    enabled:
    Create a human task manager custom property with name
    'APIEventHandler.AllEvents4ParallelRouting' and value 'true'.
    For a description how to create, modify or delete human task
    manager custom properties, please refer to:
    http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/c
    om.ibm.websphere.wbpmhelp.doc/com.ibm.ws.console.bpc.humantaskma
    nager/bpc_taskcustomproperties.html
    

Problem conclusion

  • Problem will be fixed with V8011
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44836

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-20

  • Closed date

    2013-01-10

  • Last modified date

    2013-01-10

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

    IV30442

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

Fix information

  • Fixed component name

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021