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


This page covers:


Process Builder in Amp Impact

Amp Impact has two process builder templates: “Copy Objective Field Values onto Project Objective” and “Copy Indicator Field values onto Project Indicator”.

By default, these processes are active on installation and can be customized or deactivated based on your organization’s use case.

The following process builders have been deprecated Kalausi Release onwards. They have been replaced by Flows. You can find more information about the replaced flows here. Due to a Salesforce limitation these process builders will be available in orgs installing Kalausi (v1.34) or a version after that, but will be marked deactivated.

Please refer to the Upgrade Instructions if you’re upgrading to Kalausi from a previous release.

Amp Impact Automation (Process Builder) 

Object

Process API Name

Actions

Process Summary 

Framework Objective

ampi__Pull_Objective_Level_onto_Project_Objective

Sync after creation

This process gets triggered when an ampi__Objective__c record is created. It syncs the field values of the ampi__Catalog_Objective__c with ampi__Objective__c field values.

Project Indicator

ampi__Copy_Indicator_Field_Values_Onto_Project_Indicator

Sync after creation

This process gets triggered when an ampi__Project_Indicator__c record is created. It syncs the field value of the Parent Catalog ampi__Indicator__c with ampi __Project_Indicator__c field values.

Risk 

ampi__Populate_Risk_Level

Populate Risk Level

The process updates the ampi__xx_Risk_Level__c field based on a comparison of the value of the ampi__xx_Overall_Score__c to the Risk Setting Custom Metadata Type.


Customize Process Builder

Amp Impact has the following process builder templates:

  • Copy Objective Field Values onto Project Objective. This copies the value in the following fields on ampi__Catalog_Objective__c to the corresponding fields on ampi__Objective__c:

    • ampi__Description_Language_1__c

    • ampi__Description_Language__2

    • ampi__Description_Language_3__c

    • ampi__Description__c

    • ampi__Name_Language_1__c

    • ampi__Name_Language_2__c

    • ampi__Name_Language_3__c

    • Name

    • ampi__Level__c

The Name field on ampi__Catalog_Objective__c is copied into the ampi__Label__c text field on ampi__Objective__c, as the standard Name field on ampi__Objective__c is an auto-number and cannot be updated.

  • Copy Indicator Field values onto Project Indicator. This copies the value in the following fields on ampi__Indicator__c to the corresponding fields on ampi__Project_Indicator__c:

    • ampi__Active__c

    • ampi__Calculate_Total__c

    • ampi__Cross_Disaggregation_By_Sex__c

    • ampi__Cumulative__c

    • ampi__Data_Source_Language_1__c

    • ampi__Data_Source_Language_2__c

    • ampi__Data_Source_Language_3__c

    • ampi__Data_Source__c

    • ampi__Indicator_Definition_Language_1__c

    • ampi__Indicator_Definition_Language_2__c

    • ampi__Indicator_Definition_Language_3__c

    • ampi__Indicator_Definition__c

    • ampi__Disaggregation_Group_Language_1__c

    • ampi__Disaggregation_Group_Language_2__c

    • ampi__Disaggregation_Group_Language_3__c

    • ampi__Disaggregation_Group__c

    • ampi__Exclude_From_IATI__c

    • ampi__Geographical_Disaggregation__c

    • ampi__Guideline_Language_1__c

    • ampi__Guideline_Language_2__c

    • ampi__Guideline_Language_3__c

    • ampi__Guideline__c

    • ampi__Notes__c

    • ampi__Red_Yellow_Threshold__c

    • ampi__Yellow_Green_Threshold__c

    • ampi__Reporting_Frequency__c

    • ampi__Target_Frequency__c

    • ampi__Targets_Are_Disaggregated__c

    • ampi__Type_Of_Results__c

    • ampi__Units_Language_1__c

    • ampi__Units_Language_2__c

    • ampi__Units_Language_3__c

    • ampi__Units__c

    • ampi__Validation_Range_Maximum__c

    • ampi__Validation_Range_Minimum__c

The process builders have been enabled as a template. Therefore, if you want to edit them to meet your organization’s specific use case, you can clone the process, make the required changes in the cloned process, and activate the cloned process.


Deactivate Process Builder

To deactivate any of Amp Impact’s Process Builders, go to the Setup Quick Search box and search for “Process Builder”. Expand the process builder and click “Deactivate” next to the Active Version.


  • No labels