Soft Coding Reference (Release 9.2.5.3)

For Soft Coding Reference applications, additional information such as language could be passed to the external application to localize the web applications to match the EnterpriseOne preferences.

The value in the External Application Type field points to a record in the soft coding table.

You use the Add Soft Coding Record form to add a new soft coding record to define the external application. The Soft Coding Records application is P954000.

Access the Soft Coding Record form (P954000) and enter the appropriate information in the following fields:

See Working with Softcoding.

User/Role

Enter your JD Edwards EnterpriseOne user ID and role (such as *Public).

Environment Name

Enter the name of the JD Edwards EnterpriseOne environment in which you are working.

Template Name

Leave this blank.

Record Type

Select the record type as External Form.

SoftCoding Key

Enter a unique key specific to the project. Make sure that this Soft Coding Key matches the value in the External Application Name field in the Form Design Aid (FDA). This record is defined for a specific user and an environment.

The user in the soft coding table follows the user|role hierarchy, where the user level data is retrieved, then roles is retrieved if user data is not found, and at last *PUBLIC is retrieved.

The softcoding key is a way to tie together user and environment for a given external application.

SoftCoding Description

Enter a valid description of the record.

SoftCoding Value

Define the parameters that you want to pass to the external application. The values can be EnterpriseOne properties, variables, and hard-coded values. These values are fetched during runtime and the system builds the URL with these values when you launch the external application.

Refer to the example template at the end of this section and enter the following values in the tags:

EndPoint: Enter the full path to the external application in the <endpoint> tag. This is a required value.

Type: Enter the type. The value for the <type> tag can be VBCS or URL. This is a required value.

Custom Parameters: Define custom parameters in the <customParams> tag. There are 4 elements in each <customParam> tag:<isE1>, <e1Property>, <paramValue> and <paramVariable>.

EnterpriseOne Property: The supported types for the <e1Property> tag are: FI, PO (Release 9.2.5.4), PROFILE, AIS, and JAS. Here, FI, PO (Release 9.2.5.4), and PROFILE are generated as JSON objects. In order to pass E1 Property, set <isE1> to true.

The system passes AIS and JAS to VBCS type application by default.

EnterpriseOne Variable: When <isE1> is set to false, FI<ID in the form data structure>, PO<ID in the PO data structure> (Release 9.2.5.4), AIS, JAS, userName, userId, userLongId, addressNumber, userLang, environment, role, userLocale, dateFormat, dateSeparator, and decimalFormat can be defined in the <paramVariable> tag.

Note:

The <paramName> tag should be defined in all the <customParam> tags. The value in the <paramName> tag should match the value that the external application retrieves from the http request. For example, if an external application reads “userLanguage” from the request, then “userLanguage” must be set in <paramName>.

Hard-coded Values: You can also use the hard-coded parameter values in the template.

Example Template: PROFILE

  
<external>     
<endpoint>full path to the external application</endpoint>
<type>VBCS</type>
<customParams>
 <customParam>
 <isE1>true</isE1>
 <e1Property>PROFILE</e1Property>
<paramName>userProfile</paramName>
 </customParam>
 <customParam>
  <isE1>false</isE1>
<paramName>orderNumber</paramName>
<paramValue></paramValue>
<paramVariable>FI4</paramVariable>
</customParam>
<customParam>
<isE1>false</isE1>
<paramName>docNumber</paramName>
 <paramValue></paramValue>
<paramVariable>PO4</paramVariable>
</customParam>
<customParam>
<isE1>false</isE1>
<paramName>language</paramName>
 <paramValue></paramValue>
<paramVariable>userLang</paramVariable>
</customParam>
<customParam>
<isE1>false</isE1>
<paramName>extraParam</paramName>
<paramValue>embededMode</paramValue>
<paramVariable></paramVariable>
</customParam>
 </customParams>
</external>

Example Template: AIS Services

If a URL type of Soft Coding Record external form needs to call the AIS services, enter the AIS and JAS values for <e1Property> as shown in the following example:

<external>
<endpoint>full path to the external application</endpoint>
<type>URL</type>
<customParams>
<customParam>
<isE1>true</isE1>
<e1Property>AIS</e1Property>
<paramName>aisToken</paramName>
</customParam>
<customParam>
<isE1>true</isE1>
<e1Property>JAS</e1Property>
<paramName>deviceName</paramName>
</customParam>
</customParams>
</external>