Article

(View Disclaimer)

When creating new request workflows with IDM Designer and using one of the default workflow forms, you will typically get a recipient selector field with the default Object Selector.

Sometimes you may want to replace this selector with a custom search.
In this example we will use IDM Designer to create a custom search that allows users to enter Given Name and/or Surname for their search; this search will only return users that do not have their 'Login Disabled' attribute set.

Click to view.

Here's how to proceed:

1. Open IDM Designer
2. In the 'Directory Abstraction Layer' (DAL) add a new query:

   * General
   Use the name 'queryUsers' and a display label of your choice
   Select "User" as Query Entity

   

   Click to view.

   * Parameters:
   Add 2 parameter references: 'paramSurname' and 'paramGivenName' with display labels of your choice

   

   Click to view.

   * Query Conditions
   Add a new Condition Grouping with 3 conditions

   				'Last Name' 		'starts with' 	'%paramSurname%'
   			and	'First Name' 		'starts with' 	'%paramSurname%'
   			and	'Login Disabled' 	'not equals' 	'true'
   
   

   

   Click to view.

   * Search
   Add the appropriate Search Root, Search Scope, and Max Entries

   

   Click to view.

3. Deploy the query

   We will use this query in our form to search for users that match the Surname and Given Name that we enter in the form.

   After saving your new Query, you may need to flush the Cache in administration tab of User Application

4. Create a new workflow (or open an existing workflow) of your choice.
5. Edit the Request Form and add 4 form fields:
   

   	* 'fldSurname' 		(Data type: string, Control Type: text)
   	* 'fldGivenName' 	(Data type: string, Control Type: text)
   	* 'fldSearchBtn' 	(Data type: string, Control Type: Html)
   	* 'fldMatches' 		(Data type: dn, Control Type: PickList)
   
   

   

   Click to view.

* For the 'fldSearchBtn' field add this line as 'HTML Content' (get the single and double quotes right)

'&nbsp;<input type=\"button\" name=\"btnSearch\" value=\"Search\" onclick=\"runQuery();\" />'



Click to view.

* For the 'fldMatches' field, use 'User' as Entity key and 'LastName, FirstName' as Display Expression

6. In the 'Script' tab of the form, add a new inline script with these lines

   var globalVars	= new Object();
   
   
   // called from form:onload to permanently remember some global vars
   function storeGlobalVars( IDVault, form )
   {
      globalVars.IDVault	= IDVault;
      globalVars.form		= form;
   }
   
   
   // called from custom HTML field to run the query
   function runQuery( )
   {
   	try
   	{
   		var SN = globalVars.form.getValue( "fldSurname" );
   		var GN = globalVars.form.getValue( "fldGivenName" );
   		if (( SN == undefined ) || ( SN == "" )) SN = "*";
   		if (( GN == undefined ) || ( GN == "" )) GN = "*";
   		// run the query and store the results into the "fldMatches" field
   		globalVars.IDVault.globalQuery( 
   			"fldMatches", 
   			"queryUsers", 
   			{"paramSurname":SN, "paramGivenName":GN })
   	}
   	catch ( e )
   	{
   		alert( "runQuery error: " + e );
   	}
   };
   

   

   Click to view.

7. In the 'Events' tab of the form, add a new onload script with this line

   	storeGlobalVars( IDVault, form );
   

   This will store the variables 'form' and 'IDVault' in a global form memory area to ensure that you can access them anytime.

   

   Click to view.

8. Deploy the form and test
   
   

   Click to view.

9. Adapt the procedure to your needs:

   Of course you may want to add other search fields and run a different query, but all you have to do is:

   • Add new text fields to your form
   • Modify the query object to reflect your query needs
   • modify the inline script to copy your field input into the query

Environment used:
Identity Manager Version 3.6.x/3.7.x
IDM Designer 3.5

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.