Administrator Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Getting Started with AquaLogic Pages

This chapter briefly describes Pages, the objects you can create in Pages, how to work in the user interface, and provides a use case scenario.

 


Overview of AquaLogic Pages

Pages is a web page authoring system and application builder that provides even non-technical end-users a simple way to create web pages, blogs, wikis, and other web applications. Because of its ease of use, anyone with the proper permissions can create ad-hoc, collaborative workspaces without having to rely on an IT or portal administrator to do it for them. Because objects in the system are versioned, you can allow everyone (with the proper permissions) to confer their knowledge and ideas directly to the Pages system, enabling much more rapid and complete knowledge transfer and collaboration.

Plus, unlike traditional wikis, Pages allows you to surface data from existing enterprise systems via RSS, web services, or by creating custom data sets. This allows you to reuse existing data and quickly collect new data, all of which users can contribute to by adding comments, page components, or document attachments.

Pages Objects

Web pages created through AquaLogic Pages are grouped into logical collections called LiveSpaces. For example, you might create a LiveSpace for a sales team with separate pages for new products, sales tools, leads, promotions, and reports. Each page is made up of components such as rich text, images, lists, or tables. The lists and tables are backed by DataSpaces. A DataSpace is a set of data (in the form of records) from an external source or from a custom data model stored in the Pages repository. For example, you might create a products DataSpace that includes a record for each product.

Note: For more information on an object, see the associated chapter in this guide.

Accessing Pages Content

There are several ways to access Pages content:

Note: For more information on navigating Pages, see the online help.

The Dashboard

The Dashboard is the home page (default page) for the Pages application. It provides a list of most-recently created or modified LiveSpaces, DataSpaces, pages, and documents. The Dashboard also provides links to create new LiveSpaces or DataSpaces and provides access to the Organizer.

The Dashboard displays objects, sorted by last modified date, grouped into the following categories:

To view or edit an object, click the object name. The object opens in page view (described later), in which you can view the object, and, if you have appropriate access, edit the object (for example, change settings or add text or images).

The Dashboard provides the following functionality to help you find what you are looking for:

Note: For more information on the Dashboard, see the online help.

The Organizer

The Organizer displays objects grouped by type: LiveSpaces, pages, documents, and DataSpaces. You can click an object to view it, or perform an action on the object such as viewing information and settings for the object, editing the object, or deleting the object. The Organizer also enables you to search and filter the objects.

To view or edit an object, click the object name. The object opens in page view (described later), in which you can view the object, and, if you have appropriate access, edit the object (for example, change settings or add text or images).

The Organizer provides the following functionality to help you find what you are looking for:

Note: For more information on the Organizer, see the online help.

Page View

When you click an object, the object opens in page view (there are a few exceptions noted below). Basically, Pages automatically creates a page and displays the object. This enables you to add additional content to the object just like any other page. For example, you can add a comment, an image component, rich text, or a document attachment. The page for the object is not saved unless you publish the page. If you publish the page, the additional content appears whenever anyone opens the object in page view. For example, if you are viewing a DataSpace and click a record, the record opens in page view. If you add an image to the page and publish the page, anyone who views the record in page view will see the image.

Notes:

Page Components

You can add content to an object in page view by dragging components from the palette onto the page. The following components are available:

Table 2-1 Available Page Components
Component
Description
Image
Enables you to add an image to the page. You can use an uploaded image or point to a URL.
Record List
Enables you to add a list of records to the page. A record list enables users to search for and view records. With editable DataSpaces, users with the proper permissions can also edit, add, and delete records.
Rich Text
Enables you to add formatted text to a page.
Table
Enables you to add a table of records to the page. A table enables users to search for, sort, and view records. With editable DataSpaces, users with the proper permissions can also edit, add, and delete records.

Note: For more information on page components, see Components, and the online help.

Comments

At the bottom of the page you can add comments, and engage in message-board style discussions, in the context of any object in page view. This provides a simple way for users to provide structured feedback on the page or comment on content (for example, commenting on a particular blog post).

Notes:

Documents

Although you can add content to pages using rich text and page components, you might also want to add existing content (for example, Word documents or PowerPoint presentations). You can add this existing content by attaching documents to objects in page view. After attaching a document, users can view the document or upload new versions of the document.

Notes:

Associated Objects

In page view, under This Space, you see objects associated with the LiveSpace or DataSpace you are viewing or associated with the parent LiveSpace or DataSpace:

However, you can also search for a particular object, display all the objects of a particular type, or display recently-modified objects associated with any space.

Note: For more information on the This Space area, see the online help.

Versions

Each time a page view is published, a new version is stored in the system. These versions are displayed in the page view making it easy for users to view a previous version, and, with the proper permissions, revert to the version or delete the version. Because each change is saved as a version and it is easy to revert to a previous version, users can feel free to make changes without having to worry about inadvertently causing issues on the page.

Note: For more information on versions, see Page Versions, Documents, and the online help.

 


Use Case

This is a simple example of how Pages can be used to improve the ability for a customer support team to respond to a critical support situation.

  1. A support engineer creates a new "Support Issues" DataSpace, which displays a list of support incidents for a single customer. The list is pulled directly from a customer support management system, using a custom DataSpace template created by IT.
  2. An account manager, who is largely responsible for customer satisfaction for this individual account, creates a new "Issue Tracking" LiveSpace for assembling all the information related to this specific customer and this specific issue. The information will be assembled by an extended team of participants related to the account or related to resolving the issue.
  3. The account representative opens the LiveSpace, clicks Write, and types a list of "action items" and owners for each action needed for the support team to address.
  4. A customer service representative opens the LiveSpace, clicks Design, and adds a "Support Team" Table component to the page. She points this component to the existing "Employee Contacts" DataSpace, which pulls a list of records from an internal LDAP system.
  5. A product engineer creates a "Customer Issue Resolutions" DataSpace, which displays an RSS feed listing blog entries from the support department's knowledge base, related to resolving similar issues.
  6. Another product engineer opens the LiveSpace, clicks Design, and adds a "Best Practices" Record List component to the page, pointing it to the existing "Customer Issues Resolutions" DataSpace from step 5.
  7. The support engineer opens the LiveSpace, clicks Design, and adds a "Customer Issues" Record List component to the page, pointing it to the existing "Support Issues" DataSpace from step 1.

At this point, our simple "Issue Tracking" LiveSpace has several components:

  1. After some research, the product engineer opens the LiveSpace, clicks the associated item in the Best Practices list to display the issue resolution record and adds some unstructured notes under the record, specifying specific resolution steps.
  2. The support engineer sends the resulting resolution steps to the customer to resolve the issue.

  Back to Top       Previous  Next