REST Business Service Call Does Not Process Parameters With .(Dot) Characters When Executed Through A Workflow (Doc ID 2951580.1)

Last updated on JUNE 08, 2023

Applies to:

Symptoms

After implementing the steps in Workflow Process Invoking Outbound REST Is Not Able To Get Response Hierarchy Back Into A Process Property (Doc ID 2929142.1) in order to map the IO response into a Workflow Process Property for a REST Business Service, the parameters which contain a .(dot) character are not processed when calling the Workflow directly.

The same parameters are however processed correctly when calling the Business Service directly, outside of the Workflow context.

This can be reviewed in the restoutbound.log snippets from below:

Workflow non-working scenario

Notice how the query argument is different, with $.type, param.CurrentTarrifID and param.CurrentRateplanType parameters missing from the query argument in the Workflow case.

The issue can be reproduced via the following steps:

1. Implement the steps in Workflow Process Invoking Outbound REST Is Not Able To Get Response Hierarchy Back Into A Process Property (Doc ID 2929142.1).
2. Simulate the call through the workflow for which the steps in Workflow Process Invoking Outbound REST Is Not Able To Get Response Hierarchy Back Into A Process Property (Doc ID 2929142.1) had been configured with the Workflow Process Simulator.
3. Simulate a call directly for the Business Service with the params provided directly in the Client UI Business Simulator.
4. Notice the difference in behavior.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.