JR49687: UNABLE TO MOVE TOKEN IN V7511 WITHIN LINKED PROCESSES

7.5.1.2-WS-BPM-IFJR49687
Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• The v75x Info Center notes that move token will work for linked
  processes if the token is moved to a step within the linked BPD.
  However, there is a limitation in v75x that does not allow this.
  Since there are many customer's that are impacted by this
  limitation, we are backporting a v8000 feature that allows move
  token to work for linked processes.
  

Local fix

• n/a
  

Problem summary

• ERROR DESCRIPTION - The v75x Info Center notes that move token
  will work for linked
  processes if the token is moved to a step within the linked BPD.
  However, there is a limitation in v75x that does not allow this
  and the move token action will fail.
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM) Advanced
  IBM BPM Standard
  IBM BPM Express
  
  LOCAL FIX ? N/A
  
  PROBLEM SUMMARY ? According to the v7.5.x Info Center document
  for managing orphaned tokens
  (http://pic.dhe.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?top
  ic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Ftmanagingtokens.html),
  moving tokens to a target within the same process or linked
  process is valid.  However, a restriction exists where only
  tokens of the top level parent Business Process Diagram (BPD) is
  moveable.  This causes a major impact on applications which have
  been developed with multiple layers of sub processes. Users will
  not be able to move a token to a relatively recent event in the
  process and may have to move the token at the top level BPD
  which may cause a large amount of data to be lost.
  If the REST API move token feature is executed with a token and
  a target in a sub process or linked process, the following error
  will be seen in the response:
  "CWTBG0021E: The 'tokenId' path parameter was required but was
  not specified."
  

Problem conclusion

• PROBLEM CONCLUSION -
  The move token restriction has been a problematic issue for many
  customers as stuck or failed tasks are not able to be restarted
  at a later point in the process.  A feature in v8.0 was
  introduced to allow more flexibility to the move token function.
  This has been backported to v7.5.x to provide customers the
  freedom to move tokens to a suitable event where data lost can
  be minimized.
  
  A fix is available for IBM BPM v7.5.1.1
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR49687:
  1.Select IBM Business Process Manager with your edition from the
  product selector, the installed version to the fix pack level,
  and your platform, and then click Continue.
  2.Select APAR or SPR, enter JR49687, and click Continue.
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

• n/a
  

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

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R751 PSY

     UP