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 2 Next »

This page covers:

Create Project Indicator records from the Indicators Catalog tab

On the ManageIndicators page is a tab labeled, ‘Indicators Catalog.’ This tab allows users to view a list of standard indicators that can then be added to multiple projects, see the screenshot below. This catalog can be set-up by uploading the indicators using a tool such as dataloader.io and can streamline project setup and facilitate better reporting and aggregation of data.

Within the Indicators Catalog, users may browse through all Indicator records in a table format.

  • The table displays each record in the first column as a hyperlink and is clickable to the
    record detail.

  • By default, catalog indicators are displayed according to Indicator Definition.

Admin Note:
To customize the display of specific fields within this table, speak to your System Admin. Fields may
be added to the Indicators Catalog Table by navigating to the CATALOG_INDICATORS_TABLE field set on the Indicator__c object.

  • The table will display all Indicator records which do not have a child Project Indicator record related
    to the current Project.

  • By default, Indicators in the Indicators Catalog are sorted alphabetically according to Indicator
    Definition.

Create custom Project Indicator records from the Selected Indicators tab

Create custom indicators for the current project and manage indicators that have already been added to the project.

When the Add New Custom Indicator button is clicked, a pop-up opens.

This pop-up displays the fields in the ADD_NEW_INDICATOR_POPUP field set on the Indicator object.
You can use the field set to control which fields are displayed in the pop-up for the user to enter
information on while creating the new project indicator.

When creating a new Project Indicator, certain fields are required to ensure the Indicator is accurately
created in the Project. All new Project Indicators require an Indicator Definition, Data Type, Reporting
Frequency and Geographic Disaggregation. All other attributes for a Project Indicator are voluntary but
users can add new required fields to the field set per their organization’s requirements.

Admin Note:
If the System Admin has defined default values for custom or out of the box fields on
ampi__Indicator__c, then the default values will be automatically populated when the user creates a new custom ampi__Project__Indicator__c using the Add New Custom Indicator pop-up and when the user adds an ampi__Indicator__c to the current ampi__Project__c using the Indicator Catalog tab on Manage Indicators page.
Note that some fields have default values predefined out of the box:
● ampi__Include_In_Catalog__c = TRUE
● ampi__Red_Yellow_Threshold__c = 75
● ampi__Yellow_Green_Threshold__c = 100

On the ‘Add New Custom Indicator’ popup is a field labeled ‘Include in Catalog?’ This checkbox field controls the availability of the Indicator to the projects created. When creating a custom Indicator, the Indicator can either be:

  • Added to only the current Project (ampi__Include_in_Catalog__c = FALSE)

  • Added to the current Project and made available to all other Projects (ampi__Include_in_Catalog__c = TRUE)

  • By default, the field ampi__Include_in_Catalog__c is selected as TRUE (that is, it is checked), which adds the Indicator to the Selected Indicators table for the current project and the Indicator Catalog for all other projects.
    ○ If the field is FALSE (that is, it is unchecked), the Indicator will only be added to the Selected Indicators table for the current project. If this indicator is later removed from the project, then it will display in the Indicator Catalog for that project only, and it does not display in the Indicator Catalog for any other projects.
    ○ In order to change the value of the field ampi__Include_in_Catalog__c for a particular indicator, a user must open the indicator record in native Salesforce. The value in this field may not be changed by editing a project indicator via ManageIndicators page. The data load on MI page is only affected by Indicator records where ampi__Include_In_Catalog_c = TRUE. e.g. If there are 200 Indicators but only 100 indicators have ampi__Include_In_Catalog_c = TRUE, then only those 100 indicators contribute to data load.

When the user clicks Save:

  • A new Indicator record is created with the input data.

  • A Project Indicator record is created child to the current Project and the newly created Indicator
    record.
    ○ Applicable junction records, like ampi__Project_Indicator_Geographic_Area__c and
    ampi__Project_Indicator_Reporting_Period__c, are created.
    ○ If certain fields like Disaggregation_Group__c are populated, then a new junction record
    Disaggregated_Project_Indicator__c is created.

Add Project Indicators to ManageFramework Table

After following the above instructions on adding Indicators to a Project and then associating them with one or more Objectives - Make sure that the Objectives field is added to the (i) Add New Project Indicator pop-up through the ADD_NEW_INDICATOR_POPUP field set on Indicator object and (ii) the Edit Project Indicator pop-up through the EDIT_PROJECT_INDICATOR_POPUP field set on Project Indicator object. This will allow users to tag Project Indicators with the relevant objective(s).

When a logframe item is deactivated (see Step 8 on Frameworks: Set Up and Manage Objectives in Frameworks for more instructions on deactivating logframe items), it will no longer appear as an available project objective to associate with Project Indicators in the Add New Indicator Popup and Edit Project Indicator Popup.

If the objective was already associated with a Project Indicator, it will display in the Selected Indicators
table.
Once a Project Indicator is associated with an Objective, that Project Indicator will appear next to the
related Objective in the Framework Table. A Project Indicator can be related to multiple Objectives and
will appear adjacent to all related Objectives.

Likewise, multiple Project Indicators can be associated with a single Objective, and all Indicators will appear adjacent to that related Objective.

Add Project Indicator-related Data to ManageFramework

Once a Project Indicator is associated with an Objective and displayed in the Framework table, the user can display additional information related to the Project Indicator. To add/remove fields from the Project
Indicator object, refer to the ‘Customize Field Sets’ section of the Installation Guide.

Some fields to add/remove include:

  • Baseline: Actual results that were in place at the time a project started. This data is used as a
    comparative point when collecting results.
    How to populate this field: This number field is populated in the Edit Project Indicator pop-up on the
    ManageIndicators page. Ensure the field has been added to the field set if it doesn’t display in the
    pop-up initially. This is relevant only for currency, number, and percent indicators. This field sits on
    the project indicator object to allow users to enter baseline information for the indicator depending
    on the project.

  • Life of Project Target: The target to be met by the end of the project.
    How to populate this field: This number field is populated in the Edit Project Indicator pop-up on the
    ManageIndicators page. Ensure the field has been added to the field set if it doesn’t display in the
    pop-up initially. This is relevant only for currency, number, and percent indicators.

  • Target to Date: Result records pulled from the SetTargets page. This field is on the project indicator
    object to allow users to enter a target for the indicator depending on the project.

  • Result to Date: Result records pulled from the AddResults page.

To populate the Target to Date and Result to Date fields, the user has to first indicate if the Project
Indicator’s data is collected in a cumulative or non-cumulative manner.

  • No labels