Last modified by Manuel Leduc on 2023/10/10 11:38

Before you start customizing your application you should understand:

Application Pages

All the application pages are generated inside the location specified in the first step of the application creation wizard. The code pages are grouped under the Code page and are marked as hidden (so your users don't see them by default). The location where the application entries are created is configured in the third step. By default the application entries are created directly under the application home page.


The AppWithinMinutes wizard creates the following wiki pages initially:

  • The application home page (Holiday)
    • The Preferences page (WebPreferences) which gives administration rights over the application's home page and its children to the application creator (so that he can delete all the application's pages)
    • The Code parent page, where the application code is located
      • The class, defining the structured data managed by your application (e.g. Holiday Class)
      • The template provider, which exposes your application in the Create Page dialog (e.g. Holiday Template Provider)
      • The sheet, which is used to display and edit application entries (e.g. HolidaySheet)
      • The template, which keeps the default values to fill when creating new application entries (e.g. HolidayTemplate)
      • The translation bundle, which can be used to internationalize the application (e.g. HolidayTranslations).

Among the advantages of having this separation between code and data, there is:

  • Ability to hide the Edit application options to your users by denying the Edit right on the application's Code page and all its children. This way you can precisely control which users on your wiki are allowed to edit your application and your regular users won't be able to edit/break your application by mistake.
  • Ability to control which users can add new entries or edit/delete existing entries by allowing or denying the Edit right on the application's data location and all its children. 
  • Ability to easily backup your application's data
  • Better overall organization
  • etc.

Before 8.4

There was no "Entries" step (currently the third step) so you couldn't configure the location of your application entries. The location used was the Data page right under the application home page.

Before 7.4M1

The application wizard was creating a custom live table results page (e.g. Holiday RequestLiveTableResults) in order to load the live table translations on demand. Starting with 7.4M1 the translations are loaded on wiki or user scope (based on user rights) and thus we don't need this page any more.

Before 7.3-rc-1

Each application is split into 2 XWiki spaces. If your application is named 'Meeting Manager' then your application's data pages will be stored in the space named 'Meeting Manager' (i.e. the space with the same name as the application) and your application's code pages will be stored in the space named 'MeetingManagerCode' (i.e. the name of the application, minus some special characters such as whitespace, plus the 'Code' suffix).

Before 6.2-milestone-1

Each application corresponds to an XWiki space. Both the application's code documents (class, template, sheet, translations, etc.) and the application's data documents (the entries created by the users) are stored in the same space (the space with the same name as the application).


Starting with version 4.5 the AppWithinMinutes wizard generates a document translation bundle for the application which allows you to translate class field pretty names, list values (for static list fields) and live table columns names. If you have an application that was created with an older version of AppWithinMinutes you just have to edit and save it to get the new translation bundle.

If your wiki is setup for multilingual support then on the application home page, in the application menu, you have an entry to translate the application. The link takes you to the document translation bundle which is a wiki page so it can be translated in other languages like any other wiki page.

When editing an application you have the option to update the translation bundle. Note that for the moment the translation bundle (its default language) is regenerated so you may lose translation keys you added yourself. In the future we plan to update the translation bundle preserving the custom keys you add.

See the application internationalization guide and the localization module documentation on how to use translation keys in scripts within your application.

Live Table

The live table offers many configuration options that are not available when editing your application. You have to edit the application home page in wiki edit mode to be able to use all the available configuration options.

Post Processing

You can execute code after an application entry is created/edited by using the notification system. Here's an example where the title of a page is adjusted after the page is created/edited.

Color theme

The color theme of your application can be changed from the administration section of your application's data space. Use the 'Space' > 'Administer Space' top menu, then follow 'Look & Feel' > 'Presentation' section.

Field Palette

The field palette from the class editor (second step of App Within Minutes wizard) can be customized easily. You can control both the list of field categories and the list of field types from each category. Field categories are determined by AppWithinMinutes.FormFieldCategoryClass. It's enough to add an object of this class to a wiki page to make it a field category. As you'll see this class has only one property, the priority, which specifies the position in the list of categories on the field palette. The category title is actualy the title of the wiki page.

Field types are determined by AppWithinMinutes.FormFieldClass. Before you add a new field type you need to create a new XClass property type because normally a field type is mapped to a property type as we've shown above. Supposing you have created the "External Image" property type (as explained in the linked tutorial) let's see how we can add a field type based on it.

First of all you need to create a new wiki page. The title of this wiki page will be the title of the new field type and thus will appear on the field palette. We'll use "External Image". Next you need to add an object of type AppWithinMinutes.FormFieldClass to the page we've just created to let App Within Minutes know that this page describes a field type.


You need to specify:

  • the field category
  • the icon that will appear on the field palette before the field title; you can choose an icon from the Silk icon set, as you can see in the image above, or you can attach an icon to this wiki page and put the file name in the icon input
  • the priority, which is the index inside the specified category on the field palette
  • the list of editable meta properties of the corresponding property type; these are the configuration options that you will get for this field type

Save and edit this page using the class editor. We now have to define a template for the "External Image" field type. To do so you just have to add a property of type "External Image" and set the meta properties to the default values you'd like to have when you drag an "External Image" field from the palette to the field canvas in the class editor. Basically, this property template will be copied whenever you add a new "External Image" field to your application.

Save and you're done. Now let's create a new application, or you can edit an existing one. In anycase, you should see the "External Image" field added to the field palette under the right category.


Add an "External Image" field to your application and look at the field configuration. You'll see the configuration options that you have listed previously in the AppWithinMinutes.FormFieldClass object.


Rights Configuration

Disable Access to the App but Allow to Create Entries from Another Space

From App.WebHome, go to Administer Page, Users & Rights, Rights: Page & Children.
Change the Rights there, for example, check View Rights for XWikiAdminGroup only.

Once done, for all the pages listed below, enable View rights for XWikiAllGroup:

  • App.Code.AppTemplate
  • App.Code.AppTemplateProvider
  • App.Code.AppSheet

Get Connected