Welcome!

Identity Management Tips, Thoughts and Opinions

Matthew Pollicove

Subscribe to Matthew Pollicove : eMailAlertsEmail Alerts
Get Matthew Pollicove via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: SAP B1, SAP4SME

Blog Feed Post

Linking Pulldown Attributes in NW IDM 7.1

Use of the FIELD Attribute Prefix

One of the coolest things about NetWeaver Identity Manager is that there are always new tricks to learn. The development team keeps finding new and interesting ways to extend the functionality of the product. This, in turn, allows us to further extend what we can offer to our customers. Sometimes what I learn for a particular customer is brand-new, sometimes it's functionality that's been around for years, but either way, it's usually of use to someone, so I like to share when I can.

Recently I was asked by a client how we could link two fields together so that for a given value chosen in the first field via a pull down box would result in a specific subset of values being available in the second pull-down.

After a bit of research and some emailing I found that the use of the FIELD attribute prefix was the way to go. Here's how it all works:

In your database, create a table called LOCATIONS

The database should be populated with two columns called COUNTRY and CITY as shown below:

United States New York
United States Atlanta
United States Los Angeles
Norway Oslo
Norway Trondheim
United Kingdom London
United Kingdom Liverpool

Spain Madrid
Spain Barcelona

In NetWeaver Identity Management, create two attributes called COUNTRY and CITY. Set the Displayname and tool-tip in the Presentation tab as you would like but make sure presentation is set to SingleSelect.

Next go to the Attribute values tab and set up the SQL Queries as follows:

COUNTRY: select distinct COUNTRY from LOCATIONS (We want to use distinct so we don't see duplicate entries when we use the pull-down)

CITY: select CITY from COUNTRY where COUNTRY = %FIELD.COUNTRY%

Now add these attributes to a task and make sure they are added to the screen in the attributes tab so that we can see them from the Web UI.

Basically what's going on here is that we now compare the first value we enter, that of the country to the table itself and then presents a list of cities that result from the match. Locations are an easy example, but I can also see a use in listing business units and departments or anything where you have a long list and want to be able to just look at sub-sets.

There you go! Have fun with this... Wondering what other customizations have people been making? How do you extend the interface?

Read the original blog entry...

More Stories By Matthew Pollicove

Matt Pollicove is an Identity Management architect, engineer, trainer, project manager, author and blogger with experience in user account provisioning, data synchronization, virtual directory and password management solutions. As a MaXware Technical Consultant and later as a System Engineer, he worked extensively with MaXware (now SAP) software products in large customer environments. In the past Matt has worked with several leading national and international consulting firms and is currently a Sr. Principal Consultant for Commercium Technologies. He is currently the Practice Lead for SAP NetWeaver Identity Management and SailPoint IIQ.