Business process editor Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
   2.1 Calling a human task from a business process where the interface has multiple operations
3.0 Known problems and workarounds
   3.1 Keep business process artifact names short to avoid deployment failures

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphereR Integration Developer business process editor.

2.0 Limitations

2.1 Calling a human task from a business process where the interface has multiple operations

When creating a human task from a business process (such as from the Human Task Properties page of a receive activity, for example), if you select an interface with multiple operations, you are not given the opportunity to select which operation should be implemented by the human task. An arbitrary operation is automatically selected.

There is currently no workaround other than to ensure that human tasks called from business processes use interfaces with only a single operation.

3.0 Known problems and workarounds

3.1 Keep business process artifact names short to avoid deployment failures

To avoid deployment failures on Windows operating systems when exceeding the Windows® path length limitation, it is recommended to keep your BPEL artifact names short. Encountering the Windows path length limitation is also impacted by the directory you installed WebSphere® Integration Developer to. The longer the directory name, the shorter the artifact name should be.  

As an example, if you install to a directory length of 10 characters (for example, C:\WID6010), having artifact names that do not exceed 30 characters should avoid deployment failures on Windows machines.