Rule elements

Learn about the options in the rule editor for the different types of rules.

• Arithmetic expressions
  Arithmetic expressions allow us to perform mathematical operations on resource attributes as part of the rule. When you choose this option, we can select multiple resource attributes, values, and operators (addition, subtraction, multiplication, or division) to use between them.
• Count of (quantifiable conditions)
  Create an evaluation based on a count or tally of attributes that meet the criteria.
• Current Action Count or Action Name
  Current action count, like current category count, is a way to base a profiler or rule on the number of times a Web site visitor has performed certain actions. These actions must be logged using the action logging beans in order to be accessible by the rule. Current action name inspects the names of the actions logged.
• Current Browser Capability
  Browser Capability is an application object that allows us to profile a Web site visitor based on the attributes or capabilities of the browser being used. When applicable, it appears in the rule editor as an option when we select Resource.Attribute.
• Current Date
  The current Date resource contains several attributes we can use for comparison (date, day, month, time, timestamp, weekday, and year). To set values, you may enter a specific value or reference the value of a specific attribute of the same type.
• Current Request Attributes
  Use current Request Attributes to inspect request attributes which can be set on the current JSP. You must know the name of the request attribute to use it in a rule. This request is the request passed into the content spot executing the rule.

  For example, you would use the portlet request to set the current Request attribute for portlets. The portlet request is not shared among portlets. For jsps directly within a Web application, the current Request Attribute is the HTTP request of the Web application.

• Current Request Parameters
  Use current Request Parameters to inspect data contained within the query string (the variables and values that appear after a question mark on a URL).
• Current Session Attributes
  Use current Session Attributes to inspect parameters stored within the current session object for the Web site visitor. You must know the name of the parameter to use it in a rule. All data types are supported. The current session object is the session associated with the request passed into the content spot executing the rule.

  For example, the current session object is the portlet session, which is unique to the portlet. For jsps within a WAR, the current session object is the the http session.

• do Action
  Within a binding, we can couple actions with profilers so certain tasks are performed when certain conditions are met. We can also indicate actions to be done under other conditions. Use the Do action, Otherwise do action, Always do action, and Exclude do action elements.
• Include Only
  Include Only is a choice within the Select Action and Recommendation Rule structures. We can select action or binding rule to be used as the include only cause. When the content is selected for the main select action or recommended rule, it is only returned if it would be selected by the Include Only clause's action rule.
• is
  Select is to evaluate the relationship between two sides of a conditional statement.
• order as is
  Order as is is used to specify the order you want selected content to be returned and used. The default, order as is, will return data in the order it is stored in the repository. By clicking the order as is link, we can also choose order randomly or order by.
• Profile
  Profile is an arbitrary name (of the choicethat provides information about the Web site visitor, the date and time the visit occurs, or other circumstances or conditions.
• Profiler
  Profiler is a choice within the binding rule structure, and within the Specify a Resource Attribute window when constructing a profiler. Within a binding, you identify specific actions to perforthat are based on the one profile within a profile that evaluates as true.
• Quick Profiler
  Quick profilers are created within bindings to perform simple evaluations. By using a quick profiler, we can avoid creating simple profilers as separate rules.
• sender
  sender must be a valid email address, list of email addresses (comma separated), or a resource attribute containing valid email addresses to whom the email will be sent.
• set to
  Learn about the set to action and alternatives to set to.
• value
  Value is the placeholder for the result of an evaluation. This value can be one you enter, the value of another resource attribute, or an arithmetic expression.

Parent: Rules