IBM Support

JR48017: CANNOT DELETE SPECIFIC TOKEN VIA REST API

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • WHEN DELETING TOKEN FROM A STEP WHERE MULTIPLE TOKENS EXISTS,
    ALL TOKENS GET DELETED EVEN WHEN A UNIQUE TOKEN ID IS SPECIFIED.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users utilizing REST API move token or      *
    *                  delete token functions to manage Process    *
    *                  Instance tokens.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: All tokens are removed if multiple      *
    *                      tokens exists on a step.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When calling REST API to move / delete a token, if more than
    one tokens exist on a single step, all tokens within that step
    are removed even when when a tokenId is specified.  Examples
    of the affected APIs are :
    "/rest/bpm/wle/v1/process/instance_ID?action=moveToken&tokenId=
    <token_ID>&target=target_step_ID" and
    "/rest/bpm/wle/v1/process/instance_ID?action=deleteToken&tokenId
    =token_ID"
    When issuing a moveToken command, the underlying logic will
    copy the token to the specified target step and then execute a
    deleteToken to remove from the current step. Consequently, the
    moveToken API is also affected by this issue.
    Currently it is not possible to move/delete a specific token
    from a step without affecting the other tokens.
    Due to the complexity and amount of design change required to
    resolve this issue, the fix will be implemented into the next
    release. Once this fix has been released successfully
    into the next release, then back-porting this fix may be
    considered if necessary.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR48017

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-08

  • Closed date

    2013-10-28

  • Last modified date

    2013-10-28

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

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

Fix information

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
28 October 2013