Surf Dashlets Extension Point

The Share web application has a special page called Dashboard, which contains windows (think Portlets) of content called dashlets. Currently most of these dashlets are Spring Surf dashlets, but they will eventually be converted to Aikau dashlets.

Architecture Information: Share Architecture


The following picture shows a User Dashboard with a number of Dashlets, such as My Sites and My Tasks:


You can implement your own custom dashlets that can be added to either the User Dashboard or the Site Dashboard.

Creating a Surf dashlet is the same thing as creating a Surf web script. Before continuing read through the Surf Web Scripts section. The controller of the dashlet presentation web script will usually call a Data web script on the repository side to get the content that should be displayed in the dashlet.

Let’s look at an example of a custom dashlet, the following picture shows a Member Directory dashlet that can be used to search the User/People directory:


This dashlet is implemented using a presentation web script, which in turn uses a Data web script to get the people matching the Search Filter parameter. The following picture illustrates:


In this case we have a Spring Surf Web Script on the Share side that will, in its controller, call a repository web script (that is Data Web Script) to get a list of person records in JSON format. The controller looks something like this:

// Get args from the Share page URL
var filterValue = page.url.args["filter"];
var connector = remote.connect("alfresco");
var peopleJSONString = connector.get("/api/people?filter=" + filterValue);

// create json object from data
var peopleJSON = jsonUtils.toObject(peopleJSONString);
model.people = peopleJSON["people"];  

The controller makes use of a special root object called remote, which is used to connect to a remote service, such as the repository, and get data. The JSON data is returned from a repository web script) (that is, a Data web script), which in its controller uses the public API to fetch person information matching passed in Search Filter (that is, filter).

The repository web script uses a root object called people to search for person info. This root object is Content Services specific and is only available in repository web scripts.

Now, to create a dashlet web script you also need a descriptor, which is defined in XML and looks something like this:

    <shortname>Member Directory</shortname>
    <description>Provide Search of people and display in a list</description>

The descriptor looks like any other web script descriptor except the family parameter, which can have the following values:

  • user-dashlet - A web script that implements a dashlet that can be added to a User Dashboard
  • site-dashlet - A web script that implements a dashlet that can be added to a Site Dashboard
  • dashlet - A web script that implements a dashlet that can be added to any Dashboard

The Dashlet UI needs to be implemented in the web script template as follows:

<#-- JavaScript Dependencies
<@markup id="js">

<#-- Stylesheet Dependencies
<@markup id="css">

<#-- Surf Widget creation
<@markup id="widgets">
    <@createWidgets group="dashlets"/>

<@markup id="html">
        <#assign id = args.htmlid?html>
        <#assign dashboardconfig=config.scoped['Dashboard']['dashboard']>

        <div class="dashlet">
            <div class="title">${msg("")}</div>
            <div id="${id}-memberdir" class="body">

                <div class="toolbar">
                    <div class="actions">
                        <form name="input"
                        ${msg("")}: <input type="text" name="filter" />
                            <input type="submit" value="Search" />

                <p valign="top">
                    <#list people as p>
                        <a href="${url.context}/page/user/${p.userName}/profile">
                        ${p.firstName} ${p.lastName} (${})


Here we are not using any custom client side JavaScript or CSS. Instead we use a simple HTML only based UI with default out-of-the-box styling. In the markup you will see references to i18n labels such ${msg("")}. These messages are defined in the web script properties file as follows: Directory Filter Result   

Deployment - App Server

  • tomcat/shared/classes/alfresco/web-extension/site-webscripts (Untouched by re-deployments and upgrades)
  • tomcat/webapps/share/components/dashlets (when web resources are included you need to put them directly into the exploded webapp, this is NOT recommended.)

Best practice is to put the files in a directory that explains what they are for, such as for example:


Deployment All-in-One SDK project

  • aio/share-jar/src/main/resources/alfresco/web-extension/site-webscripts/{custom path}
  • aio/share-jar/src/main/resources/META-INF/resources/share-jar/components/dashlets (when web resources such as CSS and JS are included)

More Information

  • Share Extras Project - Contains loads of Dashlets, good place to go and look at how different types of Dashlets can be implemented.

Sample Code


Edit this page

Suggest an edit on GitHub
This website uses cookies in order to offer you the most relevant information. Please accept cookies for optimal performance. This documentation is subject to the Alfresco documentation terms.