Importing Scenarios in Production

1. Purpose of Importing Scenarios:
• A scenario generated from Designer can be exported and then imported into a development or execution repository.
• This operation is typically used to deploy scenarios to a different repository, which may be in a different environment or site.
2. Import Methods:
• There are two ways to import a scenario:
1. Standard Import:
• This method uses the standard object import process.
• You can choose to import schedules attached to the exported scenario during the import process.
2. Import Replace:
• This method replaces an existing scenario with the content of the export file.
• It preserves references from other objects to the scenario being replaced.
• Sessions, scenario reports, and schedules from the original scenario are deleted and replaced with those from the export file.
3. Importing Scenarios in Different Repositories:
• Development Repository: Importing a scenario is done through Designer or Operator Navigator.
• Execution Repository: Importing can only be done through the Operator Navigator.
4. Version Control and Solutions:
• Scenarios can also be deployed and promoted to production using versions and solutions.
• For more information on this, refer to Using Version Control (Legacy Mode).