Including Configurable History in a Custom Application

This simplest way to use the History page in an application is to use one of the command objects installed with the framework.

  1. Assign the command object (AEFHistory or AEFHistoryAllVersions) to the appropriate menu object.

    For example, to use the AEFHistory object, assign it to the menu object that represents the tree you want to add the History category to. To use the AEFHistoryAllVersions objects, assign the object to the menu object for the toolbar item.

  2. To configure your own History command object:

    1. In the href parameter of the administrative command object that will call the History page, enter the emxHistory.jsp, plus the needed parameters (see Parameters Used by emxHistory.jsp) and a path indicator

      For example: 

      ${COMMON_DIR}/
emxHistory.jsp?HistoryMode=AllRevisions&Header=emxFrameworkStri
ngResource.Common.HistoryPageHeading&subHeader=Version&preFilte
r=emxEngineeringCentral.history.preFilterList&SuiteKey=eService
SuiteEngineeringCentral

      ${COMMON_DIR}/
emxHistory.jsp?HistoryMode=CurrentRevision&Header=$<type> 
$<name> 
$<revision>&subHeader=Revision&ShowFilterAction=true&ShowFilter
TextBox=false&preFIlter=connect,disconnect,promote

    2. To configure a toolbar item that opens the History page in a popup window, enter these settings:


      • Target Location=popup
      • Row Select=none
      • Registered Suite=Framework

    3. To configure a tree category that opens the History page in the content frame, enter these settings:


      • Target Location=content
      • Image=IMAGE_FILENAME
      • Registered Suite=Framework

    4. Connect the command object to the menu administrative object that will contain it. For example, if the command object is for a toolbar item, connect the command to the menu object for the Actions menu. If it is a tree category, connect it to the menu object for the tree.