Content gallery

• iPart CSS class - Enter the CSS class that will designs the button. Without a CSS class defined in this field, the content
• Panel image - (optional) Enter the URL to an image to display within the panel. The URL can be absolute (http://example.com/myImage.jpg//example.com/myImage.jpg) or relative (~/images/myImage.jpg).
  • Image alt text - (optional) If a Panel image is selected, enter a description for the image to be used as the alternative text.
• Mode - Select a mode for the Big Button Panel:
  • Navigation - Select this mode if you only want to offer a list of links. The options to filter by a URL Parameter and to trigger working On Behalf Of (OBO) someone are not available in Navigation mode.
  • Actions - In this mode, links can also contain URL Parameters that use dynamic filters. For example, you can pass the ID for the selected contact to the target page, which you can then use in content items, or to run reports for the contact. An additional option is also available to trigger working On Behalf Of (OBO) someone.
• Open links in a pop-up - Select this option to open links clicked within the Big Button Panel in a pop-up window. This option is useful, for example, if you want to quickly run a report or view information about the selected contact.
• Navigation item - (only available in Navigation mode) Select a navigation item for content to display within the panel.
  • Include parent navigation item - Select this option to include the parent navigation item as a link.
  • Child levels to display - If the navigation item selected has child navigation items within the sitemap, enter the number of levels to display. If you enter 0, all descendants are displayed. If you enter 1 or more, only that number of navigation levels is displayed.
• Limit users who can view data for other contacts - Select this option to hide the iPart if the user viewing the page does not have access to edit the selected content.
• Additional links / Actions - Click Add, enter the link information, then Save to add links to display within the panel.
  • Link Text - Enter the text to display for the link. If left blank, the text is automatically generated based on the title of the navigation item, content, or page title.
  • Link Target - Enter the target of the link, which can include URLs, URL shortcuts, navigation paths, content paths, or navigation codes.
  • URL Parameter - (only available in Actions mode) Add a URL parameter if the Link Target contains iParts or an SSRS report that can accept a URL parameter value as input. You can use dynamic variables in the URL parameter if needed. For example, if you are linking to a report that can filter results based on the value of a ContactKey URL parameter, enter ContactKey=@selecteduser, so that you can easily run the report for the currently selected user. You can use the following dynamic variables:
    • Pass in ContactKey and UserKey properties:
      • @LoggedInUser and @Me: Uses the currently logged in user.
      • @SelectedUser and @SubjectContact: Uses the selected contact, such as contacts selected through a URL parameter or On Behalf Of.
    • Pass in any existing URL parameter:
      • @url:[ParameterName]: Passes the value of a give ParameterName in the existing URL. For example, use EventKey=@url:EventKey to pass the current URL's EventKey parameter to the link.
  • Use On Behalf Of - (only available in Actions mode) Select this option if you want to set the currently selected contact as the On-Behalf-Of contact.

Do the following to create content using the Big Button Panel:
1. Edit the account page that displays after a staff user selects a contact from your directory. In the Member site, it is the Account Page Staff content record.
2. Add the Big Button Panel (add content > ContentTypes > Content > Big Button Panel) content item to the content record and configure it with the following settings:
   • Mode: Actions
   • Add an action link to run a report:
     • Link Text: Print Info
     • Link Target: Enter a link to a page that contains the SSRS Report content item that displays a report such as $/Samples/ReportingServices/MemberProfileQuery_Report.

     📘 Note

     The SSRS Report content item must be configured to Hide the parameters section and to enable the option to Inspect query string for parameters. Do not enable the option to Inspect Session for parameters. For more information about SSRS reports, see Creating SSRS Reports.

     • URL Parameter: ContactKey=@SelectedUser
   • Add an action link for event registrations:
     • Link Text: Register for an event

     📘 Note

     Customize this text for the event you want to register the contact for. For example, Register for the Spring Conference.

     • Link Target: Enter a link to the event page
     • URL Parameter: EventKey=XYZ (replace XYZ with an event code) EventKey=XYZ (replace XYZ with an event key), or use EventKey=@url:EventKey to use the event key from the URL parameter on the current page.
     • Use On Behalf Of: Enable
   • Add an action link for donations:
     • Link Text: Make a donation
     • Link Target: Enter a link to your donation page
     • URL Parameter: (Leave blank)
     • Use On Behalf Of: Enable
   • Add an action link for the shop:
     • Link Text: Purchase a product
     • Link Target: Enter a link to your Shop page
     • URL Parameter: (Leave blank)
     • Use On Behalf Of: Enable
3. Save and Publish the account page. 

To control what content appears in a Content Block, you create tags specific to ContentBlock Items and apply those tags to specific instances of the content item. For example, if you want to create a new blog for Tim Jones, you could create a ContentBlock tag such as blog-JonesT, place a new Content Block content item on a content record, and configure the content item to display the tag blog-JonesT. Now the content that Tim authors in this blog will be unique to his+ blog, if you do not apply this tag anywhere else:

Content created with anything other than a Content Block content item will not be displayed, even if it has the same tag. For example, a content record containing HTML tagged with News will not show up in a Content Block that is also using the News tag.

📘 Note

Plan for and create the tags you want to use before configuring your Content Block content items. Content can seem to disappear if you change the tags assigned to a content block already in use, because it no longer matches the tag set currently configured.

Only users with the Content Editor permission may create posts and children, but any authenticated users can reply to a post and edit or delete their own replies.

To use the Content Block as a message board with multiple posts, child posts, and replies, make use of the following configuration options:

• Maximum items to display – Choose the maximum number of posts that will be displayed; 0 indicates an unlimited number of posts.
• Display mode – Expanded display mode will display replies and child posts in-line, while Summary mode only shows replies and child posts when the post is opened.
• Allow child posts – Allow Content Editors to add a child post to existing content.
• Allow replies to posts – Allow authenticated users to reply to posts; you may indicate whether to allow HTML and/or attachments in the replies.

The Content Collection Organizer can be configured to use the content records in a content folder as the content to display on each tab. The name of each tab will match the name of the corresponding content record, and tabs will be organized by the Publish file name in alphabetical order.

📘 Note

This option is not available if Function as wizard is selected.

The same security settings apply to content folder defined tabs. If a user does not have required permissions to view a specific content record, the tab containing the content record will not be displayed. If the user does not have permissions to view any of the tabs, the content item will not be displayed at all.

You can configure the Content Collection Organizer to function as a wizard. The wizard can guide a user through multiple steps of an end-to-end process, for example, setting up a new account. When the Content Collection Organizer is enabled as a wizard, Next and Previous buttons are displayed, allowing users to navigate between the steps. Users can navigate to any previous tab, but can only navigate forward to the next tab in the workflow sequence. The user can also navigate with a browser's Forward and Back buttons, but the data is not committed until the user clicks Next.

As you add steps to the wizard, you define a name for the step, as well as select the content you want to display on that step. You can also define where the wizard will take a user if a step is successful or fails. Each page in the workflow is validated when the user clicks Next. If any of the data on a page is incomplete or incorrect, an error message is displayed and the user cannot proceed to the next step until the error is corrected.

You can also define the destination to which users are directed when they click Finish in the wizard. To do this, you must define the Finish button redirect. Select the Content record or URL radio button, then select the content or URL to which you want the user redirected. This defines the action that will happen once a user clicks the Finish button in a wizard process.

📘 Note

It is not recommended to point to content records that contain embedded content records. This can interfere with the behavior of pop-up windows. Also, if you are creating a wizard that is intended to be displayed in a pop-up window, it is not recommended to add any other content items to the wizard content record.

You can set up a Content Collection Organizer content item wizard to walk users through the process of creating an account. To do this, you must add a Content Collection Organizer content item to a content record.

1. Add a name for the Content Collection Organizer and a title, and make sure you select Function as a wizard.

You can select the content to redirect a user to when they are finished with this wizard. Redirect the user to their new account page upon completing this wizard. Select @/iCore/Contacts/ContactLayouts/AccountPage for the Finish button redirect content.

2. Create a first step. Select a content record with a Contact Account Creator content item, for example, @/iCore/Contacts/CreateAccount.
3. The Contact Account Creator content item must have specific configuration options set:
   • Select Hide for authenticated users.
   • Select Include option to create an account.
   • Select Require username and password.
   • Set the Redirect to option to Do not redirect.

You can now add as many additional steps as you like. On the last step, a Finish button is added. You have already added a redirect link for this button.

4. Click OK to save your wizard, save and publish, and add this content record to your website.

• - Full screen mode
• - Cut, Copy, Paste
• - Find and Replace, Spell check, Undo, Redo
• - Font name, Font size, Bold, Italics, Underline
• - Font color, Font highlight color
• - Left align, Center align, right align
• - Indent, Outdent, Insert numbered list, Insert bullet list
• - Insert table, Insert horizontal line, Insert image
• - Content Link Manager, Insert link (hyperlink, anchor, or email), Remove link
• - Insert new paragraph, Paragraph style, Apply CSS Class, Insert Symbol, Format Stripper:
  • Apply CSS Class - You can use the Apply CSS Class drop-down to apply styling and formatting to specific portions of the content. Select the area you want to style and choose a CSS class from the drop-down.
  • Format Stripper - Takes away any of the formatting that was applied. You have the option to select the type of formatting you want to take away from any highlighted content: All, Css, Font, Span, or Word.

To embed any external page into an iMIS site, you can use an <iframe> like this:

1. From the Staff site, go to RiSE > Page Builder > Manage content and create a new content record.
2. Select add content and place a single Content Html content item on it (from the ContentTypes folder).
3. Show the source by clicking the <> HTML tab and type in an iframe tag, such as this:

   <iframe width="100%" height="652" frameborder="0" src="//help.imis.com/"></iframe>

   📘 Note

   To avoid having content blocked (resulting in a Mixed Content error) do not include http: or https: in the src element.

4. Go to RiSE > Site Builder > Manage sitemaps and create a new navigation item that points to the new content record.
5. If appropriate, restrict the navigation item's Access Settings, such as to Authenticated User Full Control.

To insert a direct link to any content in iMIS or to an external site, you can use the content link manager:

1. Create a new content record with the Content Html content item, or edit an existing record to insert a link.

📘 Note

If the content record you are working with is new, you must save the content record before you are able to upload a new downloadable document.

2. From the editor toolbar, select the content link manager icon:

3. Choose a Link type:
   Content or URL

   This link allows users to travel to a separate webpage.

   1. Enter the Link text.
   2. To define the Content or URL do one of the following:
      • Select content from the Document Browser.
      • Type in a content record's direct path. For example, @/iCore/DefaultStaff.
      • Type in a shortcut URL. This will preserve the link even if the content is moved in the document system. The shortcut must conform to the format ~/Shortcut.
      • Type in a direct link. For example, http://www.help.imis.com.
   3. Enter a CSS Class that will be applied to the link.
   4. If the Content or URL is pointing to an iMIS content record, select a Default website.
   5. Enter or select a Source code to associate this link with a marketing campaign.
   6. Enter Additional URL parameters to include in the link. To add multiple URL parameters, follow this format: param1=value1&param2=value2&param3=value3
   Downloadable document

   This link allows users to download a document:

   1. Enter a link description for Link text.
   2. From Document, select the desired file, or upload a new file by clicking New. If the content record you are working with is new, you must save the content record before you are able to upload a new file.

   📘 Note

   To manage these files, go to RiSE > Page Builder > Manage files.

   3. Click OK.
   4. (optional) Enter a CSS class for the link.
4. Click OK.

You can install and display JavaScript-based web widgets (plugins, gadgets) in your WCM-generated websites using the Content Html content item. A web widget is a small program that your users can execute within a web page and that can provide a wide range of functionality.

For example, Google Gadgets offers thousands of free web widgets including mini applications, games, news feeds, maps, and a wide range of other types of content. Many other websites also provide free widgets that can access data from their site. For example, Twitter provides widgets that let you display Twitter updates on your website. LinkedIn provides plugins that display information such as company profiles, member profiles, and links to share on LinkedIn. You just have to search the web to see what you can find that meets your needs.

🚧 Warning

Only embed widgets from authors whom you trust. Malicious code may damage your computer or violate your privacy.

The Content Html content item does not support the use of the ~/ (tilde slash) shortcut, often used to automatically build the correct paths when a control is rendered in different domains. However, several variables are available in this content item that allows you to enter paths for links and resources that are automatically resolved to various folders in your website.

• [Website] and [@] – Both variables resolve to the root of the website and contain the website name. For example, [Website]Home.aspx resolves to http://mydomain/Staff/Home.aspx.
• [~] and [Root] – Both variables resolve to the root of the website. For example, [~]Home.aspx resolves to http://mydomain/Home.aspx.
• [Common] – Resolves to the AsiCommon directory of the website. For example, [Common]images/image.png resolves to http://mydomain/AsiCommon/images/image.png.
• [iMIS] – Resolves to the iMIS directory of the website. For example, [iMIS]images/image.png resolves to http://mydomain/iMIS/images/image.png.
• [Theme] – Resolves to the website’s theme folder. For example, [Theme]images/image.png might resolve to http://mydomain/App_Themes/Orion/images/image.png. This variable can be used to access theme resources such as images and CSS.

📘 Note

Images that use relative paths do not render in Design mode because the variable is not transformed until the content record is published.

You can define any number of data sources. For your data source, you may use any valid data contract, minus the "Data" suffix. For example, EventData is sourced as Event. Browse the Common Entity Types for key data contracts (entities) and their properties:

• Membership entities
• Commerce entities
• Event entities
• Fundraising entities

Each data source has the following properties:

• As - The value by which to refer to the data source. Each data source must have a unique value or name.
• From - The SOA entity type that the data source returns.
• Where - The where clause used to locate the entity. This consists of the following:
  • Property - The entity property to search on. Typically the entity Id (EventId, PartyId, or ItemId). Multiple properties may be specified using | as a delimiter. For example, PartyId|ItemId.
  • Value - The value to search for. This can be retrieved from a URL parameter. When using multiple Where properties, supply a value for each property using | as a delimiter. For example, 260|G15.

You can use the @SelectedID variable to filter by a selected contact ID. The ID is selected based on the ID passed in the URL parameter. If no ID is passed in the URL, the ID is considered to be the On Behalf Of contact's ID (if set), or the logged in user's ID. You can use this variable when you specify PartyId as the Property.

You can retrieve the Value property of the Where clause from the URL. This allows a single content item to dynamically display details from a given entity by providing the Id value of the entity (or other such unique property value) in the URL.

To read a parameter value from the URL, use the syntax url:parameter, where parameter is the name of the URL parameter. For example, url:EventKey.

📘 Note

Where the data source matches multiple entities, only the first entity is resolved into the content.

Use placeholders within the content and the title to denote areas that will resolve against the data sources. Placeholders may also 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. May be chained together using dot notation. For example, prop1.prop2.prop3. Where the property is a collection, a specific item may 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 may be specified:
  • uppercase - Convert the data to uppercase
  • lowercase - Convert the data to lowercase
  • format - Format non-string values, such as Format="d", for date (search MSDN for iFormattable)
  • noencode - Do not HTML encode the data. This is useful where the data contains HTML markup that you wish to be rendered in the browser.

  👍 Example

  <strong>{#Party.FirstName noencode}</strong>

  • resolve=~ - replace any ~ (tilde) characters in the data with the webroot url. This is useful where the property is a URL that uses ~ notation to denote the webroot, such as a Events.ImageUrl.

Examples:

{#event.Name}
{#event.Name uppercase}
{#event.StartDateTime format="d"}
{#party.Status.Name}
{#party.Addresses[1].Address.CityName}
<img src="{#event.ImageUrl resolve=~}">

Foreach {foreach alias in source [orderby [property,... ]] [limit[number]]}

The {foreach} placeholder must have a closing {/foreach} placeholder. The content between the opening and closing placeholders is the inner content. The inner content may contain placeholders, including nested {foreach} placeholders. The inner content is repeated and resolved against each item in the collection.

The placeholder consists of the following components:

• alias - A name for the data source that will represent the current item in the collection. This data source will be used in placeholders within the inner content to refer to the item being processed.
• source - A data source and property path that refers to the collection to iterate through e.g. event.Functions. If the data source itself is a collection, the property path may be ommitted (typically only used in nested foreach loops for iterating through collections of collections).
• orderby - (optional) To order the collection, use the orderby keyword followed by a comma-delimited list of properties to order the collection by.
  • A maximum of five sorting properties may be specified.
  • Property names must refer to properties of the objects within the collection and may be chained using dot notation.
  • Do not specify a data source in the property names.

The entire collection is ordered before the optional limit clause is applied.

• limit - (optional) To limit the number of records processed in the collection, use the limit keyword followed by the maximum number of records you want processed. Limit is applied after the entire collection has been sorted using the orderby clause.

Examples:

• Display the city from each party address:
{foreach a in #party.Addresses}
{#a.Address.CityName}
{/foreach}
• Display the name of each function in an event, ordering by the start date and name, and have the data display as an ordered list:
<ol>
{foreach f in #event.Functions orderby StartDateTime,Name}
<li>
{#f.Name}</li>
{/foreach}
</ol>

The communication creator uses this same functionality. For more information, see steps 5 and 6 in Defining a new email template.

Sometimes it is helpful to be able to conditionally control what is displayed in the Data Showcase content item based on a value retrieved from the database. In this example, the Data Showcase was added to the Account Page Staff content record. This simple example is using Party ID information to detail whether the contact is a man, woman, or unidentified by looking at the Mr., Mrs., Miss, or blank prefix in their name.

The end result will look something like this:

• The actual content for this example is short.

Where {#myParty.Name} is injecting the Party name from the data source (myParty). The data source is using the Party property where the PartyId equals the ID in the URL to find the Party record. For example, Teresa Spain’s ID is 19384. As long as the parameter ID=19384 is in the URL, we will use Teresa’s party record as the data source.

• Once the Data sources are specified, its time to insert some javascript. This is where you identify what information from the data source that you want to use. In the content item, click the HTML tab. This is what we have in the HTML tab for this example:

<script>
// Use jQuery to add an onready function
jQuery(function()\{
		// read the prefix from the hidden field it was injected into and tidy it up
		var prefix = 
jQuery("#NamePrefix").val().toUpperCase().replace(".","");
								
		// figure out which of the man,woman,unidentified spans to show
		var spanId = "#unidentified";
		switch (prefix) {
					case "MR":
						spanId = "#man"
						break;
					case "MRS":
					case "MS":
					case "MISS":
						spanId = "#woman"
						break;
			}
			// show the span
			jQuery(spanId).show();
\});
</script>
					
<!- Here we have a hidden field whose value we are setting from our datasource->
<input id="NamePrefix" type="hidden" value=" {#myParty.PersonName.NamePrefix}" />

{#myParty.Name} is
								
<!- Here we have  spans containing the different content we want to display based on the sex of the contact ->
<!- All the spans are hidden by default, and the javascript shows the relevant one ->
<strong>
<span id="man" style="color: blue; display: none;">a man</span>
<span id="woman" style="color: fuchsia; display: none;">a woman</span>
<span id="unidentified" style="color: green; display: none;">unidentified</span>
</strong>

In this example, we opened up a script block and are using a jQuery to inject an onready function, so that this function will run after the page has loaded. The actual function contains all of the logic, but for now let's review the hidden input field:

\
\ 

• In this section we have added a hidden input field to the page. The value property of the hidden input field is using the standard naming notation:

  {#myParty.PersonName.NamePrefix}

So we know that it is coming from data source myParty, and that PersonName.NamePrefix is going to be the value property of the hidden control. You don't have to use a hidden control, you can use a span, div, or anything you like, but you need to be able to get to it later by name or ID.

For our example, we've given the input control an ID of NamePrefix, which is used in the jQuery in the lines above to access the element and read its value:


• The {#myParty.Name} is line is what you see in the Design screen. Below that line is a series of spans. Each span has a unique ID - man, woman, and unidentified. Some styling has been applied to these lines as well:


These IDs can be anything you would like, for example, larger text, images, or tables. When the page loads, the jQuery ready function runs. While it runs it is looking at this text:



It's pulling the NamePrefix data we described earlier, and then it cleans the text up a little, making the name prefix uppercase, and getting rid of any periods at the end of it. So at this point we will end up with capital MR, MRS, MS, and so forth.

• The next sections is a switch statement. It declares a variable called spanId, which is the ID of the span it is going to show when it gets to the end of the function, and that corresponds with the man, woman, and unidentified spans defined earlier.
• The default span will be the unidentified span. Then we tell it to look at the prefix, and if there is a Mr, Mrs, or Miss, then put in the correlating identifier. Then the last bit is telling it to show the span once the span is identified as one of the three.