Compartilhar via

QuickSheet: How to create a custom view of resources in FIM 2010

  • Artigo

This blog entry is to intended to act as a quick checklist or roadmap for those experienced in FIM 2010 to implement custom views (i.e. search scopes) of custom resource types and/or subsets of default resource types (e.g. Person). This entry will not cover creating custom resource types, but only how to make them available for display to Portal users, or a subset of them (e.g. Administrators).

Step 1: Create a search scope that defines the set (subset of resource objects that you wish to display. Ensure that that you supply a useage keyword that represents the set of users whom you wish to allow to use this search scope. (e.g. Accounting)

Step 2: Create a set that contains the  created search result scope (e.g. All Accounting Search Scopes). Although manual membership is an option, the recommended practice is to create to implement a criteria based membership based off of the value of the search scope's keyword provided in the previous step (e.g. Accounting).

Step 3:: If you wish to display the search scope results via a Navigation Bar, create an Navigation Bar  resource that will display the results of the created search scope. For the navigation URL, use the following syntax

 ~/IdentityManagement/aspx/customized/CustomizedObjects.aspx?type=RESOURCE_NAME

 &searchtype=EXACT_GUID_OF_THE_SEARCH_SCOPE

  

 Ensure that you have provided a useage keyword that matches the one used in the search scope (i.e. Accounting)

Step 4: Create a set that contains the created navigation bar resources (e.g. All Accounting Navigation Bar Resources). Although manual membership is an option, the recommended practice is to create to implement a criteria based membership based off of the value of the search scope's keyword provided in the previous step (e.g. Accounting).

Step 5:: If you wish to display the search scope results via a homepage reseources, create an homepage resource that will display the results of the created search scope. For the navigation URL, use the following syntax

 ~/IdentityManagement/aspx/customized/CustomizedObjects.aspx?type=RESOURCE_NAME

 &searchtype=EXACT_GUID_OF_THE_SEARCH_SCOPE

  

 Ensure that you have provided a Usage keyword that matches the one used in the search scope (i.e. Accounting)

Step 6: Create a set that contains the  created homepage resource  (e.g. All Accounting HomePage Resources). Although manual membership is an option, the recommended practice is to create to implement a criteria based membership based off of the value of the search scope's keyword provided in the previous step (e.g. Accounting).

Step 7: Create a set that ties all all the search scope and any homepage and navigation bar resources together (e.g. All Account UI Resources). Again, although manual membership is an option, the recommended practice is to create to implement a criteria based membership based off of the value of the search scope's keyword provided in the previous step (e.g. Accounting).

Step 8: Create a request-based MPR (e.g. All Accountants can read Account UI Resources) that grants permissions (i.e. check the grants permission box) to the desired set of users (e.g. All Accountants) to read (i.e. check the read resource permission checkbox) the set that contains all your UI resources (i.e. All Account UI Resources)

Step 9: Perform an IISRESET on your portal server. DONT FORGET THIS STEP

Comments

  • Anonymous
    May 25, 2012
    Thanks, Erich!  Very helpful.

  • Anonymous
    July 31, 2014
    Although this is an old post, in case anyone else tries this and fails: Be aware that you need to add the (system)name of your custom object to the list of usagekeywords! I just spend two hours to figure out, why my search scope is not showing up ;)