Développer ma barre des réalisations de la Communauté.

Submissions are now open for the 2026 Adobe Experience Maker Awards
RÉSOLU

can sysFilter be used to hide attribute for user?

Avatar

Level 1

Hi,

 

for schemas it's working fine but can we used also for attributes ?

 

1 solution acceptée

Avatar

Réponse correcte par
Level 10

Hi @BartoszGo ,

 

No, sysFilter does not directly hide individual attributes within a schema. The visibility of attributes within a schema is primarily controlled by access rights and the schema's definition itself. sysFilter operates at the schema level, not the individual attribute level.

 

Here's how you can do it:

1. Create an operator group which contains the list of all operators who should have access to that attribute.

2. In the schema definition, add the below bold syntax to the attribute definition:

<attribute label=“Creation Date” name=“creationDate" type="datetime" visibleIf="((HasNamedRight('admin') == true) or (HasNamedRight(‘custom’Right') == true))"/>

3. Also, you can make few fields read only to certain operators using the below syntax in Input Forms:

<container colcount="2" colspan="2" readOnlyIf="HasNamedRight('approvalAdministration')=false"

                    type="readOnlyGroup">

 

Whatever, elements mentioned under this container will be readOnly to all the operators who does not belong to 'approvalAdministration' operatorGroup.

 

Thanks,

Jyoti

 

 

Voir la solution dans l'envoi d'origine

2 Replies

Avatar

Community Advisor

Hi @BartoszGo ,

For attribute level you can try utilizing the below parameters inside your attribute tag as per your requirement,

visibleIf="hasNamedRight('abc')=true"
accessibleIf="hasNamedRight('xyz')=false"
advanced="true"

Avatar

Réponse correcte par
Level 10

Hi @BartoszGo ,

 

No, sysFilter does not directly hide individual attributes within a schema. The visibility of attributes within a schema is primarily controlled by access rights and the schema's definition itself. sysFilter operates at the schema level, not the individual attribute level.

 

Here's how you can do it:

1. Create an operator group which contains the list of all operators who should have access to that attribute.

2. In the schema definition, add the below bold syntax to the attribute definition:

<attribute label=“Creation Date” name=“creationDate" type="datetime" visibleIf="((HasNamedRight('admin') == true) or (HasNamedRight(‘custom’Right') == true))"/>

3. Also, you can make few fields read only to certain operators using the below syntax in Input Forms:

<container colcount="2" colspan="2" readOnlyIf="HasNamedRight('approvalAdministration')=false"

                    type="readOnlyGroup">

 

Whatever, elements mentioned under this container will be readOnly to all the operators who does not belong to 'approvalAdministration' operatorGroup.

 

Thanks,

Jyoti