JR48017: CANNOT DELETE SPECIFIC TOKEN VIA REST API

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 1 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products

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 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