Understanding Menu Group Importing

The Menu Import Application Engine process (PORTAL_MENU) imports menu groups from the menu definition into a portal registry.

Important:

Only system administrators should perform this process. If the user does not have security to the menus and pages, just a folder titled Label gets created.

The process creates folders and content references that reflect the menu definition hierarchy. This table shows the folder hierarchy that is imported:

Level	Menu Item
Folder level one	Menu group
Folder level two	Menu name
Folder level three	Bar name
Content reference	Component name

Note:

Use the Menu Import process to migrate custom menus only. The navigational menus that are delivered with your PeopleSoft application have already been added to the appropriate portal registry. The Menu Import process has no effect on components that are already registered. However, you can use the process to pick up additional components that are not delivered with the PeopleSoft system.

Before you use the Menu Import process, note these points:

• Object names that are assigned by the Menu Import process are autogenerated.

  If a folder name or content reference name already exists, the system appends a number to the generated object name. Consequently, you may have folder object names such as USE, USE1, USE2, and USE3. As a result, use the registration wizard if you plan to copy the application database registry structures into PeopleSoft Interaction Hub. When you use the registration wizard, you can control the object naming, and you can ensure the uniqueness of object names across databases.

• If a component resides in multiple menus, the process creates a separate content reference for each menu and component combination.

• The navigation hierarchy created by the Menu Import process does not match the delivered PeopleSoft hierarchy.

  To keep the navigation consistent, consider putting all custom menus into a common menu group and generating the registry structures for that menu group. Then, once the registry structures are generated, manually move the content references to an appropriate folder in the existing navigation hierarchy.

  To create a common menu group, open the custom menu in PeopleSoft Application Designer. On the Use tab of the Menu properties dialog box, enter a unique name in the Menu Group field. After you save the menu, it is available for other menus to use.

Using the Menu Import Process with PeopleSoft Interaction Hub

If you run the Menu Import process against multiple application databases and merge multiple registries into PeopleSoft Interaction Hub, bar names (level-three folders) can be overwritten because they frequently have duplicate names. The last folder that is copied takes precedence over all previous folders.

The autogenerated object names are based upon the current database portal registry. The Menu Import process cannot check external databases for existing object names, but it does check the current database.

If you run this process on different databases, the different databases may likely contain identical folder or content reference object names that refer to different objects. This can become problematic if you decide to copy these portal registry structures into PeopleSoft Interaction Hub. The same-named objects overwrite each other. You might need to delete the generated folders and content references to make them unique in the future.

Use the registration wizard to register menus and components into the portal registry. Although with the registration wizard you must register items one by one, you can control folder and object names at the time of the import.

See Application Designer Developer’s Guide: Understanding the Registration Wizard.