JR64316: COPYING OR MOVING AN ARTIFACT FROM ONE PROJECT TO ANOTHER CREATES MULTIPLE VERSION DEPENDENCIES FROM THE SAME TOOLKIT

APAR status

• Closed as fixed if next.

Error description

• When you try to move an artifact from one project to another in
  Process Designer, it may create a toolkit snapshot dependency on
   a toolkit that already exists. As a result, you end up having
  multiple versions of dependencies on the same toolkit.
  

Local fix

• Open the project in desktop Process Designer and delete the
  toolkit dependency that was added as part of the copy or move.
  

Problem summary

• This issue occurs when you have an artifact that has a
  dependency on a toolkit snapshot that gets copied or moved to
  the target project. As a result, the target project might end up
   having dependencies on multiple versions from the same toolkit.
  Example:
  If you copy a process 'Process1' from Process app 'PA1' that has
  a dependency on a 'BO1' from toolkit 'A' snapshot 'S2' in track
  'dev' to Process App 'PA2' where 'PA2' already has a dependency
  on 'S1' from toolkit 'A' track 'main'. This results in 'PA2'
  ends up having dependencies on 'S1' and 'S2' from the same
  toolkit 'A'. Further, you can change the dependency of 'S2' from
  track 'dev' to 'S3' from track 'main' in desktop Process
  designer. Now, you have multiple dependencies on the toolkit
  from the same track.
  
  PRODUCT AFFECTED:
  IBM Business Automation Workflow
  IBM Cloud Pak for Business Automation
  

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