Skip to main content

NetIQ IDM - How to close a workflow request based on a group membership (NetIQ Userapp workflow forms)


Solution:

Suppose you want to close a request form by cancelling it upon a certain condition, such as if the caller is requires to be member of a specific eDirectory group.

1. On the request form,  add a field called "recipient". i.e the caller of the form
2. Workflow->Start->Data-Item-Mapping, Add  "recipient" as the source expression
3. On the request form field "recipient", Properties add event "onload"
4  Paste the following script:


function CheckGroupAccess(userDN)
 {

 var isMember;

 var grp = IDVault.get(null,userDN,'user','group');

 var access_grp = "ACCESS_GROUP_DN";

access_grp = access_grp.toLowerCase();

var lvEnt = Array();

lvEnt = grp;

var EntSize = lvEnt.length-1;

  for (var i = 0; i <= EntSize; i++)
     {
        currentEnt=lvEnt[i].toString().toLowerCase();

if (currentEnt.match(access_grp))
{isMember="x";
  break ;}
  else
  continue;
  };

 return isMember;

 }


5. Add the following script on the same page below or above the previous one

try{



if (CheckGroupAccess(field.getValue()) != "x"){

  alert("You are not authorized for this form, closing request form");
       form.submit("CancelAction");
}
     // DEPENDS ON YOUR CHOICE
    //form.showMsg("Authorized ok, please proceed");

}catch(e){
 alert(e);
}

Comments

Maqsood Bhatti said…
I just added this code since the workflow default Trustee rights functionality never worked for me in any version. they should remove it or should call it something else like "Authenticated Users"

Popular posts from this blog

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...

NetIQ IDM - Strip unwanted group member values from current operation

This code example shows how to remove unwanted group members from current operation based on some business logic. Optimization group members add to avoid  "ALREADY_EXIST_VALUE" kind of errors. when IDM engine fails to do so. Here I am doing look up in AD for members, and for each added member from IDM if user is already member of AD group, i am just striping out current member value from the current operaiton. < do-set-local-variable name = "group-dn" scope = "policy" > < arg-string > < token-src-dn /> </ arg-string > </ do-set-local-variable > < do-set-local-variable name = "group-members" scope = "policy" > < arg-node-set > < token-dest-attr class-name = "Group" name = "Member" /> </ arg-node-set > </ do-set-local-variable > < do-trace-message > < arg-string ...

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands

Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy: < do-set-dest-attr-value direct = "true" name = "psexecute" > < arg-association > < token-resolve datastore = "src" > < arg-dn > < token-text xml:space = "preserve" > {userref} </ token-text > </ arg-dn > </ token-resolve > </ arg-association > < arg-value type = "string" > < token-local-variable name = "cmdlet" /> </ arg-value > </ do-set-dest-attr-value > < do-append-xml-element expression = "../modify[@direct]" na...