App Generator: Parts of an application

Modified on Fri, 11 Aug 2023 at 09:55 AM

Applications can be individually designed and adapted to specific processes and usage scenarios. Nevertheless, there are overarching concepts that are identical in all applications.


This section describes from the user's perspective which functions and elements make up an application and how users can later work with it. An in-depth understanding of these functions is helpful in making the right decisions for designing the configuration.


Overview page

Basically, the overview page is divided into 3 sections:

  • Toolbar
  • Tab 
  • within the tabs, the elements in tabular form

In the function bar, a new element can be created and thus a new instance of the form can be filled in. Depending on the configuration, a new template can be created. The handling of templates is described in detail under Working with templates. If a task block is configured in the form, an overview of all tasks is provided. This is also accessible to users from the toolbar. Finally, the application can be configured directly via the three-point menu, if the corresponding rights are available. In addition, access to the app key figures is located there.


The tabs allow a filtered view of the elements. Thus, not all items, of all users across all statuses are displayed. Many apps will have configured tabs such as My Applications, Applications to be Approved by Me, All Applications, or similar manifestations. Basically, the tabs do not display items that are visible to the current user.


For those responsible for the application, another tab may be displayed for viewing deleted items. See: Restore deleted pages and files.


Within the tabs, a table is displayed for accessing the created content. The contents of the table vary from application to application. Depending on the configuration, a full text search is displayed above the table and one or more filters are displayed next to the table. Using these filters, even large amounts of content can be searched quickly. At least one column in the table contains a link to the detail view of an element.


Detailed view

The detailed view of an element (for example, an application) is also divided into three sections: 

  • Document header with the navigation
  • Content or the configured form
  • Document Steering

The document header shows the title of the page as well as the current status, the creator, the author and the date of the last edit. In the upper right area of the document header there are the buttons to return to the overview or, if the user has the necessary rights, to edit the page. The three-dot menu can be used to access PDF printing.


The actual form is divided into so-called content blocks. These are freely configurable and can be used in any number. Content blocks can be form blocks that request user input or offer selection options. The management of attachments or tasks is also mapped via separate blocks.

The content blocks are also subject to rights management. Depending on the configuration, not all blocks are visible to all users. Likewise, the editing of individual blocks can be restricted.


As in other applications in Q.wiki, the user switches to change mode via the Edit button and can edit the content.


With the document steering the page is moved in the workflow. A graphical timeline shows a representation of the last changes and status changes. Representation and function are identical to the document steering in the process area of the Q.wiki.



Translated with www.DeepL.com/Translator (free version)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article