Javascript API for blueprint wizards

This page details the Javascript API available to support blueprint wizards.  The page contains the following topics:

Overview of the API

The Confluence Blueprint features includes a JavaScript setWizard() API. You can use this API to access one of three hooks:




Called before the system renders the Soy template. Use to add data to the Soy rendering context.


Called after the system renders the Soy template. Used to add JavaScript behavior to add addtional Javascript behavior to the wizard page.


Called when the dialog is submitted. Use this when you want to:

  • validate the wizard form
  • set the next wizard page
  • override the default submission behavior (for example, to go to a custom page)

  The callback function for each hook gets passed the jQuery event object and a  state  object containing several properties. Not all the properties are available to all the hooks. 




Contains all data gathered by the wizard pages. This is contained in the pages property of wizardData. The pages property is a map where the key is the id of the dialog page (e.g. page1Id) and the value is the pageData collected from that page.

pre-render: YES

post-render: YES

submit: YES


The jQuery object wrapping the page's rendered Soy template.

pre-render: NO

post-render: YES

submit: YES


Filled with the page's form values. May have further data added to it.

pre-render: NO

post-render: NO

submit: YES


Blank when the submit callback is called. You can set this value to specify which Wizard page to show next. If blank, the next page defined in <dialog-wizard> is shown.

pre-render: NO

post-render: NO

submit: YES


Blank when the function is called. You can set this value on the last page of the Wizard it specifies where the Wizard will go on completion. If blank, the Wizard displays the Editor page or View page based on the create-result configured in your blueprint module. See "Skipping the Editor" for details.

pre-render: NO

post-render: NO

submit: YES


Contains values for use in the Soy render. values The context object for adding values to, for use in the Soy render. The context is empty by default.

pre-render: YES

post-render: NO

submit: NO

Adding validation through the submit hook

To add validation to the form in your wizard, you can use the  submit  hook provided by the API. You add the hook in your Blueprint's Javacript:

Confluence.Blueprint.setWizard('com.atlassian.confluence.plugins.myplugin:blueprint-item', function(wizard) {
    wizard.on('submit.page1Id', function(e, state) {
        var myName = state.pageData.myName;
        if (myName == 'abc') {
            alert('That is not a real name!');
            return false;

As you can see from the above code, values from the wizard form are present as properties of the state.pageData object. See the Write an intermediate blueprint plugin for a complete example.

Skipping the editor

Some templates might get enough data from the wizard that they can skip the Editor and create the page directly. To do this, update your blueprint module to include a create-result attribute:

<blueprint key="myplugin-blueprint"

By default, wizards take users to the page in the Confluence Editor. To specify the view result, add a create-result attribute to your blueprint module. When view is set, the wizard creates the page immediately and takes the user to the completed page view.  If you choose to set create-result to view, you must pass a title for the new page. You can pass this value from your ContextProvider class or from the wizards JavaScript.  Using two methods allow you to collect a user-specified title through a from rather than generating a page title for the user.

User-specified Page Titles

To easiest way to pass a page title through the JavaScript wizard is to have a title form field in your wizard. This form value is passed to the server on the submit. The alternative is to add the title property to the wizardData state object manually somewhere in your JavaScript Wizard hooks. An example of a title field in the Wizard is the File List Blueprint that is bundled with Confluence.

Generated Page Titles

To generate a page title from back-end logic (for example, from a call to a remote site, or by adding a prefix/suffix to the Blueprint name), you can use a ContextProvider class (see the intermediate tutorial for an example). In your code, you add a property with the key ContentPageTitle to the context map. For example,

public Map<String, Object> getContextMap(Map<String, Object> context)
    context.put("myName", "Sherlock");
    context.put("ContentPageTitle", yourPageTitleProvider.makeTitle());
    return context;

An example of the ContentPageTitle being set by a ContextProvider is the Meeting Notes Blueprint that is bundled with Confluence.  

Custom JavaScript Wizards / Callbacks

There may be certain behaviors that our API doesn't allow for. In that case, you might need more control of the create experience. To get this control, regsiter a direct callback that is called when the user clicks the Create button after selecting your Blueprint. To register a direct callback, add the following to your blueprint's Javascript: 

Confluence.Blueprint.setDirectCallback('com.atlassian.confluence.plugins.myplugin:blueprint-item', function(e, state) {
    state.finalUrl = Confluence.getContextPath() + "/pages/createpage.action?spaceKey=" + encodeURIComponent(state.spaceKey);

When you use this callback, users that create your blueprint are taken to the URL specified above. In this example, it is the Confluence Editor with a blank page.  The direct callback is passed a state object similar to the default state object mentioned in the overview. Two important properties for direct callbacks are:

  • Use state.finalUrl instead of calling window.location or directly. 
  • state.spaceKey contains the space key of the space the user selected in the Create dialog.

If your blueprint includes a Let's get started page, the system displays it before redirecting the user to the finalURL page. All other wizard pages are ignored, even if you have JavaScript calls to setWizard and <dialog-wizard> defined in your Blueprint.

Once you send the user to a different browser location, you'll need to wire up the required xwork actions in your plugin XML, add a custom action, and so on. This advanced behavior is common with the Confluence plugins. See the XWork-WebWork Module for more information.

To provide users with a consistent experience and simplify the development experience for you, we recommend using the Blueprint API as much as possible. If you need to use setDirectCallback because of a deficiency in the API, please let us know!

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport