Skip to main content

NetIQ IDM - How to validate form field based on the Regular Expression (validation mask) in NetIQ Userapp workflow forms


Workflow forms in the  NetIQ Userapp provides to validate input fields using regular expression.

Here is the recipe:

Example allow only alphabets and spaces in the form field.

1. On the form field, Add regular expression validation mask:

^[a-zA-Z ]*$

2. On the form field, Add event (OnChange)

3. Add following code on the Event handler:


/*
Function to validate with mask (default) and set new
message if not valid returns true if field valid, else false
*/

function validateField() {
// check if field is valid, by calling default validation,
//which uses the mask

if (field.validate()) {
// not valid
form.clearMessages(); // get rid of the default
// validation mask message

form.showError("The entry " + field.getValue() + " is " +
"not valid");
return false; // field not valid
} else {
// valid, clear old messages
form.clearMessages();
return true; // field is valid
}
};

if (field.getValue() != ""){
validateField();
}

Comments

Popular posts from this blog

My own developed - Active Directory Cache Inspector for AD Driver Novell Identity manager

Sometimes there is a need for us (Consultants) to see a snapshot of all the changes that happened on the Active directory side while the Novell AD IDM driver was stopped or was not running, before we decide to start the AD driver. Since Novell Identity Manager currently allows us to see all the events which happened in the Identity vault only, but not on the AD side, I decided to write such a tool myself, and of course wanted to share this tool with the consultants/community out there. It's a .NET 2.0 WinForm application, written in C# programming language. To run this tool you should have at minimum: .NET 2.0 framework installed, ( Not supported on the Linux platforms yet) This application must be run under the same user which is configured on the AD driver. Short Tutorial (How To): When you run the application (ADCView.exe), the application automatically discovers the current domain, a domain controller, and default domain naming context in the user logged in domain automatically

NetIQ IDM - How to read Component type data from Query nodeset done from command transformation

Suppose query: <do-set-local-variable name="local.sub.ctp.QueryContacts" scope="policy"> <arg-node-set> <token-query class-name="User" scope="entry"> <arg-match-attr name="UPN"> <arg-value type="string"> <token-src-attr class-name="User" name="UPN"/> </arg-value> </arg-match-attr> <arg-match-attr name="contacts"> <arg-value type="string"> <token-text xml:space="preserve">get-contacts</token-text> </arg-value> </arg-match-attr> <arg-match-attr name="userid"> <arg-value type="string"> <token-association/> </arg-value> </arg-match-attr> </token-query> </arg-node-set> </do-set-local-variable> Outpu