Portal, V6.1

---

 

Actions

Actions use simple evaluation statements to select content to use or display, or to set information. Basic arithmetic calculations (addition, subtraction, multiplication, division) can be used on either side of the evaluation. Arithmetic calculations follow order of operations; there is no provision for the use of parentheses. Actions can be combined with profilers into bindings.

Select actions

Select data or content. Select actions retrieve data from a data store, typically for display on a Web page. Select actions also can be used within bindings to exclude certain content, that is, filtering a subset of returned content from a superset.

Update actions

Update content or objects on the request. Update actions cannot select content. Update actions are used to store content or data in the user profile, an application object, or other data stores.

E-mail actions

Send e-mail messages using a Web page as the body. E-mail actions cannot select content. An e-mail action sends an e-mail message to a recipient or list of recipients. An e-mail action assigned to a content spot sends an e-mail message when the content spot is triggered. For example, at the time a Web site visitor views a page with the content spot.

The e-mail action editor allows the fields that identify the recipients (primary, copied and blind copied), the subject line, and the sender to be identified by either explicit text or by resources attributes. The e-mail body is a separate file, such as a text file, an HTML file, or a JSP, that must be accessible from the e-mail server via a URI. An e-mailed JSP can contain content spots for personalizing the e-mail message for the user who triggers the content spot.

Although e-mail actions differ somewhat from e-mail promotions, both have prerequisites that must be in place and working before e-mail can be sent.

• Example: Simple select content action
  

• Example: Simple update action
  

• Example: Simple e-mail action
  

 

Parent topic

Rules

---