Submissions: Customization Options

This page covers:

Related pages:

• 🔎 Submissions

• Submissions: Key Relationships

Set Up Submissions

The Submissions feature consists of six Lightning Components. In order to be able to use Submissions in Amp Impact, your Salesforce instance will need to be in Lightning Experience, and MyDomain will need to be set up in your Salesforce org. For more details, please see Salesforce’s documentation on how to set up MyDomain.

(Optional) Field Sets: Customize Pop-ups to Create/Edit Sections and Questions in Submissions

Section (ampi__Section__c) and Question (ampi__Question__c) are two Amp Impact objects that are used to customize Submission templates, populate Submission responses, and score responses. Each object has a Field Set that controls the display of the respective pop-up windows to add or edit records.

Add/Edit Section pop-ups - fields displayed on the “Add New Section” pop-up and the “Edit Section” pop-up

• Object: Section_

• Field set name: Add_Edit_Section_Popup

• Unsupported field types: Encrypted String, Multi-select Picklist, Time

Add/Edit Question pop-ups - fields displayed on the ‘Add New Question’ pop-up and the “Edit Question” pop-up

• Object: Question__c

• Field set name: Add_Edit_Question_Popup

• Unsupported field types: Encrypted String, Multi-select Picklist, Time

(Required) Assign Record Types on Profiles

The Submisson (ampi__Submission__c) and Question (ampi__Question__c) objects each have two Record Types. Since the Amp Impact package does not contain any Profiles, those Record Types must be manually assigned to each Profile that needs access to the Submission feature.

• ampi__Submission__c Record Types:

  • Template: Assign this record type to any Profile that needs to create or view submission templates.

  • Submission: Assign this record type to any Profile that needs to assign a submission to another user from a template, fill out a submission response, or review a submission response.

• ampi__Question__c Record Types:

  • Question: Assign this record type to any Profile that needs to create or view questions on a submission template.

  • Answer: Assign this record type to any Profile that needs to create a submission from a template, fill out answers in a submission response, or review answers in a submission response.

(Required) Assign Permission Sets to Users

Amp Impact provides three permission sets that should be assigned to users depending on how they will use the Submissions feature. The following table details each permission set and example users. For any custom permissions that need to be provided, clone the relevant permission set to customize the permission sets.

Follow these steps to ensure your Submissions Users can fully use the feature: 

1. Go to the Setup Quick Search box, and enter “Permission Sets”.

2. Open the Permission Set that you would like to assign to Users. This opens the Permission Set detail page.

3. Click the “Manage Assignments”  button in the top menu of the Permission Set detail page. This will load an assignment interface.

4. On the next page, click the “Add Assignments” button in the top menu. This will load a list of all Users in the org.

5. Select the checkbox next to each User to whom you want to assign the Permission Set. Once all relevant Users are selected, click the “Assign” button.

6. Click Done

Customize Submission Objects, Lightning Pages, and Components

The Submission feature involves three objects, three Lightning pages (on the ampi__Submission__c object), and seven Lightning Components, all of which can be configured to meet your specific use case. Review the following table to understand each Lightning Component, its functionality, and example users that might be interacting with the component to create custom interfaces for Users to utilize Submissions.

The SubmissionResponseForm and SubmissionResponseScoring components can be further customized for different profiles and their requirements by using the following design attributes:

To make the Submissions feature easier to use, now the SubmissionResponseForm can now be used on the record page of the parent object to which the Submission object looks up.

(Required) Create a custom relationship between Submission and another object 

Out of the box, the Submission object is not associated with any specific Salesforce object, besides Section and Question. Since the feature can be used to assess or qualitatively report on any Salesforce object, the System Admin will need to custom configure that relationship depending on the organization’s use case. 

Add a lookup field on the Submission object to create Submission records for another object record. You can choose to add a lookup to Standard Salesforce objects, Amp Impact objects, or any custom object in your Salesforce system.

Once the lookup field is created, be sure to add it to the Page Layout (only the Submission Layout and Response Layout) that will be displayed to Users creating Submission records to be filled out by other Users.

Create a Submission Relationship custom setting record

Once Submission is related to another object, a custom setting record will need to be created in order to correctly display either the Submission Response Form or Radar Charts on the parent object record pages. The purpose of the custom setting is for the component to store this metadata for the component to query (i.e. a custom setting record would need to be created for every relationship field that is added on Submission if the Submission Response Form Radar Charts are being used on each parent object).

1. Go to Custom Settings in Setup.

2. Click “Manage” next to Submission Relationship.

3. Click the “New” button.

4. Fill out the Name field with the API name of the parent object.

   1. e.g. If Submission is child to the Project object from Amp, Name would be populated with “ampi__Project__c”.

5. Fill out the Child Relationship Field Name field with the API name of the relationship field created earlier.

   1. e.g. If Submission is child to the Project object, Child Relationship Field Name would be populated with “Project__c”, the API name of the custom field added to the Submission object.

In the example below, Submission looks up to Projects (Object API Name: ampi__Project__c) through a custom lookup field on Submission (Field API Name: Project__c).

(Required) Assign the Submission Page Layouts to specific Profiles & Record Types

Out of the box, the Submission object comes with three page layouts:

• Template Layout - this should be assigned to the Template Record Type and the Profile of users who will be creating, editing, and downloading submission templates (e.g. Program Officers).

• Response Layout - this should be assigned to the Submission Record Type and the Profile of users who will be filling out responses in submissions (e.g. Grantee).

• Submission Layout - this should be assigned to the Submission Record Type and the Profile of users who need to see the full details of the submission record (e.g. Program Officer, Assessment Reviewer).

On the Submission object, scroll to the Page Layouts and click the Page Layout Assignment button to customize which page layout is displayed to which user profile and record type.

(Required) Assign the Question Page Layouts to specific Profiles & Record Types

Out of the box, the Question object comes with two page layouts:

• Question Layout - this should be assigned to the Question Record Type and the Profile of users who will be creating, editing, and downloading submission templates (e.g. Program Officers).

• Answer Layout - this should be assigned to the Answer Record Type and the Profile of users who will be responding to questions in submissions (e.g. Grantees).

On the Question object, scroll to the Page Layouts and click the Page Layout Assignment button to customize which page layout is displayed to which user profile and record type.

(Required) Assign the Lightning pages to specific Profiles

None of the Lightning pages have pre-configured user assignments. Provide user access to the three pages directly through the activation settings on the pages themselves, based on how Users will work with Submissions. For example, a System Administrator, who will see both Templates and Submission Reviews, can be assigned both the Submission Template and Submission Review Record Pages by using the Record Type assignment.

Additionally, by default, the three Lightning pages are configured based on the three main functions of the Submission feature: Template creation, Submission response, and Submission review. These Lightning pages can be further configured to address an organization’s specific use case by cloning the pages and making the necessary changes.

Set up Radar Charts to display Submission scores

Add the Radar Chart component to Lightning and Digital Experience pages

Since the parent object of Submission needs to be custom configured for each organization, the radar chart component (SubmissionsRadarChart) is not included on any Lightning page out of the box. To display the component, simply open the Lightning record page of Submission’s parent object in the Lightning App Builder and/or Digital Experience Builder and drag the Radar Chart component into the desired space on the page. As needed, add visibility filters to the component to only display the component when certain criteria are met.

Set up automation for users to view Submissions components outside of the Submission record page 

The following components are available for Flow so that they can be launched from pages besides the Submission record page:

• SubmissionResponseForm

• SubmissionResponseReview

• SubmissionResponseScoring

Depending on the organization’s use case, set up a Flow, using the Screen Flow element, to display the relevant component in other locations in the system - e.g. the Lightning Home Page of an app or the record page of a related object.

Set up automation to assign scores to Sections and Submissions 

Scores on Sections (ampi__Section__c.ampi__Score__c) and Submissions (ampi__Submission__c.ampi__Overall_Score__c) can be populated either manually or through automation, based on the score values assigned to child records.

Organizations may choose to build additional automation (e.g., section scores should take the average of the question response scores) for assigning scores using native Salesforce automation, according to their specific requirements. 

Set up automation to lock Responses and/or Reviews 

The SubmissionResponseForm and SubmissionResponseScoring components are displayed as either editable or read-only, depending on the value in two fields on the Submission object.

1. If ampi__Response_Locked__c = TRUE, then the SubmissionResponseForm component is locked from editing for all Users on that Submission record.

2. If ampi__Review_Locked__c = TRUE, then the SubmissionResponseScoring component is locked from editing for all Users on that Submission record.

3. If ampi__Response_Status__c = “Submitted” then the SubmissionResponseForm component is locked from editing for all Users on that Submission record.

4. If ampi__Review_Status__c = “Submitted” then the SubmissionResponseScoring component is locked from editing for all Users on that Submission record.

By default, these fields are updated manually. If the components should lock after specific user actions, automation can be built to auto-populate these fields based on those user actions. For example, if the SubmissionResponseForm component should lock after a user submits their response and the submission review is in progress, then a workflow rule can be built such that when ampi__Review_Status__c = “In Progress”, ampi__Response_Locked__c updates to TRUE, so the user can no longer edit their answers in the midst of a review.

Set up Radar Charts to display Submission scores

Add the Radar Chart component to Lightning and Digital Experience pages

Since the parent object of Submission needs to be custom configured for each organization, the radar chart component (SubmissionsRadarChart) is not included on any Lightning page out of the box. To display the component, simply open the Lightning record page of Submission’s parent object in the Lightning App Builder and/or Digital Experience Builder and drag the Radar Chart component into the desired space on the page. As needed, add visibility filters to the component to only display when certain criteria are met.

Set up automation for users to view Submissions components outside of the Submission record page

The following components are available for Flow so that they can be launched from pages besides the
Submission record page:

• SubmissionResponseForm

• SubmissionResponseReview

• SubmissionResponseScoring

Depending on the organization’s use case, set up a Flow, using the Screen Flow element, to display the
the relevant component in other locations in the system, e.g., the Lightning Home Page of an app or the record page of a related object.

Set up automation to assign scores to Sections and Submissions

Scores on Sections (ampi__Section__c.ampi__Score__c) and Submissions (ampi__Submission__c.ampi__Overall_Score__c) can be populated either manually or through automation based on the score values assigned to child records.

Organizations may choose to build additional automation (e.g., section scores should take the average of the question response scores) for assigning scores using native Salesforce automation, according to their specific requirements.

Set up automation to lock Responses and/or Reviews

The SubmissionResponseForm and SubmissionResponseScoring components are displayed as either
editable or read-only, depending on the value in two fields on the Submission object.

1. If ampi__Response_Locked__c = TRUE, then the SubmissionResponseForm component is locked
   from editing for all Users on that Submission record.

2. If ampi__Review_Locked__c = TRUE, then the SubmissionResponseScoring component is locked
   from editing for all Users on that Submission record.

3. If ampi__Response_Status__c = “Submitted” then the SubmissionResponseForm component is
   locked from editing for all Users on that Submission record.

4. If ampi__Review_Status__c = “Submitted” then the SubmissionResponseScoring component is
   locked from editing for all Users on that Submission record.

5. By default, these fields are updated manually. If the components should lock after specific user actions, automation can be built to auto-populate these fields based on those user actions. For example, if the SubmissionResponseForm component should lock after a user submits their response and the submission review is in progress, then a workflow rule can be built such that when ampi__Review_Status__c = “In Progress”, ampi__Response_Locked__c updates to TRUE, so the
   user can no longer edit their answers in the midst of a review.