This chapter contains the following topic:
While working in JD Edwards EnterpriseOne, users can email other users a shortcut to an application or a form. More often, shortcuts are sent to recipients automatically as part of a JD Edwards EnterpriseOne workflow process. For example, a workflow process might automatically send a manager a shortcut to an approval application after a user enters a sales order. The recipient (in this example, the manager) double-clicks the shortcut to access the corresponding application.
If more than one server is dedicated to JD Edwards EnterpriseOne workflow tasks, you can configure to which server a shortcut is routed. When you configure the shortcut to access a server other than the default server, your changes are stored in the F986101 Object Configuration Master table. For multiple environments using different port numbers with the same HTML server, first create one record for each HTML/port combination in the Deployment Locations Application (P9654A). Then create the Environment/Service Configuration record for each user who would send shortcuts, specifying the HTML server and port. The user could be *public or individual users or roles. These mappings need to be defined for both System and Server map data sources, including "J" environments.
If a workflow process runs on the enterprise server, the system will first look for the HTML service mapping in the F986101 table. The F986110 table determines which HTML server to use for the shortcut URL, based on the environment and user. The system uses the information in F986101 to locate the HTML server parameters defined in the Deployment Locations Application (P9654A). These parameters include the protocol, hostname and domain name (defined in the Server URL field), and the port to use when constructing the shortcut URL. If the HTML service mapping is not set up, the system will use the primary HTML server specified on the Work With Locations and Machines form in P9654A. The HTML server Preference section of the enterprise server jde.ini file is not used.
If a workflow process runs on a Microsoft Windows client, the system will first look for the HTML service mapping in the F986101 table. If the mapping does not exist, it will look at the HTML server listed in the workstation jde.ini file. If no preference is specified, the system will use the primary HTML server specified on the Work With Locations and Machines form in the Deployment Locations Application (P9654A).
You might want to run a workflow process on the Microsoft Windows client if a user is developing a JD Edwards EnterpriseOne workflow process. The workflow process contains a shortcut to a new application that resides only on the user's workstation. The user wants to test the new application before making it available to everyone, so she wants the shortcut to access the new application located on her workstation. By default, the shortcut sent by the workflow process routes users to an HTML server, not to the user's workstation. You can configure JD Edwards EnterpriseOne to route shortcuts to the user's workstation by creating a record for the workstation in the Deployment Locations Application and the Environment/Service Configuration application.
Access Environment/Service Configuration (P986110).
Note:Before creating a record in P986110, verify that there is a record in the Deployment Locations Application (P9654A) for the HTML/port combination that you plan to configure for shortcuts. If the record does not exist, create one before proceeding with the shortcut configuration. See Defining Shortcut Links for further details.
Use the EntepriseOne menus to navigate to the Environment Management (GH9053) menu. Double-click Environment/Service Configuration (P986110). You cannot use the Fast Path to navigate to this application.
On the Work with Service Configuration form, verify that there is a record for the HTML server where you want the shortcut to point to.
If a record does not exist, click Add.
On the Service Configuration Revisions form, complete these fields:
The environment on which the user sending the shortcut is logged in.
The user who is sending the shortcut.
The logical server name of the web server on which the user sending the shortcut is logged in. You must enter a logical web server name rather than the physical server name.
The port number associated with the logical server.
Note:During an initial installation, the HTML server is set up with port 80. If your company does not use port 80 for the HTML server, you must delete the HTML server record and add it again with the correct port number.
Select the record in the grid.
From the Row menu, click Change Status to activate the service.
See Also: Deployment Server Installation in the JD Edwards EnterpriseOne Application Installation Guide.