Although the Multi Environment feature is designed for flexibility of use, Jacada suggests that you follow recommended guidelines to get the greatest benefit from your enhanced account. This article provides best practice recommendations for the following scenarios:

Note: Multi Environment accounts are currently supported only in the web-based Interaction Designer.

Managing a Routine Development Cycle: Best Practice

In a routine development cycle, it is recommended that deployment progress linearly, from DEV to TEST to PROD. The best practice workflow (illustrated in the diagram below) is:

  1. Develop new Interactions and all required resources (including creation and definition of environment variables) in the DEV environment. 
  2. When development is closed, deploy the Interactions and resources from the DEV environment to the TEST environment. 
  3. In the TEST environment, test the new resources in Locked mode. If bugs are discovered, switch to Editing mode, perform fixes, and then test again in Locked mode.
  4. When all testing is complete, deploy the resources to the PROD environment.

For more information about working in the different modes, refer to The Multi Environment Setup. For details about deployment, refer to Performing Deployment in the Multi Environment Setting.

Handling Production Defects: Best Practice

If a defect is found in production, it is recommended to perform fixes in the TEST environment, and then to re-deploy the fixed version to PROD. This practice ensures that development in progress in the DEV environment is not disrupted.

The best practice workflow (illustrated in the diagram below) is:

  1. (Optional): If warranted, in the PROD environment, perform a rollback to the previous version (the version in production before the defective version was deployed). 
  2. Switch the TEST environment to Editing mode and perform necessary fixes on the relevant version. Then, switch to Locked mode for testing. 
  3. When all testing is complete, deploy the resources to the PROD environment.

 

Revision:

Comments