This page covers:
Once an organization finalized its logical framework, they have the option to create the objectives for each level in Amp Impact. This forms the backbone of monitoring and evaluation processes and allows them to link indicators to their logical framework objectives.
Create and Manage Objectives for a Project
From the ManageFramework page, a user can create new objectives and add them to a project by
clicking the “Add New Framework Item” button on the top right of the Framework page.A pop-up will appear with Objective fields for the user to fill out.
Admin Note:
Values for the Description fields cannot include semicolons (;) to preserve the functionality of search filters for the ampi__Objective__c field.
3. When a user clicks “Save” on the pop-up, an Objective record and a Project Objective junction
record are created.
4. If there are any help texts for the fields added to the Add/Edit Framework Objective popup, then a
user can view them by hovering over the info icon.
5. Note that a Project Objective cannot be its own Parent Project Objective, as this violates hierarchy
rules. The Lookup field allows associate users to associate a Project Objective with another that
does not directly or indirectly refer to itself.
6. After a logframe item has been created, users can edit or delete the item by clicking on the pencil
icon or garbage icon respectively.
7. 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.
8. 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.
9. 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).
