Bookshelf Home | Contents | Index | PDF |
Siebel Finance Guide > Managing Product Group Visibility > About the Logic for Product Group VisibilityProduct group visibility can be set for an object in either of two modes, Confidential or Suppress. A user property set at the applet level determines the mode for an applet. The logic for Confidential mode objects is based on the value of the Public Flag field at the record level: For Suppress mode objects, a record is considered public if the creator's product group has its Suppress Flag unchecked. Otherwise the record is considered nonpublic. For each object, views with product group visibility are available. At the time of implementation, if customers want product group visibility for these objects, then they can enable or disable views based on view licensing and setting appropriate responsibilities to different users appropriately. Table 40 shows the list of views that are preconfigured with product group visibility. Read-Only and Editable ViewsThe main list views in the views shown in Table 40 are read-only while others are editable. This is because the applets of these views are based on intersection tables between Product Group and the corresponding object for performance purposes (for example, FINS Product Group's Opportunities view is based on the business component, FINS CI Opportunity, which is sitting on table S_OPTY_PGROUP). The new intersection table-based business components are FINS CI Opportunity, FINS CI Call Report, FINS CI Action and FINS CI Contact. The applets of these views have user property FINS PGV UseBaseTable set to N. These read-only views show only records that have the current user's Product Group associated. Sharing between Product Groups doesn't work on these views. Also, public records are not shown unless they have the current user's Product Group associated with them. Viewing a List of Primary Product Group MembersYou can view a list of primary product group members. To view a list of primary product group members Related Classes, Methods, and Business ServicesFor an applet that requires product group visibility, use the class CSSSWEFAFrameListPGVisibility, or CSSSWEFAFramePGVisibility for Form applets. This class, during the initialization of the applet, uses GetPGVisibilitySearchspec to get a searchspec string using the business service FINS Product Group Visibility Service. SetNamedSearch sets the searchspec in the business component of the applet. When Execute is invoked later, the records are filtered according to the visibility rules. Here are two examples of the searchspec returned by the business service for Opportunities:
Business ServiceThe business service FINS Product Group Visibility Service plays an important role in implementing the PGV functionality by generating the searchspec. BS Name: FINS Product Group Visibility Service Business Service MethodsThe Business Service method getting the searchspec is as follows: Method Name: getPGVisibilitySearchSpec Output: The searchspec string as value of the output propset. (key: "FINS PGV Confidential Flag" value: Y or N) (key: "FINS PGV Suppress Flag" value: N or Y) (key: "FINS PGV UseBaseTable" value: Y or N) (key: "FINS PGV UseMyPGRecordsOnly" value: Y or N) Another method of the Business Service is as follows: Method Name: getCurrentUserPublicFlag Output: Public Flag value (Y / N) in output property "FINS Product Group Visibility Public Flag" Customization and Extensibility OptionsApart from the preconfigured applets and views having product group visibility, customers can create new applets and views with product group visibility with either the Confidential mode or the Suppress mode. |
Siebel Finance Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |