Module Generator: Test and release configuration change

The Module Generator checks your configurations for errors and logical gaps. While it's simple to use, the processes you model are often very complex – and so are the configurations.

The publication process differs depending on whether you're publishing a new module or modifying an existing one in production. Both scenarios are explained here.

Scenario 1: Publishing a new module

After you create and set up a new configuration, publishing works like this:

1. Check your configuration for errors and issues. You'll see these during configuration in the symbol at the top right – see Configuration errors and issues. You can ignore issues, but you must fix errors before you proceed.
2. Test your module: In the main navigation, click Test configuration. A new browser tab opens with a test version of your module. It's visible only to you and is automatically deleted after 24 hours. You can share the test link with other project members so they can help test.

Once testing is successful, publish your configuration: Click Create module. You'll see how this affects your module quota. If no free modules are available, you cannot publish the new module.

Scenario 2: Modifying an existing production module

When you modify an already productive module, the first steps are the same: check your configuration and test it in a temporary test version. However, the rest of the process is different:

• Confirm all required data migrations before proceeding.
• Start migration mode: The module becomes read-only and displays a message to your users. Once no active work is being done in the module, data migration starts automatically. After completion, the module becomes writable again and the message is removed.

For detailed information on this scenario, see Modifying a production module.

Related articles

• Configuration errors and issues
• Modifying a production module