Multi Environment accounts are provided with the following three out-of-the-box environments:

This article describes each environment in detail, and provides tips and best practices for working in the different environments.

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

Working in DEV 

This environment is set up to support efficient development and frequent changes in design:

  • A link for opening the Interaction Designer is provided on the left side of the Admin Console. 
  • All mechanisms for creating and updating resources (such as system variables, Integration Points, etc.) are available.

The figure below shows a sample DEV environment. Note that the Add button is enabled, and that environment variables are set to DEV values. 

 

Accessing the DEV Environment

By default, the DEV environment is presented upon login to the Admin Console. To return to DEV after working in other environments, select Dev from the environment selection dropdown. 

Deploying from the DEV Environment

When exporting resources from DEV, it is recommended to deploy to TEST and/or File only. This practices ensures that newly developed features are tested on a practice environment before deployment to production. For an example of deploying from DEV to TEST, refer to Performing Deployment in the Multi Environment Setting.

If a defect is found in production, it is recommended not to deploy back to DEV, but to instead perform the fix in the TEST environment. This practices ensures that development in progress in the DEV environment is not disrupted.

Working in TEST

This is a special environment designated for testing. The TEST environment is unique in that it can operate in either of the following modes:

  • Locked Mode: This mode simulates the PROD environment. All resources are read only. The only components that can be updated are values of system variables. In addition, you can add and update Interact Reports.
    Use Locked mode to test resources deployed from the DEV environment and to test bug fixes (when relevant). 
  • Editing Mode: This mode simulates the DEV environment, where resources may be added and updated. Use this mode to fix defective resources deployed back from the PROD environment.

By default, the TEST environment is in Locked mode, as shown in the following example. Note that the Add and Delete buttons are disabled, and the link to open the Interaction Designer is hidden.

The next example shows how the TEST environment looks in Editing mode. All resources are editable, and there is a link for opening the Designer. The pink banner at the top of the page provides a constant reminder that you are working in Editing mode.

Switching Between Locked and Editing Modes

It is recommended to always keep the TEST environment in Locked mode (the default mode), unless you need to create a production patch. When necessary, use the toggle button under the Jacada logo to switch between the modes.

To switch to Editing mode:

  1. At the upper left corner of the page, click .
    A confirmation popup opens.

  2. Click Yes.
    The TEST environment switches to Editing mode.

To switch to Locked mode:

  1. At the upper left corner of the page, click .
    A confirmation popup opens.

  2. Click Yes.
    The TEST environment switches to Locked mode.

Deploying to and from the TEST Environment

The recommended practice is to maintain your TEST environment in Locked mode for testing of packages deployed from the DEV environment. When testing is completed successfully, deploy the resources to the PROD environment. It is not recommended to deploy resources back to the DEV environment. 

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

Note: For successful deployment to and from TEST, the environment must be in Locked mode. 

For more information about deployment, refer to Performing Deployment in the Multi Environment Setting.

Working in PROD 

This is the dedication production environment, where no development or testing takes place. The Interaction Designer cannot be accessed from the Admin Console. Resources may not be created or edited. The only components that can be updated are values of system variables.  In addition, you can add and update Interact Reports.

Accessing the PROD Environment

To provide extra security for the exclusive production environment, Jacada Interact has the following built-in access restrictions for PROD:

  • Users who have a role of Agent or Designer are not allowed to access the PROD environment. 
  • Users must provide a password to access the PROD environment. 
  • Account administrators may restrict an individual user from accessing PROD by selecting the Restrict Production Access checkbox for that user. This checkbox appears on the New User page (when creating a new user), and on the User Details page. For example:

     

To access the PROD environment:

  1. At the upper left side corner of the page, from the environment selection dropdown, click Prod.
    The Identity Confirmation popup opens.

  2. Enter your password, and click OK.
    The PROD environment is displayed.

Deploying to and from the PROD Environment 

It is recommended not to deploy resources directly from DEV to PROD. After the resources have been thoroughly tested in the TEST environment, they can be imported to PROD.      

If a defect is found in production, it is recommended not to deploy back to DEV, but to fix the defect in TEST, and then re-deploy to PROD. This practices ensures that development in progress in the DEV environment is not disrupted. 

Revision:

Comments