Importing Scenarios in Production FAQS

1. What is the purpose of importing a scenario into a different repository?
• Importing scenarios into a different repository allows you to deploy scenarios in a new environment or site, typically from a development repository to a production or execution repository.
2. What are the two methods of importing a scenario?
• The two methods for importing a scenario are:
1. Standard Import: Imports the scenario and its attached schedules.
2. Import Replace: Replaces an existing scenario with the exported scenario, deleting existing sessions, scenario reports, and schedules, and replacing them with those from the export file.
3. Can I import a scenario into both development and execution repositories?
• Yes, you can import scenarios into both types of repositories, but:

• In a development repository, you can use Designer or Operator Navigator to perform the import.
• In an execution repository, only the Operator Navigator can be used to import scenarios.

4. What happens to schedules when importing a scenario?
• During the standard import process, you can choose to import the schedules attached to the exported scenario. However, when using Import Replace, the schedules from the original scenario are deleted and replaced with those from the export file.
5. What does the "Import Replace" method do?
• The Import Replace method completely replaces an existing scenario with the exported content. It preserves references from other objects to the scenario but deletes the sessions, scenario reports, and schedules associated with the original scenario.
6. Can I use version control when importing scenarios?
• Yes, scenarios can be deployed and promoted to production using versions and solutions. For more details, refer to the section on Using Version Control (Legacy Mode).
7. What tools are required for importing scenarios in the development and execution repositories?
• In a development repository, you can use Designer or Operator Navigator for importing scenarios.
• In an execution repository, only Operator Navigator is available for importing scenarios.
8. What happens to the original scenario when using Import Replace?
• When using Import Replace, the original scenario is replaced, and sessions, scenario reports, and schedules from the original scenario are removed. The export file's schedules will be imported instead.
9. Can I import scenarios without affecting their references from other objects?
• Yes, when using Import Replace, references to the imported scenario from other objects are preserved, but the associated schedules and session data are replaced by those from the exported scenario.