What is a View?
By user9156809 on Mar 25, 2009
What is a View?
A view is a collection of Attributes that come together from one or more objects that are managed by IDM. They are transient, dynamic and are not stored in the Repo. Basically think of it as a snapshot of Attributes. It can change depending on what your Workflow/Form is doing. You run into views primarily in Workflows and Forms.
So lets quickly explain a few things
A Form is a way of displaying the View graphically in a browser for editing. A form contains rules for changing the data in the views and tell the browser how to display the view attributes.
A Workflow are the logical steps, a sequence of actions and tasks that are performed consistantly according to a defined set of rules.
View Attributes are a collection of name/value pairs that get assembled from one or more objects stored in the repo or are read from the resources.
View Handlers are java classes that contain the logic to create the views and perform actions. These usually get kicked off by a workflow to perform more complex task such as approvals or provisioning.
Some views that are frequently used are Deprovision, User, Reconcile and many more.
The most important view is the user view. This contains the users attributes that are stored in IDM and attributes that are read from the accounts managed.
Checking out User Views:
To check out a view using the IDE
1. create a new project
2. Right click on the project
3. Go down to the IDM in the drop down and select check out view.
4. This will open a box, I choose user and my user Test (see image below)
To check out a view in the BPE
1. Make sure you have the WSHOME and JAVA_HOME environmental varibles set.
2. Run lh config , This will open up the BPE .
3. Once inside, Select file open View this will open a dialog box
4. Type in the view you want to check out (user), in the field name enter the name of the user, in my case it is user Test.
5. Click ok and it will be displayed in the right side.
I will be going into detail on the user view.
Again the User view is a collection of attributes that describe the user, these include attributes stored in IDM and also attributes it gets from the resources. This view gets called when you edit the user, create the user.
For instance, when you want to edit a user, you go to the accounts tab and choose user action and edit. This form is called the tabbed user form. This form launches a workflow that checks out the view. This workflow holds the view so that the workflow can manipulate the view before checking it back in and having the form display it back to the browser.
As you can see the view is used in conjunction with the forms.
In the view picture above, you can see some attributes in the user view. As you can see the attribute can be nested. I will talk about a few of these .
waveset - contains infomation that is stored in the Repo( the WSUser object). In here you can see that we have accountId so if you wanted to display this you would have to use waveset.accountId .
accounts - contains the values of all the resources accounts that are associated with this user. In here if you have more then one resource attached to the user you will see the attributes from those listed here. If the user is only in IDM then you will see Lighthouse.
accountInfo - This contains read-only information about the resources and accounts associated with the user.
global - this contain attributes that are syncronized across all resource accounts.
As you can see I can go into a lot more detail on the attributes and how to display and use them in your forms. I will save this for a later post. I hope you find this useful . Please send me comments and I will try to answer them as quickly as possible.