Previous Topic: EventsNext Topic: Use Dynamic Values in Data or Action Elements

Data Elements

Data elements are used for creating policy data. A policy can contain multiple data elements that represent the information used by the policy.

Policy Xpress uses flexible plug-ins for gathering the data element information. Each plug-in can perform a small, dedicated task. However, several plug-ins can be used together to build more complex policies. An example of a data element plug-in is a user attribute element. The goal of the element is to gather information about a certain attribute which is a part of the user's profile.

Data elements are calculated when they are called, meaning either a rule is using the data element, or another element needing calculation is using the data element as a parameter.
For example, an SQL query data element can retrieve a value from a table, but it needs the user's department to build the query. In this case, the department data element must run before the SQL query data element, and then the value can be used as a parameter.

The following fields define a data element:


Defines a friendly name that describes the data element. Some data elements are complex (such as getting variables or retrieving information from the database). Be sure to select a meaningful name to simplify data element management.


Provides a grouping of data elements. This field sorts the data elements and makes selection easier.


Specifies the data element type, each with its own dedicated use. This field is based on the category selected.


Defines possible variations of the same data. Most data elements only support the Get function.

For example, the user attribute data element has the following functions:

Function Description

Provides a prepopulated description of the function. Each function selected provides a different description to help in understanding its use and what the expected values are.


Defines the parameters passed to the data element. Data elements are dynamic and can do different things based on the parameters. A user attribute data element returns different results based on the attribute selected. The sub type option also defines the number of parameters, their names, and the optional values when available.

You can add additional parameters if necessary. The SQL query example accepts two required parameters, the data source and the query itself. The query can use the "?" to be replaced with values (much like a prepared statement). Adding additional parameters allows you to set those values.

Note: When viewing data elements in Policy Xpress, there is a column titled 'In Use'. A checkmark in this column means that the data element is used by a rule, an action parameter, or as a parameter to other data elements.