Last updated on DECEMBER 21, 2016
Applies to:Siebel CRM - Version 22.214.171.124.3 [IP2014] and later
Information in this document applies to any platform.
Constrain PickList on Applet "Query" Mode
Pick List on HLS Case that presents Account records. The Pick List is constrained by the following logic:
HLS Case.Primary Organisation Id = Account.Primary Organisation Id
When the user goes to pick an Account against a Case, the list of accounts is correctly constrained to show only those that have the same Primary Orgs.
HOWEVER, when the user enters query mode on the Case applet, users are able to invoke the Pick Applet again in order to choose an Account to use in their search criteria. In this situation, the list of Accounts is unconstrained. That is, users are able to see Accounts that belong to all Organizations - presumably because there is no relevant Case record on which to derive the constraint.
This, however, gives our users 'visibility' of data they should not be able to see, even though the result of the Case query are correct and won't return any records if a non-visible account is used in the search criteria.
When editing a Case record, the Account Pick List should be constrained by the Case Primary Org Id
When querying for a Case record, the Account Pick List should be constrained by the logged in user Primary Org Id
Is this possible?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms