When you combine custom properties with the Variable type of condition, you can define views with variable components. The following examples demonstrate how to work with variable condition components.
Define dynamic user name view
You can define a view that includes only items that contain a custom property value that matches the currently logged-in user. For example, to return only items that have an Employee custom property that contains the user name of the person running the view, you would add a condition that determines if the Employee field is equal to the current user's user name. The following table provides the settings you use to define a dynamic user name view.
| Condition Component | Value |
|---|---|
| Constrain by | Custom Property |
| Type | Variable |
| Field | User custom property |
| Operator | Any |
| Value | Customer user’s user name |
If you want to return only items that are captured by the person running the view, you add a condition that determines if the Created By field is equal to the current user's user name. To include only items that are routed in a workflow, checked out, created, last viewed, modified, or marked private by the currently logged-in user, refer to the following settings for the condition:
| Condition component | Value |
|---|---|
| Constrain by | User |
| Type | Variable |
| Field | Any |
| Operator | Any |
| Value | Customer user’s user name |
User attribute view
You can define a user attribute view by including only items that contain a custom property value that matches a specific attribute value of the currently logged-in user (such as first name, last name, locality, or organization unit.) For example, all items are in folders created from a folder type that has a custom property called Region. Region has values such as Northeast, Mid-Atlantic, and Southeast. In the same context, the users are assigned region properties, using exactly the same values (Northeast, Mid-Atlantic, and so on) stored in the user attribute called Locality. The following table provides the settings you use to define the user attribute view.
If you want to return only items with a folder Region custom property that matches the Locality value of the person running the view, add a condition that determines if Region is equal to Current user’s locality.
| Condition component | Value |
|---|---|
| Constrain by | Custom property |
| Type | Variable |
| Field | Any custom property value that uses a user attribute |
| Operator | Any |
| Value | Customer user’s user name |
Dynamic date view
You can define a dynamic date view by including items that contain a custom property date value that can be compared to the date when the view is run. For example, to return invoice items that are past due, you would add a condition that determined if the payment due date is less than the current date and time. The following table provides the settings you use to define a dynamic date view.
| Condition component | Value |
|---|---|
| Constrain by | Custom property |
| Type | Variable |
| Field | Any date custom property |
| Operator | Any |
| Value | Current date and time |