Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


This page covers:


Once an organization finalized its logical framework, they have the option to create the Framework Objectives for each level in its logical framework in Amp Impact. This forms the backbone of impact measurement and ultimately, allows them to link Project Indicators to their Framework Objectives.

Here is an example of a framework that an organization is using to track progress toward its objectives:

You’ll notice that they:

  • Defined a hierarchy of objectives that are nested in this list (Impact > Outcome > Output > Activity);

  • Connected their Indicators to various objectives to track progress toward their goals;

  • Are automatically aggregating indicator target and result data in this table to track their overall progress.

Now, let’s get into the step-by-step data entry process.

There are three ways to add objectives to a framework (i.e. create Framework Objective records):

Create Custom Framework Objective records

Add Framework Objectives from a catalog

Clone a Framework from another Amp Impact Project

Create Custom Framework Objectives

  1. Navigate to the “Frameworks” tab located in your system’s Amp Impact Project tab. The naming could differ depending on the configuration in your system (for example, it could be called “Results Framework”, “Logframe”, “Logical Framework”, or something similar). Click on the “Add Custom Framework Objective” button.

  2. Complete the fields in the pop-up below:

Here are a few considerations when creating custom Framework Objective records using the pop-up:

  1. The “Objective Name” field will be visible to users on the framework you create.

  2. You can choose if you’d like to add this objective to the catalog for other users to add to their frameworks. See the Add Objectives from a Catalog to the Framework section below.

  3. Values for the “Description” field cannot include semicolons (;) to preserve the functionality of search filters for the ampi__Objective__c field.

  4. Once you click “Save” on the pop-up, an Objective record as well as a Project Objective junction
    record is created.

  5. If you’re creating an objective hierarchy, the Project Objective cannot be its own Parent Project Objective.


Add Framework Objectives from a Catalog

xx


Copy Framework Objectives from Another Framework

Often organizations use the same (or similar) frameworks across their projects or initiatives. Instead of creating or adding the same Framework Objectives to the new Project Framework, Amp Impact allows users to simply clone a framework from one project to another.

Framework Objectives can only be cloned from another Project Framework if the ManageFrameworks Lightning Web Component is used. If you don’t have this option, you might be using the manageFrameworks Visualforce Page. Check with your System Administrator.

  1. Once again, you can navigate to the “Frameworks” tab located in your system’s Amp Impact Project tab. The naming could differ depending on the configuration in your system (for example, it could be called “Results Framework”, “Logframe”, “Logical Framework”, or something similar). Click on the “Copy From Another Framework ” button on the top right to launch the wizard for copying Framework Objectives.

Select a Project and Framework to Copy Framework Objectives From

The “Copy From Another Framework” wizard will guide you through the process to select and copy Framework Objectives to your new Project Framework.

  1. Select the Amp Impact Project and Project Framework to copy Framework Objectives from.

    1. Only those projects that have related framework(s) or framework objective(s) are available for
      selection in the ‘Select A Project’ type ahead box. Additionally, only those frameworks that have
      related framework objective(s) are available for selection in the ‘Select A Framework’ type ahead box.

    2. To select a framework with linked objectives but no association to a project, leave the ‘Select A
      Project’ type ahead box empty and select the desired framework from the ‘Select a Framework’ type ahead box.

    3. To select a project with linked objectives but without any linked framework(s), leave the ‘Select A Framework’ type ahead box empty and select the desired project from the ‘Select A Project’ type
      ahead box.

Select the Appropriate Framework Objectives

Admin Note:
To customize the columns displayed in the ‘Select Framework Objectives’ table, edit the fields in the ampi__SELECT_FRAMEWORK_OBJECTIVES_TO_COPY fieldset in the ampi__Objective__c object.

  1. Once you’ve selected a project and framework, click “Next” to see the list of objectives. Select the appropriate Framework Objectives by checking the relevant boxes.

Indicators linked to Framework Objectives:

  • Please note that the ‘Copy the Indicators related to selected Objective(s)’ is deactivated if none of the objectives have any related project indicators.

  1. However, if there are project indicators linked with the framework objectives, the user can select the checkbox as shown in the below screen and click on the ‘Next’ button.

  1. The ‘Select Project Indicators’ screen will appear within the pop-up on clicking ‘Next’, displaying a

list of project indicators linked with the objectives selected in the previous screen.

Admin Note:
To customize the columns displayed in the ‘Select Project Indicators’ table, edit the fields in the
ampi__SELECT_PROJECT_INDICATORS_TO_COPY fieldset in the ampi__Project_Indicator__c object.

  1. By clicking on the checkbox associated with each indicator, the user can select the project indicators to copy.

10. Clicking on ‘Save’ will successfully copy, both, the selected objectives and their linked project
indicators into the user’s current framework
For more information on Copying Framework Objectives, please refer to the Manage Frameworks User
Guide.

Admin Note:
To customize the labels and help text values displayed on all the screens within the pop-up, edit the
relevant custom labels from the ‘Setup’ menu. Please refer to the Manage Frameworks User Guide
for the list of custom labels.

Manage Framework Objectives for a Single Framework

  1. After a logframe item has been created, users can edit or delete the item by clicking on the pencil
    icon or garbage icon respectively.

  1. Deleting a project objective removes the record from the logical framework. If the deleted item had

any relationships (for example, to an Activity and/or Project Indicator), which are displayed on other
pages, those will also be deleted.

  1. Clicking on the Pencil icon prompts the edit framework item popup to display. On this interface,

users can:

a. Add/modify/remove information about the logframe item
b. Deactivate the item. Choosing this action allows the user to remove the project objective
from the logical framework without deleting the record. A logframe item can be
deactivated by checking the field ampi__Deactivate__c.

  1. Objectives can look up to other Objectives, which creates a hierarchy represented with nesting, i.e. a

parent Objective will be left-justified, and its immediate child Objectives will be indented once from
the left.

10. Objectives are ordered alphabetically at their hierarchical level, i.e. all parent Objectives are
alphabetized, and their immediate child Objectives are alphabetized only within the parent
Objective.

11. A chevron displays to the left of any Objective with at least one child Objective. On click of the
chevron, users can toggle the display of an Objective’s child Objectives by either collapsing or
expanding those nodes.
12. If any of those child Objectives also have grandchild Objectives that are collapsed or expanded,
those states are preserved on collapse and re-expansion of the grandparent Objective.

13. At the top of the table next to the Framework Item column header, there is an action link which
reads as either “Expand All” or “Collapse All”. A user can click “Expand All” to view all Objectives,
including their child Objectives and grandchild Objectives, in the table.

14. A user can click “Collapse All” to hide all Objectives in the table except for the ones that do not
have a parent Objective (that is, the highest level of Objectives).


Admin Note:
The ‘Copy From Another Framework’ button will be hidden if no framework exists on the project. To
hide the button manually, you can select the ‘Hide Copy from Another Framework button’ design
attribute checkbox.

  • No labels