Skip to content

Dynamic Group Configuration Guidance

Please be aware of the following behaviours of dynamic criteria:

  • Only the criteria that you are entitled to use will be available for you to configure. Access to sensitive criteria, such as age, is tightly controlled. Please create a Service Now ticket if necessary.
  • Each standard (non-role) criteria is combined using an AND operator. This means that a member must satisfy all criteria to be included in the group.
  • Role based criteria are combined with an OR. This means that a member only needs to satisfy one role criteria to be included.
  • Standard and role criteria are combined with an AND

Role Criteria

Please be aware of the following when defining role criteria

  • The Role identifier must be chosen
  • An optional Target Type can be chosen
  • Optional Target IDs can be chosen, using a variety of opertors: Equals, Not Equals, In, Not In, Between

To query for all TSOs for both buildings and car parks you would specify 2 criteria:

Field Operator Value
Role Equals TSO
Target Type Equals BUILDING
Field Operator Value
Role Equals TSO
Target Type Equals PARKING

For example, to query for all TSOs in buildings 31, 28 and 513 you would specify:

Field Operator Value
Role Equals TSO
Target Type Equals BUILDING
Target ID In 31,28,513

Examples

The following would give me all the Section and Group leaders in building 31: 

"BUILDING Equals 31" AND
(
"Role Equals SL, Target Type Equals SECT" OR
"Role Equals GL, Target Type Equals GROUP"
)

If I modified it to the following I would have no members because nobody is in both building 31 and building 28. 

"BUILDING Equals 31" AND
"BUILDING Equals 28" AND
(
"Role Equals SL, Target Type Equals SECT" OR
"Role Equals GL, Target Type Equals GROUP"
)

If I wanted Section and Group Leaders from both buildings I would use the In operator for the building criteria: 

"BUILDING In 31,28" AND
(
"Role Equals SL, Target Type Equals SECT" OR
"Role Equals GL, Target Type Equals GROUP"
)

Several incidents have been caused over the years by people adding a criterion PersonID Equals 1234567 when troubleshooting an issue - please be aware that this will reduce your dynamic group to a single person.