...
...
🔧 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.
| Info |
|---|
Sections marked as required are only mandatory if your organization is using Submissions. |
...
(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 Popup: Field set on Section object that determines which fields are displayed and required in the Add New Section and Edit Section pop-ups.
Add/Edit Question Popup: Field set on Question object that determines which fields are displayed and required in the Add New Question and Edit Question pop-ups.
...
(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.
...
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.
...
| Info |
|---|
Admin Note: If the organization’s use case will involve creating Submissions for multiple objects, then Steps 2 and 3 will need to be repeated for each object that will require the Submissions feature. For example, an organization may conduct assessments on Organizations/Accounts and request narrative reporting for Projects. The System Admin will need to add one lookup field and one custom setting record for Account, and repeat the process for the Project object. |
...
(Required) Assign the Submission Page Layouts to specific Profiles & Record Types
Out of the box, the Submission object comes with three page layouts:
...
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
Lightning Page API Name | Function | Components | Related Record Type | Example User |
Submission_Template_Record_Page | Enables users to create and edit submission templates, preview templates and assign those templates to other users to fill out | CreateTemplateData SubmissionTemplatePreview SubmissionClone | Template | Program Officer |
Submission_Response_Record_Page | Enables users to fill out any submissions that have been assigned to them and submit responses for review | SubmissionResponseForm SubmissionClone | Submission | Grantee |
Submission_Review_Record_Page | Enables users to read responses submitted by other users and assign scores to those responses | SubmissionResponseReview SubmissionResponseScoring | Submission | Assessment Reviewer |
...
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.
...
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
| Info |
|---|
Admin Note: |
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.
| Info |
|---|
Admin Note: |
...
Set up automation for users to view Submissions components outside of the Submission record page
| Info |
|---|
Admin Note: |
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.
| Info |
|---|
Admin Note: |
...
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.
If ampi__Response_Locked__c = TRUE, then the SubmissionResponseForm component is locked
from editing for all Users on that Submission record.If ampi__Review_Locked__c = TRUE, then the SubmissionResponseScoring component is locked
from editing for all Users on that Submission record.If ampi__Response_Status__c = “Submitted” then the SubmissionResponseForm component is
locked from editing for all Users on that Submission record.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.
...