Show TOC

Function documentationContexts Locate this document in the navigation structure

 

Contexts represent a named collection of certain application objects, grouped so that users in application groups can access the set of objects as a unit in the application.

Context administration involves creating and maintaining contexts, and defining the fundamental aspects of the context, including the name, objectives to use, and the application groups who can access the context. You can also define other features listed below.

A context represents the full set of components or a subset of components, depending on the way you set it up. For example, you may implement a strategy with initiatives but not the scorecard or reports.

Use the Contexts section to assign the components, control the order that perspectives and objectives appear in the application, and optionally override a perspective's or objective's description for a context (while keeping the original description intact in the master list of perspectives and objectives).

Prerequisites

After you create perspectives and objectives in the library, the next step is to create a context that uses some or all of those perspectives and objectives.

You are an administrator or a user assigned to an application group with Create/Edit Contexts permissions. If Contexts is unavailable to you, it means you do not have the correct permissions.

Features

Context administration has the following features:

  • You create, rename, modify, and delete contexts.

    For more information, see Context Development.

  • You can facilitate the creation and maintenance of many identical or similar contexts by creating context templates and then basing new contexts on that template. Use this feature to create a large numbers of scorecards (contexts) within a deployment.

    For information, see Context Development Using Templates.

  • You pick objectives from the library to be used in the context.

    For more information, see Objective Selection and Perspective and Objective Library Development.

  • You assign application groups to the context. An application group is a named set of users who are known to the application. Once you assign an application group, the users in the group can begin to use the context in the application. These users have a particular view of the context that is based on the tabs and permissions assigned to the application group using the Manage Application Groups link in the Administration section.

    For more information, see Application Group Assignments.

  • You can set the display order for perspectives and objectives to appear in the application. If you do not set the display order, perspectives and objectives appear in alphabetical order.

    For more information, see Perspective and Objective Ordering.

  • (Optional) You can select one public report set and one public dashboard to be associated with this context. By selecting reports and dashboards for a context, they become available to users in the application. When users in the assigned application groups select the context and then access the Reports or Dashboards component, they see the public reports and dashboard selected for that context.

    For more information, see Report and Dashboard Selection.

    Note Note

    Reports, report sets, and dashboards are created in the application.

    End of the note.

  • You can modify the definitions of perspectives and objectives for a context while keeping the original definitions intact in the library. If you were to use the perspective or objective in another context, the original definitions would be used. You can modify descriptions, responsible users, and associated links. You can also change the perspective type between internal, external, or no perspective type.

    For more information, see Perspective and Objective Description Overrides by Context.

  • You can add a message to appear in the System Message section of the Home component when the particular context is selected. Any user with access to the Home component in the application will see this message in the Home component.

    For more information, see System Message Implementation.