My Oracle Support Banner

E1: ORCH: Enhancement Request To Use Variables For Application Version In Message Service Request (Doc ID 2987625.1)

Last updated on JANUARY 03, 2024

Applies to:

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

Symptoms

For now it is not possible to softcode the version of an application link in the message service request.

Customer want to use the Message Service Request in orchestrations to send out messages via email.  These messages contain a link to specific E1 applications. Currently it is not possible to softcode (by using a variable) which version of the application to link to.  The version of an application link in the message service request, is always hardcoded (by selecting a specific version from the dropdown list).

Customer need to be able to softcode the version of the application in the application link.  Because the version of the application to use, can be data related (e.g. depending on the CO, version A or B needs to be triggered).  Another reason for softcoding the version, is that client might want to use their own defined versions instead of the standard delivered versions.

As it is possible to softcode the version of an application in the Form Service Request, customer would like that this be made available to softcode the version of an application when using application links in a Message Service Request.

Message Service Request:

 

When defining a version of the application (in the application link), it is only possible to select something from the dropdown list.  It is not possible to softcode, using a ${variable}:

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
Symptoms
Changes
Cause
Solution
References


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