Bookshelf v7.5: Overriding the Popup Visibility

If the Popup Visibility Type setting is not sufficiently restrictive (for example, All visibility), this can lead to a large number of records being extracted when the picklist is processed during synchronization. Making the Popup Visibility Type more restrictive reduces the number of records extracted for picklists. The OverridePopupVisibility user property for an applet overrides the Popup Visibility Type on a business component. Use this property when the desired visibility differs from the business component's Popup Visibility Type, and you do not want to change the Popup Visibility Type. If several picklists use the same business component, you can also use the OverridePopupVisibility user property to vary the visibility of the picklists in the different applets.

There are two considerations you should keep in mind if multiple applications are sharing the same repository. First, changing the Popup Visibility Type has a global effect for all instances where the business component is used. If multiple applications share the same repository and use the same business components, changing the Popup Visibility Type for a common business component could have an undesirable effect for another application. Second, if multiple applications share the same applet, the picklist in each applet shares the same visibility as defined by OverridePopupVisibility property. This is because the OverridePopupVisibility property is set on the containing applet.

In Siebel Tools, go to Applet > Applet User Properties, and define the OverridePopupVisibility user property on the applet containing the control that opens the pick applet. See Table 10 for a description of the syntax. Assign a value to this property using the syntax shown, where <buscomp field n> is the underlying business component field of an applet control or column, and <visibility type> is the code corresponding to the desired visibility of the picklist's business component. (See Table 9 for a list of the visibility codes.) Because the name of the OverridePopupVisibility parameter must be unique, append a unique number to the name of the parameter for any other picklists, for example, OverridePopupVisibility1, OverridePopupVisibility2, and so on.

Table 10. OverridePopupVisibility Syntax
Name	Value
OverridePopupVisibility	<buscomp field 1>, <visibility type>
OverridePopupVisibility1	<buscomp field 2>, <visibility type>
OverridePopupVisibility<n>	<buscomp field n + 1>, <visibility type>

NOTE: If OverridePopupVisibility is used, then the picklist and pick applet search specifications are ignored during synchronization when the records for the picklist are extracted.