mysterious-rose-44236
10/25/2021, 1:57 PMproducts:org=1#list@(groups:organization1#members)
products:org=1,dep=1#list@(groups:department1#members)
products:org=1,dep=2#list@(groups:department2#members)
products:org=1,dep=1#list@(products:org=1#list)
products:org=1,dep=2#list@(products:org=1#list)
groups:department1#members@john
groups:organization1#members@jane
This way, John can only list products from his own department whereas Jane can list products from both department 1 and 2.
Is this best-practice, or would you recommend another approach?products:org=1,dep=1#list@(groups:department1#members)
products:org=1,dep=2#list@(groups:department2#members)
products:org=1,dep=1#list@(groups:organization1#members)
products:org=1,dep=2#list@(groups:organization1#members)
groups:department1#members@john
groups:organization1#members@jane
products:org=1,dep=1#list@(roles:productmanagers,dep=1#member)
products:org=1,dep=1#list@(roles:productmanagers#member)
products:org=1,dep=2#list@(roles:productmanagers,dep=2#member)
products:org=1,dep=2#list@(roles:productmanagers#member)
roles:productmanagers,dep=1#member@john
roles:productmanagers#member@jane
steep-lamp-91158
products:org=1,dep=1#list@(products:org=1#list)
products:org=1,dep=2#list@(products:org=1#list)
by a global rule that does not need any relation tuple creation over the APImysterious-rose-44236
10/26/2021, 7:10 AM