BROWSE-ONLY lookup does not work if it is using a parameter construct

Document ID : KB000105830
Last Modified Date : 03/08/2018
Show Technical Document Details
Issue:
BROWSE-ONLY of dynamic lookup does not work

STEPS TO REPRODUCE 

1. Create Dynamic Lookup. It includes Parameter like as below. 

SELECT 
@SELECT:RES.ID:ID@ 
,@SELECT:RES.FULL_NAME:FULL_NAME@ 
FROM 
SRM_RESOURCES RES 
WHERE 
@FILTER@ 
@BROWSE-ONLY: 
AND ((RES.IS_ACTIVE = 1) AND (@WHERE:PARAM:USER_DEF:INTEGER:N_FLG@ = 1)) 
:BROWSE-ONLY@ 

2. create custom object. 
a. create attribute. (n_flg) 
b.. create attribute. (sugsh02_test_lookup) 
c.. define View settings. (Layout Create) 
d.. define View settings. (Layout Edit) 

3. Access custom object list and create instance, and select some active user for multi value lookup field and save. 
4. Go to Resource page and make user who is selected by above step to Inactive. 
5. Go to custom_object page and view instance. 

Expected result: Inactive user who was selected before is appeared.       
Actual Result: Inactive user who was selected before is not appeared. The @BROWSE-ONLY@ works when selecting a value, but the DISPLAY for saved values seems to be using the @BROWSE@ logic when it should not.          

The field DISPLAY VALUE works as expected with the following query - BUT it does not have the dependent parameter construct at all
SELECT 
@SELECT:RES.ID:ID@ 
,@SELECT:RES.FULL_NAME:FULL_NAME@ 
FROM 
SRM_RESOURCES RES 
WHERE 
@FILTER@ 
@BROWSE-ONLY: 
AND RES.IS_ACTIVE = 1 
:BROWSE-ONLY@ 

If the query does not have @BROWSE-ONLY@ section, it works as expected to display all the saved values.  But then when selecting a value, the user would see all values for selection.
Environment:
PPM15.3
PPM15.4
Cause:
DE40581
Resolution:
Fixed in Future Version.