E1: ORCH: Token Input Provided When Calling an Orchestration is Not Used in the Subsequent Steps Resulting in Multiple User Sessions (Doc ID 3040433.1)

Last updated on AUGUST 08, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When calling an orchestration using a third-party, the inputs contain a token input along with the other required inputs for the orchestration. Even though the token is provided as an input to the orchestration, it is not being used in the subsequent steps in the orchestration. The steps use a different token which results in multiple user sessions.

Changes

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

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

E1: ORCH: Token Input Provided When Calling an Orchestration is Not Used in the Subsequent Steps Resulting in Multiple User Sessions (Doc ID 3040433.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!