Recommendations for creating an application

Getting started with creating an application is kept as simple as possible with the automatic checks and test mode included in the app generator. The implementation of a simple application can be done without much preparation. For more complex applications, it is recommended to model the associated process beforehand.

During the configuration of the application, it is possible to switch between the configuration screens at any time in order to make changes to the existing configuration.

At the beginning of the configuration, the basic content blocks - and thus the building blocks of the form - are created in the Data and Views tab. Subsequently, the obvious fields are entered, whereby the access restrictions on block level can still be ignored.

After the first draft for the form design has been created, the necessary statuses are created in the Workflow tab and linked to each other with transitions. Here, too, the restriction of the editing rights of the statuses and transitions can be dispensed with for the time being.

In the Overview tab, the necessary tabs for the application are created and configured. Subsequently, the table and the filters are maintained. 

At this point, most of the application is configured and the editing and viewing rights in the statuses, transitions and form items can be entered. 

• In general, it is recommended to keep Q.wiki as open and accessible to all users in the organization as possible. Nevertheless, there are use cases where sensitive data is processed and requires special protection. In this case, the access restrictions per content block or under Overview -> Basic the global access restriction are activated and configured.

Under Overview -> Basic, the texts are individualized and necessary other settings are made.

After checking the configuration errors and possible problems, it is recommended to perform a test run and run through the intended usage scenario in the test application.

It is quite common to switch between configuration screens several times during configuration, just as several iterations of the test mode of a configuration are run through before the application is finalized. During this discovery phase, a wide variety of configurations can be tried out and undone without affecting the final application.

In case of difficulties with the configuration or complexity of an application, the consultants of Modell Aachen GmbH are available to support the implementation of the individual use case in the best possible way.