Item still showing even with Global Restriction

Answer

The environment is configured with two Global Data Restrictions (Type = QUALIFIED) to prevent
users from being to access a particular item from both the Item Master
and the Inventory applications. These Global Data Restrictions are for
objects ITEM and INVENTORY, and each one has a null for the Application
field. These restrictions appear to be working well - you can't see
the restricted item in either the Item application or the Inventory application.

However, the item still shows on the Item tab of the Storerooms application even though the data on that screen comes from the Inventory object.

EXAMPLE STEPS TO REPLICATE:
1) Condition created in Conditional Expression Manager called HIDEITEM
type: expression
expression: :itemnum<>'D600'
Always Evaluate: checked

2) In Security Groups application Select Action menu select Global Data
Restrictions and create two global restrictions
- Ist restriction: Object: Inventory
Type Qualified
Reevaluate checked
Condition: HIDEITEM

- 2nd restriction - same as first global restriction except Object is
ITEM

3) Go to Item application and notice that Item D600 does not show in the
list (this is expected). Go to Inventory application and notice that
item D600 does not show in list (also expected). Next go to the
Storerooms application , select the Hardware storeroom and then click
on the Items tab. Item D600 does show up which is not expected since
the field is INVENTORY.ITEMNUM and the global restriction is expected
to apply.

ANSWER:
Qualified Data Restrictions are not applied to child objects or
attributes, as noted in the field help.

"Type of restriction being configured. Valid types are Hidden,
Required, Read-only and Qualified. Qualified means that only data
meeting the condition is 'qualified' to be fetched from the database
and can only be applied to top-level objects (not child objects or
attributes). "

The use case provided involves creating a Global Database Restriction
against Item and Inventory, type Qualified, with condition " :itemnum<>'D600' ".

To prevent visibility of unauthorized items in child table views, it is
recommended to create additional Global Database Restrictions of type
Hidden with an opposite condition, such as " :itemnum = 'D600' " or " :itemnum in ('D600' ,
......)"