HowTo: Use Resource Request Portlets to add Navigation Items to User Application in IDM 4.0x - Walkthrough

You can use the IDM "Resource Request Portlets" to add your custom workflow request definitions as new navigation items in the main UserApp menu.

The result would allow quick access to any custom workflows directly from the left navigation menu.


211 Resource Request Portlet Page

The example shows a custom workflow "Clearing Process" link in the "Information Management" menu on the "Identity Self Service" tab.

This feature is around in User Application for a couple of years now, but it seems that it is still unknown to many customers.

So, lets start a step-by-step walk-through to get you going.


  • Login as uaadmin (or other provisioning admin).

  • Select Tab "Administration".

  • Expand the IDMProv node under Portlet Applications

101 Resource Request Portlet


102 Resource Request Portlet

  • Click on the "Resource Request" Application (not on its leaf node)


  • Enter a custom name for your new request portlet

  • Click "Register"

103 Resource Request Portlet


104 Resource Request Portlet

  • The new portlet shows as another leaf node under "Resource Request".

  • Click on it to continue.


  • Select the most appropriate categories.

  • Save Categories

105 Resource Request Portlet


106 Resource Request Portlet

  • Under tab "Settings" you may localize the display name of your request portlet.


  • Scroll down to define some custom settings.

  • Start with settings like

    • Requires Authentication: true

  • Display Title Bar: true

  • Keeping the other flags on "false"

  • Save Settings

107 Resource Request Portlet


108 Resource Request Portlet

  • Under tab "Preferences" click on "View/Edit Custom Preference"


  • Click "Continue"

109 Resource Request Portlet


110 Resource Request Portlet

  • From the drop down list, choose your custom workflow (Provisioning Request Definition)

  • Submit


  • Do not forget to click on "Save Preferences" before returning

111 Resource Request Portlet


113 Resource Request Portlet

  • Find and add trustees (containers/users/groups) that you want to access the your custom portlet.

  • Leave the box "List Permission Set to Admin Only" unchecked

  • Save


Now you have created your first Resource Request Portlet.

The next steps let you configure, where to display your portlet.

You will create a new page and add it to the navigation menu.


201 Resource Request Portlet Page

  • Under tab "Administration"/"Page Admin": click on the "New" icon in the "Page Actions" area.


For convenience, we assign the same name to the page that we also used for our portlet - here "Clearing Process".

  • Choose a name that best represents your provision request.

  • Select the appropriate categories.

  • Click Save Page

202 Resource Request Portlet Page


203 Resource Request Portlet Page

  • In multi-locale environments click on "localize" and enter the approriate translations.

  • Save.

204 Resource Request Portlet Page


Now you have a portlet and you have a page.
The next step lets you add your custom portlet to your custom page.

  • Click on "Select Content" in the "Page Tasks" area.

205 Resource Request Portlet Page


206 Resource Request Portlet Page

  • Locate and add your custom portlet to your custom page

  • Click "Save Contents"


To define who is allowed to use your custom page, assign the respective trustees.

  • Click "Assign Permissions"

207 Resource Request Portlet Page


210 Resource Request Portlet Page

  • Find and add trustees (containers/users/groups) that you want to access the your custom page.

  • Leave the box "View Permission Set to Admin Only" unchecked

  • Save


211 Resource Request Portlet Page

Notes, drawbacks, and caveats:

  • Using a Resource Request Portlet may save your users from the sometimes annoying task of finding a request definition in the dashboard and may save them a couple of clicks.

  • You may use the feature to copy the most frequently used PRDs to a prominent place in the User Application GUI.

  • The result page that usually shows up after submitting your PRD from the dashboard may be missing. Users may be confused if their submission was successful or not.

  • You may set the new page as default page. When doing so, the request form may directly re-open after your last request was submitted. This could be desired in some environments, but irritating in others.




How To-Best Practice
Comment List