Configure button is missing from iManager 2.5

  • 7006122
  • 25-May-2010
  • 26-Apr-2012

Environment

iManager 2.5

Situation

Configure button is missing from iManager 2.5

Resolution

The file with the Views setting is done per object and stored in the following path:

/tomcat/4/webapps/nps/web-inf/config/NDS<TREE>-<OBJECT>/fwViewAdmin.xml

To clear the assignment for an object just delete the object's folder.
Because the setting on the Admin user was being overridden by the object's parent container's setting you can delete the "Read parent containers of this object" checkbox from the fwViewAdmin.xml file for that user which will allow that user's settings to take priority.  To do so open the fwViewAdmin.xml file in that object's directory and delete the following section:

<setting>
<name><![CDATA[ReadParentObjects]]></name>
<value><![CDATA[1]]></value>
</setting>

Once that is done save, log out and back in and the Configure (or other) button should be there again.
A third option is to clear the View assignment on the parent container by changing the following section:

<setting>
<name><![CDATA[iManagerView:fw.ConfigureView]]></name>
<value><![CDATA[1]]></value>
</setting>

Change the section <![CDATA[1]> to <![CDATA[0]> (changing the 1 to a 0).  Save, logout and back in and the icon should be back again.

Additional Information

Set views for the Admin's container to "Hide" the Configure button (iManager: Configure: Views: iManager Views).

Set view for Admin object explicitly but had set the "Read parent containers of this object" which overrode the settings by getting them from the parent container.
In the fwViewAdmin.xml file should be a setting for each icon that is explicitly configured.  Be sure if you mean to change the ConfigureView that you do not change the Favorites or some other view.  For this reason the first solution, though the most "destructive" initially, is probably the most-sure solution to work.
These solutions do not require a restart of Tomcat but, if the user is logged in, they will need to log out and back in to see the change (Apache does not ever need to be restarted for an iManager change unless one of Apache's configuration files is changed such as httpd.conf).
Formerly known as TID# 10098455
Formerly known as TID# NOVL102961