RiSE Settings: Recent history
The Recent History content item displays a list of recently viewed contacts, events, groups, commerce products, and/or gift items. Use the settings at Settings > RiSE > Recent history to customize the text for each item that is displayed in the Recent History.
Example: There is an annual event with the same name each year. Customize how the event name displays in the Recent History content item so that it is clear which event was recently viewed.
Understanding how to create placeholders
Placeholders can be used to populate attributes within HTML tags, such as the src attribute of <img> and <a> tags. Placeholders are specified using { } notation. For example:
{datasource[.property... ] [attributes]}
The {#...}
placeholder embeds data into the content or title at the placeholder location. The placeholder consists of the following components:
- datasource - The name of the data source.
- property - (optional) The name of the property. Can be chained together using dot notation. For example, prop1.prop2.prop3. Where the property is a collection, a specific item can be accessed using [i] notation. For example, .Address[1] would return the item at index position 1 from the Address collection.
- attributes - (optional) A space delimited set of attributes, some of which require values. Multiple attributes can be specified:
- uppercase - Convert the data to uppercase.
- lowercase - Convert the data to lowercase.
- format - Format non-string values, such as format="d".
- noencode - By default, inserted properties are HTML-encoded. This means that any HTML characters in your properties are rendered as plain text. Use the noencode attribute to ensure HTML markup is rendered in the browser.
Example: <strong>{#Party.FirstName noencode}</strong>
Customizing the text for each type
Before updating the Recent History settings, review the following information:
- After changes are saved, the items listed in the Recent History do not conform to the updated format until the item is visited again. Newly visited items conform to the updated format.
- When left blank, the default display for that type is used. Use the reset icon to reset the data to the default.
- If there is a placeholder that cannot be resolved, the formula is ignored, and the default data is used.
To customize the text for each type, go to Settings > RiSE > Recent history:
- Contacts - Used to display recently viewed individual or organization account pages. Out-of-the-box, recent contact history is displayed on the Community > Find contacts and Community > Dashboard pages. Use PartyData properties to build the placeholders.
- Events - Used to display recently viewed events. Out-of-the-box, recent events history is displayed on the Events > Find events page. Use EventSummaryData properties to build the placeholders.
- Groups - Used to display recently viewed groups. Use GroupSummary Data properties to build the placeholders.
- Products – Used to display recently viewed commerce products. Out-of-the-box, recent product history is displayed on the Commerce > Find products page. Use ItemData properties to build the placeholders.
- Gifts – Used to display recently viewed gift items. Out-of-the-box, recent gift item history is displayed on the Fundraising > Find gift items page. Use ItemData properties to build the placeholders.
Example: {#party.Name}, {party.Id}
Example: {#event.Name}, {event.StartDateTime}
Example: {#group.Name}, {group.GroupClass.Name}
Example: {#item.Name}, {item.ItemCode}
Example: {#item.Name}, {item.ItemCode}
Restricting properties to staff users only
To restrict certain properties to staff users only, use the {if #session.IsStaff} {/endif} placeholders around the staff-only property, for example:
{if #session.IsStaff} {#datasource.property} {/endif}
Replace {#datasource.property}
with the desired property.
Example | Placeholder | Staff users | All others |
---|---|---|---|
Restricting the contact ID property to staff users only | {#party.Name} {if #session.IsStaff} ({#party.Id}){/endif} | image | image |
Restricting the product code property to staff users only | {#item.Name}{if #session.IsStaff} ({#item.ItemCode}){/endif} | image | image |
Additional syntax options
The following information provides additional formatting options with examples.
Syntax of conditional functions
To insert a conditional function in the HTML body of one of the supported areas, use the syntax:
{if (conditions)} Text or HTML to appear if condition is true {/endif}
If the conditions evaluate to FALSE, then the text or HTML is not shown.
Available conditional functions
This section covers the specific conditional functions supported in alerts, communication templates, Data Showcase, and Query Template Display.
Important! All conditional functions are case sensitive and must be upper case.
COUNT
Counts the number of items in a collection and returns an integer value.
Example:
{if (COUNT(#party.AdditionalAttributes) GT 0 AND #party.AdditionalAttributes[1].Name EQ 'IsMemberRecord' AND #party.AdditionalAttributes[1].Value EQ true)} Is a member. {/endif}
LENGTH
Determines the length of the value and returns it as an integer.
Example:
{if (LENGTH(#query.TAX_EXEMPT) GT 0)} Contact is tax exempt. {/endif}
ISTRUE
Tests whether the specified parameter is true.
Example:
{if (COUNT(#party.AdditionalAttributes) GT 0 AND #party.AdditionalAttributes[3].Name EQ 'IsMember' AND ISTRUE(#party.AdditionalAttributes[3].Value))} Contact is a member. {/endif}
ISFALSE
Tests whether the specified condition is false.
Example:
{if (ISFALSE(#query.IsMember))} Contact is not a member. {/endif}
ISNULLOREMPTY
Indicates whether the specified string is null or empty. Returns true if the value parameter is null or an empty string; otherwise, false.
Example:
{if (ISNULLOREMPTY(#query.Website))} Please add your website! {/endif}
ISNOTNULLOREMPTY
Indicates whether the specified string is not null or empty. Returns true if the value is not null or empty; otherwise, false.
Example:
{if (ISNOTNULLOREMPTY(#query.PaidThrough) AND #query.PaidThrough LT Now)} Contact is not yet expired. {/endif}
DAYSBETWEEN
Returns the number of days between two dates as an integer value.
Example:
{if (DAYSBETWEEN(#query.RenewedThrough, #query.PaidThrough) GT 90)} Member is due for renewal. {/endif}
DATE
Makes sure date or literal date value is culture safe.
Example:
{if (ISNOTNULL(#query.JoinDate) AND (#query.JoinDate GTE DATE('12/31/2021')))} 2022 MEMBER {/endif}
CONTAINS
Checks whether a particular sequence of characters is part of a given string. Case is ignored and true or false is returned.
Example:
{if (CONTAINS(#query.JoinDate, '2022'))} New member in 2022. {/endif}
NOTCONTAINS
Checks whether a particular sequence of characters is not part of a given string. Case is ignored and true or false is returned.
Example:
{if (NOTCONTAINS(#query.City, 'Austin'))} Member is not an Austin resident. {/endif}
STARTSWITH
Check whether the beginning of the current string instance matches with a specified string or not. Case is ignored and true or false is returned.
Example:
{if (STARTSWITH(#query.City, 'Aus') OR STARTSWITH(#query.City, 'Dal') )} Member may live in Austin or Dallas. {/endif}
ENDSWITH
Check whether the end of the current string instance matches with a specified string or not. Case is ignored and true or false is returned.
Example:
{if (ENDSWITH(#query.FullName, 'Smith') OR ENDSWITH(#query.FullName, 'Richards') )} Last name ends with Smith or Richards. {/endif}
The letter expressions are case sensitive and must be upper case. The following are acceptable condition operators:
- GT - Greater than
- GTE - Greater than equal to
- LT - Less than
- LTE - Less than equal to
- EQ - Is equal
- EQUALS - Is equal
- NEQ - Not equal
- OR - Logical Or
- AND - Logical And
- == - Is Equal, but preferred syntax is EQ
- != - Not equal, but preferred syntax is NEQ
- || - Logical Or, but preferred syntax is OR