When your application is released and in use by multiple users on a daily basis, it is generally best practice to create multiple servers so that development of the system can continue.

Typically a released application will at least have a development server and a production server.

The development server will be published to as new changes are being developed in WorkflowFirst. By having this as a separate server, it won't interfere with the users who are using the application on a daily basis.

The production server will be the application that users will be using on a daily basis. This will only be published to when the development release is stable and has been tested thoroughly.

Additional servers can also be created, such as a pre-production server (QA server) that can be tested by a QA team.

Other types of servers you can create include:

• Scenario server: This would have production data put onto it each morning. Users can use this to test out *potential changes* in data to see the impact without changing the actual production data.

• Training server: This would also have production data put onto it each morning, but the server itself will only be used by new employees as they are trained on using the system. If they make a mistake, the mistake will not affect the production data.

When publishing, you select the server to publish to using the "Target Server" dropdown on the publish form. It may also be advisable to set up an email notification to occur whenever a publish occurs, so relevant people can be notified when production it updated.

The next section will detail how to create multiple servers.