Using the . Operator

You can restrict the results returned by an expression by using the dot operator ("."). This can be used in two ways.

Using the dot operator to qualify organization entities

You can use the dot operator to specify a qualification of an organizational entity. For example:

orgunit(type="Sales").privilege(name='signoff' qualifier>10000)

This expression returns resources in those Organization Units of type Sales that have the privilege qualified by a value of greater than 10000.

Note: This is not a simple "and" operator; the expression does not return resources that are in organization units of type Sales and that have the required privilege; it returns resources where the organization unit itself has that privilege.

The dot operator is not commutative: in other words, changing the order of the expression changes its meaning.

So, for example:

position(name='abc').orgunit(type='Sales')

Expressed in natural language, this example means:

All Resources, in all Positions of Org-Unit of type "Sales", in which the Position named "abc" .

Another example is:

orgunit(type="Sales").position(name="abc")

Expressed in natural language, this example means:

All Resources in the Position named "abc" of Org-Unit of type "Sales".

Using the dot operator in hierarchical relationships

The dot operator works differently when used to express hierarchical relationships between two organizational entities. For example:

orgunit(type="area office").position(type="manager")

returns Positions of type manager that are in organization units of type area office.

Note: You can only use the dot operator to link organizational entities that are directly connected by arrows in the diagram in Navigating the Organization Model with RQL Queries . For example:

organization(type="public company").position(type="manager")

would not be valid, because organization and position are not directly linked.