Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

DIFFERENCE BETWEEN ReAD ACESS AND WRITE ACESS IN SYSFILTERS

Avatar

Level 3

hi All, 

I am bit confused between ReAD ACESS AND WRITE ACESS IN SYSFILTERS

SO BELOW IS THE CODE we are using.

what will happen practiccally if we ,use below code in schema

and all other operator groups when they try to see data and data fields  in this schema 

and whey query this scheam using quey acitivity

 

in case we use write parameter

<sysFilter name="writeAccess">
<condition enabledIf="hasNamedRight('newlyCreatedNamedRights')=false" AND "hasNamedRight('ADMIN')=false Expr="FALSE"/>
</sysFilter>

 

SO BELOW IS THE CODE we are using.

what will happen practiccally if we ,use below code in schema

and all other operator groups when they try to see data and data fields  in this schema 

and whey query this scheam using quey acitivity

 

in ncase here we use read parameter

 

<sysFilter name="READAccess">
<condition enabledIf="hasNamedRight('newlyCreatedNamedRights')=false" AND "hasNamedRight('ADMIN')=false Expr="FALSE"/>
</sysFilter>

 

 

@ParthaSarathy

@ParthaSarathy 

@ParthaS 

@AkshayAnand 

@Craig_Thonis 

@Manoj_Kumar_ 

@Amine_Abedour 

@Marcel_Szimonisz

@DavidKangni 

@Amit_Kumar 

@ShashankNigam02

@Ganesh5067

@Jonathon_wodnicki

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @jefrii ,

By Default the operators with 'admin' namedRights can able to read and write access.

 

 

    <sysFilter name="readAccess">
      <condition enabledIf="hasNamedRight('NewNamedRights')=false" expr="FALSE"/>
    </sysFilter>

 

 

If you use the above script, all the operators and operator groups having the named rights as 'NewNamedRights' (and 'admin' by default) can able to Read the data and query the data. And rest of the operators and operator group without this namedRights will see NO data in the schema.

 

 

 

    <sysFilter name="writeAccess">
      <condition enabledIf="hasNamedRight('NewNamedRights')=false" expr="FALSE"/>
    </sysFilter>

 

Similarly, If you use the above script, all the operators and operator groups having the named rights as 'NewNamedRights' (and 'admin' by default) can able to Write (insert / update) the data. And rest of the operators and operator group without this namedRights won't be having permission to insert or update the data in this schema.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @jefrii ,

By Default the operators with 'admin' namedRights can able to read and write access.

 

 

    <sysFilter name="readAccess">
      <condition enabledIf="hasNamedRight('NewNamedRights')=false" expr="FALSE"/>
    </sysFilter>

 

 

If you use the above script, all the operators and operator groups having the named rights as 'NewNamedRights' (and 'admin' by default) can able to Read the data and query the data. And rest of the operators and operator group without this namedRights will see NO data in the schema.

 

 

 

    <sysFilter name="writeAccess">
      <condition enabledIf="hasNamedRight('NewNamedRights')=false" expr="FALSE"/>
    </sysFilter>

 

Similarly, If you use the above script, all the operators and operator groups having the named rights as 'NewNamedRights' (and 'admin' by default) can able to Write (insert / update) the data. And rest of the operators and operator group without this namedRights won't be having permission to insert or update the data in this schema.