Designer/Mapping Issues

Mapping to Database Adapter is not supported in Compact Domain

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

Mapping a milestone to a database adapter (request or response) leads to errors at runtime if indicators have been assigned to the milestone. This issue is limited to a compact domain setup and does not happen in an expanded domain configuration.

Workaround

Either configure an expanded domain or follow the instructions below:

For request: Map the milestone to a BPEL assign activity before the invocation of the database adapter and extract indicator values from a BPEL variable available at this point. If no such assign activity exists, you need to create it.
For response: Map the milestone to a BPEL assign activity after the invocation of the database adapter and extract indicator values from a BPEL variable at this point. If no such assign activity exists that maps the necessary values (required indicator values) to a BPEL variable, you need to create it.

Oracle BPEL PM supports the use of activities with same names across multiple scopes. Mapping a milestone to such an activity may cause unexpected behavior and is not supported

Bug Number: 22937770

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

Activity names must be unique. If they are not unique, it may cause an unexpected behavior.

Oracle BPEL PM supports the use of variables with same names across multiple scopes. Defining extraction criteria for an indicator from such a variable may cause unexpected behavior and is not supported

Bug Number: 22244803

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

Variable names must be unique. If they are not unique, it may cause an unexpected behavior.

Only “On Entry” mapping supported for Throw/Rethrow Activities

Bug Number: 22644657

Impacted Releases: 12.2.1.3.0

Impacted Platforms: All

When mapping to throw/rethrow activities, only “On Entry” is supported. The throw/re-throw activities for the exit/completion criteria are not captured.