Search

Prepare Models for ALM

These examples illustrate how to prepare your existing models for management with Application Lifecycle Management (ALM) features. After following the steps, your development, test, and production models are structurally compatible, so changes can be promoted using Compare and Synchronize.

Choose the example that best matches your situation:

When you create a model from a revision, the new model is created in the workspace you're currently working in. Once created, you can import the model into a development, test, or production workspace. Production lists will not contain any data.

Example A: Application Still Under Development

Let’s say you’re in the process of building a development model. Once you’ve completed the initial build, do the following:

  1. In the development model, set all production lists and production imports (including import data sources) and then add a revision tag.
  2. If you want to use a test model:
    1. Create a test model from the latest revision tag in the development model.
    2. Enable deployed mode in the test model.
  3. If you don't need a test model, create a production model from the latest revision tag in the development model.
  4. Enable deployed mode in the production model.
  5. If applicable, use the options in Settings > Source Models to remap model-to-model imports.
  6. Make the production model available to end users.

Example B: Existing Production Application Consisting of a Production Model Only

Where there is a production model only, to introduce separate development and test models:

  1. Take the existing production model offline.
  2. Don't enable deployed mode yet.
  3. In the production model, set production lists and production imports (including import data sources) and then add a revision tag.
  4. Enable deployed mode in the existing production model.
  5. Create a development model from the latest revision tag in the production model.
  6. If needed, create a test model from the latest revision tag in the development model, then enable deployed mode.
  7. If applicable, use the options in Settings > Source Models to remap model-to-model imports.
  8. Bring the production model back online.

Example C: Existing Separate Development, Test, and Production Models

Where separate development, test, and production models already exist, to make your existing models compatible with ALM features:

  1. Take the existing production model offline.
  2. Don't enable deployed mode yet.
  3. In your production model, manually replicate any outstanding changes from your existing development or test models.
  4. In your production model, set all production lists and production imports (including import data sources) and then add a revision tag.
  5. Enable deployed mode in the existing production model.
  6. Bring the existing production model back online.
  7. Create a development model from the latest revision tag in the production model.
  8. Create a test model from the latest revision tag in the development model, then enable deployed mode.
  9. If applicable, use the options in Settings > Source Models to re-map model-to-model imports.

Your existing production model is now compatible with ALM. Changes can be promoted from the new development model using Compare and Synchronize.