Change Envelope Build Environment

Use this procedure to change the build environment of a modeled form's envelope to another system code. The destination system code must reside on the same application instance, but not be within the same facility (dataset). 

This functionality is only used for systems on legacy architecture that has been set up with multiple environments per namespace (i.e. LIVE, BUILD, SAMPLE). It allows for envelopes built in one system to be changed to another for edits.

RADplus Utilities > Modeling > Change Envelope Build Environment

• The modeled form envelope can have only one build environment. When changing this environment, the component tables and component forms in the envelope build environment are also changed. The envelope can then only be changed from the new environment.

• If any components within the envelope are not defined in the target system, they are automatically copied.

• Locked dictionary values are transferred to the target system automatically.

• Only one user is permitted to edit any portion of the modeled form's envelope. 
  For example: if a specific envelope is selected for editing in this form, the following forms cannot be accessed by any other user for editing the envelope, tables, or associated forms.

  • For envelope editing: Envelope Definition, Change Envelope Build Environment, Envelope Merge, Envelope Export, Envelope Import

  • For table editing: Table Definition, Table Deletion

  • For form editing: Form Definition, Purge Form Data, Copy Form To Different System Code

Prerequisites:

• The user must be logged into the build environment (system code) where the envelope was created.

• Components in the envelope must be defined in the system code.

• The username and password used must be valid in the system code.

1. In the Select myAvatar PM Envelope screen, enter the envelope name, and click Ok.

2. In the Target System Code field, enter the system code of the destination system.

3. In the Target System Username field, enter your username in the destination system.

4. In the Target System Password field, enter the your password in the destination system. The username and password must be valid in the target system.
   Invalid combinations of System Code, Username, and Password are tracked as failed logins (see Failed Login Report).

5. In the If a component table or form is not defined field:

• Select Yes to transfer the values for any unlocked dictionaries to the User Defined file of the target system Dictionary Update form.
• Select No to leave out unlocked dictionary values when moving the build environment. New values will need to be added manually in the target system.

6. Click Submit.