File Menu

File menu actions enable you to manage Interactions within the file system. The options are listed and described in the following table.

Option

Toolbar Icon

Description/Notes

New

IconCreateNew

Creates a new Interaction. For details, refer to Creating Interactions.

Open

IconOpen

Opens an existing Interaction (i.e., an Interaction saved on a local disk).

Open template

N/A

Opens an existing Interaction template.
A template is a reusable Interaction with default items already defined. When a template is saved as a new Interaction, the behavior of the template is inherited by the Interaction.

Open recent

N/A

Opens an Interaction that has recently been worked on. Users can select from a list of up to 10 recently created/opened Interactions.

Close

N/A

Closes the currently displayed Interaction. If there are unsaved changes, you will be prompted to save them.

Print

N/A

Prints plain language reports, such as the Procedure and Specification reports.
Currently, the Print option does not support printing of the Interaction itself. You can print Interactions using the Export Interaction option.

Export specification

N/A

Exports the Specification report as a Word or HTML document.

Export procedure

N/A

Exports the Procedure report as a Word or HTML document.

Export Interaction Map

N/A

Exports an Interaction as a .png file to your local file system. The image can then be opened using a variety of desktop publishing and image tools, and printed or otherwise manipulated for presentation.

Save

IconSave

Saves the current Interaction to the file system.

Save as new

N/A

Saves an Interaction as an entirely new version (clone) of a current Interaction, with unique identifiers assigned to the new Interaction. This avoids overwriting issues when Interactions are published.

Save as template

N/A

Saves an Interaction as a reusable Interaction with default items already defined. The template can then be used to create new Interactions as unique clones.

For example, users can create an Interaction with some complex database behavior, and save it as a template. Each time there is a need to reuse that complex behavior, a new Interaction can be created from the template, avoiding the need to reproduce the complex behavior.

Exit

N/A

Closes the Designer. If there are unsaved changes in any Interaction, you will be prompted to save them.
If the application exits unexpectedly or without saving changes, users have the option of restoring lost changes from a local cache when the Designer is opened again.