A System Administrator and Designer Tasks for Classic EnterpriseOne Pages

This appendix instructs you on how to add One View Reports and Portlets to EnterpriseOne Pages (also referred to as Classic Pages in EnterpriseOne Tools release that you create in an HTML editor. It also describes how to assign Kiosk mode to a JAS server.

This appendix contains the following topic:

A.1 Designer Tasks for EnterpriseOne Pages

This section contains the following topics:

A.1.1 Adding One View Reporting (OVRs) to EnterpriseOne Pages

To add OVRs to an EnterpriseOne Page (also referred to as Classic Page in EnterpriseOne Tools release

  1. In an HTML editor, open the EnterpriseOne home.html page to which you want to add an OVR.

  2. Use the following sample text strings and OVR ID and enter it in the HTML code:


  3. Save the EnterpriseOne Page.

  4. View the EnterpriseOne Page.


One View reports and the queries upon which they may be based are both user defined objects (UDOs). UDOs must be shared for other users to access them. Users must also have the appropriate permissions to view them.

For more information on approving and sharing UDOs, see the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide.

For more information on UDO security, see the JD Edwards EnterpriseOne Tools Security Administration Guide.

A.1.2 Adding Portlets to EnterpriseOne Pages

You can add portlets to EnterpriseOne Pages, though only Form Design Aid (FDA) portlets are supported. Portlets enable you to interact with an application without having the application open.

EnterpriseOne Pages are not intended to completely replace functionality found in an actual portal implementation such as WebCenter Spaces or WebSphere Portal. Form interconnects function differently in EnterpriseOne Pages. The initial EnterpriseOne portlet application and form that is displayed in the EnterpriseOne Page provides a launching mechanism with one-way communication into subsequent form interconnects. The EnterpriseOne Page support for EnterpriseOne portlet applications does not include returning data or other information back to the initial EnterpriseOne portlet application and form.

To add an FDA portlet to an EnterpriseOne Page:

  1. In an HTML editor, open the EnterpriseOne home.html page to which you want to add a portlet.

  2. In the HTML code, search for "/jde/E1PagePortlet?OID=.

    The graphic below shows an example of portlet values in an EnterpriseOne Page. These values are the ones you add to create your own portlets.

    Figure A-1 Portlet Values in EnterpriseOne Page

    Surrounding text describes Figure A-1 .


    You do not need to include a pUID number unless you have the same portlet on an EnterpriseOne Page more than once. The number provides distinction between the portlets. If you do not include a number and have two or more of the same portlets, when you change one portlet, the other portlet will reflect the changes as well.
  3. Save the EnterpriseOne Page.

  4. View the EnterpriseOne Page.


    EnterpriseOne Pages only support FDA portlets. If you have entered portlet values that are not supported, the following error message displays: Surrounding text describes portlet_error_message.png.

A.1.3 Understanding Embedded EnterpriseOne Pages

Embedded EnterpriseOne Pages enables users to work on multiple EnterpriseOne applications by simply switching to different EnterpriseOne Pages. Embedded Enterprise One Pages display as tabs located at the top of the EnterpriseOne interface. Applications launched from these EnterpriseOne Pages do not contain a Close button. Instead, users navigate away from the application by clicking other EnterpriseOne Pages located at the top of the screen. When a user navigates away from an application in an Embedded Page, EnterpriseOne saves any information they have already entered, so when they return, their information remains as they left it.

Use the following syntax to denote that the EnterpriseOne Page you are creating is an Embedded EnterpriseOne Page.

/jde/EmbeddedE1FormPageLaunch?OID=application information

With EnterpriseOne Tools release and the introduction of Page Composer, you must append the following to the end of each Embedded EnterpriseOne Page's URL:


You may also want to use Page Composer to create the embedded pages instead. See Composed EnterpriseOne Pages (Release in this guide.

The following list contains samples that support the Embedded EnterpriseOne Page:

  • /jde/EmbeddedE1FormPageLaunch?OID=P30200_W30200C_ZJDE0001&FindOnEntry=true&FormQueryId=NONE&FormDSTmpl=|8|9|10|11|15|&FormDSData=|60011| M30||3.0000|EA|&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P01012_W01012B_ZJDE0001&FindOnEntry=true&FormQueryId=0a192767-26d8-4f5d-9a98-ba55f9a5e5ce&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P0901_W0901H_ZJDE0001&FindOnEntry=true&FormQueryId=NONE&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P01012_W01012B_ZJDE0001&FindOnEntry=false&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P98MOQUE_W98MOQUEA&FindOnEntry=true&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P05PTLET_S05PTLETA&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P01012_W01012A_ZJDE0001&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P01012_W01012A_ZJDE0003&FindOnEntry=true&FormDSTmpl=|5|12|13|14|15|16|17|18|19|20|21|22|23|&FormDSData=||1||||||||||||&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P4210_W4210E_ZJDE0001&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=P982400_W982400A&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?OID=PMODAL_WMODALA&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?TaskId=3/G01&embededInCompositePage=true

  • /jde/EmbeddedE1FormPageLaunch?TaskId=1/G05BE1&embededInCompositePage=true

A.1.4 Kiosk Mode

Kiosk mode is a way to designate a JAS port so that all users on that port are running in Simplified Navigation mode, regardless of the User or Role Simplified setting.

To assign Kiosk mode to a JAS server:

  1. Access Server Manager.

  2. In the Configuration section, select the Advanced from the View menu.

  3. Locate the appropriate JAS.ini file, and change the Force KIOSK setting to True.