IBM Support

JR55686: WHEN MODIFYING TASKS BY USING SERVICES, STALE TASK INFORMATION IS SAVED AFTER THE TASK CLOSES

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

  • When you model a heritage human service, you can start the task
    as user 1, reassign that task to user 2 by using the JavaScript
    API, and then model a postpone activity which introduces a
    transaction boundary. When the task is then resumed by the REST
    API and reassigned back to user 1 with the JavaScript API,  the
    task neither closes properly nor is it reassigned to the correct
    user. As a result, you experience other issues; for example, the
    autoflow feature fails because it cannot continue navigation
    with the correct user.
    

Local fix

Problem summary

  • The business process definition (BPD) engine does not consider
    any changes to the task context that services make. The task
    context is loaded only once in the beginning of the navigation
    and is then held until the navigation finishes. As a result,
    stale task information is written to the database, which causes
    numerous other problems.
    

Problem conclusion

  • A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.06
    that will cause IBM BPM to refresh the task context before
    writing back the final task state to make sure that the latest
    changes are taken into consideration.
    
    To determine whether the cumulative fix is available and
    download it if it is, complete the following steps on Fix
    Central:
    
    1. On the Select product tab, select WebSphere as the product
      group, IBM Business Process Manager with your edition from the
      WebSphere options, All as the installed version, and All as
      the platform, and then click Continue.
    
    2. In the Text field, enter "cumulative fix?, and click
      Continue.
    

Temporary fix

  • Not applicable.
    

Comments

APAR Information

  • APAR number

    JR55686

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-05

  • Closed date

    2016-05-27

  • Last modified date

    2016-05-27

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
27 May 2016