How to use a before query business rule to hide records if certain catalog item

[Blair5]

I have a requirement to hide an RITM from one catalog request for everyone unless they are the submitter. Additionally, task needs to be hidden to everyone except users in a particular assignment group or the submitter. 

I was going down the ACL path, but since this is such a small use case, I'd rather use an on before query business rule. Any help appreciated!

[Ankur Bawiskar]

Hi Blair,

sample query BR below should do the trick

Table: sc_req_item

Condition: gs.getSession().isInteractive() && !gs.hasRole("admin")

Script:

Ensure you give the catalog item sys_id for which it should work

current.addEncodedQuery('cat_item=512d045a076f8010540bf2508c1ed0d4^sys_created_by=' + gs.getUserName());

Regards
Ankur

[ying zeng]

hi 

can you tell me how to create a before BR  to hide the record only if the login user is assignment group member pls..

[Jaspal Singh]

Hi Blair,

Getting business rule created would require more efforts than ACL as in Query business rule you need to esure it does not break existing functionality of visibility & works only for required item.

Better would be an ACL approach for Table level with script as below.

Script:

if(current.cat_item=="sys_id_of_catalog_item")
{
	if(current.request.requested_for==gs.getUserID()){
		answer=true;
	}
	else{
		answer=false;
	}
}

Somethig similar for Catalog tasks. But this will have ACL message of 'Security constraint....' which will relatively be only specific case for Query Business Rule

[Blair5]

What if there are already 5 table level read ACLs defined? Do each of those need to be updated to include this script?