Paid webs, in this case applications, can be created with the app generator. A detailed manual with useful information about the creation of individual webs is available at the following link: https://www.modell-aachen.de/de/buchung-workflow-generator

In Q.wiki the following web types can be created without changing the subscription:

• Process webs
• Knowledge webs
• Glossary webs

Below is the information that needs to be provided to Support to set up the new web.

Process webs

Name of the web

• Maximum 14 characters without special characters

Rights management

• Who is allowed to see the web and its contents?
• Who is allowed to create or change content in the web?
• Who is allowed to delete content?

        In each case as a group or list of users:

• Example for a group: HRGroup
• Example for a list of users: PeterTest, MaxMüller, RainerExample,...

Approval workflow

• No approval workflow: no further information necessary

    Each as group, user or metadata field of type user to define the approver:

• one-level approval workflow 
• two-stage approval workflow 
  • Approval level 1 
  • Approval level 2

Metadata

The following metadata is available by default in each process web:

• Title of the content
• Person responsible (if a approval workflow is used)
• Document type
• Scope
• activated standards from the standards assignments area

If additional metadata is to be provided, it must be listed in separate lines with field type, specification, and content, if applicable. Example: customer - multiple selection with tagging - customer A, customer B, customer C;

Possible field types are:

• Text - input of a free text
• User - input of exactly one user from Q.wiki, offered via auto-completion
• Multiple users - input of one or more users from Q.wiki, offered via auto-completion
• Selection from list - selection of a value from a list to be defined (specify selection options)
• Multiple selection from list - selection of one or more values from a list to be defined (specify choices)
• Multiple selection plus tagging - selection of one or more values from already existing keywords. If a keyword does not exist, the user can create it.

Knowledge webs

A detailed explanation of the knowledge webs can be viewed at the following link: https://www.modell-aachen.de/de/wissensbereiche.

At the end of the linked page, there is a form that supports the design of the knowledge area. With this form the requested configuration of a knowledge area can be sent to the support for implementation.

Glossary webs

Name of the web

• Maximum 14 characters without spaces and special characters

Rights management

• Who is allowed to see the web and content?
• Who is allowed to create or modify content in the web?
• Who is allowed to delete content?

        In each case as a group or list of users:

• Example for a group: HRGroup
• Example for a list of users: PeterTest, MaxMüller, RainerExample,...

Inclusion in process webs

• Should glossary terms and roles be underlined in other process webs? Yes/ No
• If there is more than one process web: Names of the process webs that should be included.