Show TOC

Procedure documentationMailing a Strategy View Locate this document in the navigation structure

Prerequisites

You have a PDF Reader installed.

Procedure

  1. In the Strategy component, select the subcomponent you want to mail, either a Goal Diagram, Cause & Effect, or Themes or Pathways.

  2. Click Mail to display the Print & Mail Settings dialog box.

  3. Enter the values as shown in the following table:

    Field

    Description

    Include report name and annotation

    Includes the report name and annotation in the report.

    Title

    Type the name of the report or use the default report name.

    Annotation

    (Optional) Type a comment about this report. This comment will appear above the report.

    Include perspective and objective details

    Includes an extra page containing the perspective name, responsible user, and description.

    Include mission and vision description

    Includes an extra page containing the perspective name, responsible user, and description.

    Include pathways details

    Includes each pathway name, description, responsible user, and pathway peak date, as well as the Pathway diagram if you are mailing from the Pathways component. Also included for each pathway is each objective name, description, responsible user, and associated perspective.

    Include link to Strategy Management

    Includes a Go there now link in the attached report.

    Portrait or Landscape

    Controls whether to lay out the report in portrait or landscape.

  4. Click OK.

  5. At the information box that explains how to send the email, click OK.

  6. Send the email as directed in the message, and then close the browser window.

Result

The report is mailed as a PDF file attachment.

When the email recipient clicks the Go there now link in the attached report, the recipient will go directly to the live view in the appropriate component in the application. Users who click this link in the report must be strategy management users, must have access to the Web server where the application is installed, and must have access to the components and contexts being used in the view. Otherwise, that user will not have access to the live view.