Modify a Configuration

After you create, import, or open a Lasernet configuration, you can modify it in Lasernet Developer.

Use Lasernet Developer and Lasernet Form Editor

Lasernet Developer enables you to develop a workflow by adding modules, engines, modifiers, regional profiles, and other elements to the configuration. Form Editor enables you to create form designs, which a Form engine uses to generate output files or data according to that design (such as invoices in PDF format).

For more information about Lasernet Developer and Lasernet Form Editor, see the following guides:

• Lasernet Developer Guide

• Lasernet Form Editor Guide

When you use these tools to modify the configuration, your changes are synchronized with other users who are working on the same configuration.

Next Steps

After you make changes to the configuration, you should check the configuration for errors and test that it works as you expect it to.

Note

For an overview of the whole Lasernet configuration management process, see About Lasernet Configurations.

Validate the Configuration

To check the configuration for errors and warnings, you can validate the configuration.

Test the Configuration

Before you commit your changes (to create a new revision of the configuration), you should test that the updated configuration works as you expect it to.

Module Tester in Lasernet Developer

You can use the Module Tester feature of Lasernet Developer to test individual modules in the workflow.

For more information about the module tester, see the Lasernet Developer Guide.

Deploy Workspace

To test the entire workflow that the configuration describes, use the Deploy Workspace feature to deploy the content of the workspace to a test Lasernet environment. The workspace includes all the in-progress, uncommitted changes that you and other users have made to the configuration.

For more information about Deploy Workspace, see Deploy a Configuration to a Test Environment.

Commit and Deploy Commit

When the configuration has been tested and declared ready for use in a production environment, commit your changes to the configuration to create a new revision of it in the Config Server’s repository. For more information about committing changes, see Commit Configuration Changes to the Repository.

At an appropriate time, deploy the new configuration revision to the production Lasernet environment. For more information about using Deploy Commit to send a configuration revision to a production Lasernet environment, see Deploy a Configuration to a Production Environment.