Email Alert Configuration in Provar Grid
This document details the steps required to enable email alert notifications to be sent once a Test Plan Schedule Job is completed in Provar Manager. Guiding the user through existing Salesforce email alert functionality to trigger, based on Test Plan Schedule job records changing to Complete, Failed, or Aborted.
The functionality described is not proprietary to Provar; it is all inherent in the Salesforce organization.
Create an Email Template
Email templates can be created either through the use of Lightning Templates or Classic Templates. Follow whichever steps are more appropriate for your company’s needs.
Lightning Email Templates
First, they must be enabled in the setup to utilize lightning email templates. To do this,
- Launch Setup.
- Quick Search for ‘Lightning Email Templates.’
- Toggle the ‘Folders and Enhanced Sharing’ setting to ‘On’.

For the Test Plan Schedule Job to appear when creating a new lightning email template. First of all, the steps below must be followed to make the necessary custom objects available to the related entity types list.
- Launch Setup.
- Navigate to the Object Manager.
- Quick find the ‘Test Plan Schedule Job’ custom object.
- Edit the details.
- Check the ‘Allow Activities’ checkbox and save.

- Navigate to ‘Page Layouts.’
- Open the ‘Test Plan Schedule Job’ layout.
- Under the ‘Related Lists’ category, add ‘Open Activities’ and ‘Activity History’ to the Related Lists layout section.

- Perform an ‘Empty Cache and Hard reload’ of your browser for these changes to take effect immediately.
- Log out and back into your Salesforce organization.
Now that the Test Plan Schedule Job object will be available for us to reference in the Email template, follow the below instructions to set up a Lightning email template.
- Go to the Apps Center.
- Launch the ‘Email Templates’ application.
- Select ‘New Email Template.’
- Enter the following values:
- Related Entity Type = Test Plan Schedule Job
- Folder = Public Email Templates
- All other fields can be entered as per your company’s requirements. Including merge fields in the email template can make the emails more meaningful. Provar recommends a Test Plan Schedule job, and you may want to include the Job Number and the status that the record has been changed to. Merge fields can be added by selecting the curly brackets in the bottom right of the template. See below for an example.
Dear User,
You’re receiving this email to notify you that Test plan schedule job – {{{provar__Test_Plan_Schedule_Job__c.Name}}}
Changed status at {{{provar__Test_Plan_Schedule_Job__c.LastActivityDate}}} and now has a status of {{{provar__Test_Plan_Schedule_Job__c.provar__Status__c}}}.
Best Regards
Provar

Classic Email Templates
- Launch Setup
- Quick search for ‘Classic Email Templates.’
- Select ‘New Template.’
- Select the template type appropriate to your needs; for this document, we will select ‘Text.’
- Enter an appropriate ‘Email Template Name’ and ‘Description.’
- Enter your required Subject and Email body.
Note: The ‘Available Merge Fields’ can be used to add appropriate content to your email. By selecting the ‘Test Plan Schedule Job Field’ as the ‘Selected Field Type’ and the relevant fields, the returned value can be copied and pasted into your template. See the below example.
Dear User,
You’re receiving this email to notify you that Test plan schedule job – {provar__Test_Plan_Schedule_Job__c.Name}
Changed status at {provar__Test_Plan_Schedule_Job__c.LastActivityDate} and now has a status of {provar__Test_Plan_Schedule_Job__c.provar__Status__c}.
Best Regards
Provar
- Use the check box to set the email template to ‘Available for Use.’

Create an Email Alert
Once you have some email alerts to reference, the next step is to create an ‘Email alert’.
- Launch Setup.
- Quick search for ‘Email Alerts.’
- Select ‘New Email Alert.’

- Enter the ‘Object’ as ‘Test Plan Schedule Job.’
- Enter the ‘Email Template’ as the template you created in the previous steps.
Note: there is a toggle to search for Classic or Lightning email templates.
- Populate all other fields as per your company’s requirements
- For recipients, include all users who want to receive email notifications.
- If the recipients are not users in Salesforce, enter their email addresses in the ‘Additional Emails’ field.
- Save the Email Alert.

Create Record Triggered Flow
- Launch Setup.
- Quick Search for ‘Flows.’
- In ‘Flows,’ select ‘New Flow.’
- Select ‘Record Triggered Flow.’

- In the ‘Object,’ select ‘Test Plan Schedule Job.’
- Select Trigger flow when: ‘A job is updated.’
- Under ‘Conditional Requirements,’ select ‘Any Condition is Met (OR)
- Set the following three conditions:
- provar__Status__c equals Completed
- provar__Status__c equals Failed
- provar__Status__c equals Aborted

- Select ‘When to run the flow for updated records’ to ‘Only when a record is updated to meet the condition requirements.’
- Select ‘Optimize the Flow for Actions and related records.’

- Save the changes to the ‘Record Triggered flow’. This will lead you to a flow diagram.
- Select the + icon below the ‘Run Immediately’ text when you hover over the circle.

- Add a ‘Send Email Alert’ element to your flow.
- This will take you to a ‘New Action’ screen and allow you to select the Email Alert created in the previous steps.
- Add a meaningful Label, API Name, and Description.
- For the record ID, select $Record – provar_Test_Plan_Schedule_Job_c and then ‘Record ID.’

- Click Done.
Your flow should look like this:

- Save your Flow and provide a meaningful Label, API name, and Description.
- Select ‘Activate.’
- You can test if the email works as expected by navigating to an existing Test Plan Schedule Job record and changing its status to either ‘Complete,’ ‘Failed,’ or ‘Aborted.’
Conclusion
Email alerts are a fantastic way to stay updated with changes you’re interested in. As a Salesforce native application, Provar Manager benefits from all of the inbuilt functionality Salesforce offers, including notifications sent via Flows.
As a matter of good business practice, notifications are only effective when used in a targeted way for a specific audience. Otherwise, recipients may suffer notification fatigue, so please use them carefully.
Provar Grid jobs are designed to be scheduled at regular intervals or as part of the continuous development life cycle; the jobs run by Provar Grid will typically run with minimal manual intervention. Therefore, notifications when jobs are complete become an essential piece of the puzzle and will keep stakeholders informed effectively.
Provar plans to make email and Slack alerts a more integrated part of our services in coming releases. But in the meantime, we hope this documentation helps to solve this problem in the short term.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Creating and Importing Projects
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Automation
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- Running Tests
- Searching Provar with Find Usages
- Secrets Management and Encryption
- Setup and Teardown Test Cases
- Tags and Service Level Agreements (SLAs)
- Test Cycles
- Test Plans
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Provar Manager
- Provar Manager Setup and User Guide
- Installing Provar Manager
- Configuring Provar Manager
- How to Use Provar Manager
- Managing Your Testing Life Cycle
- Provar Manager Test Execution
- Test Executions and Defect Management
- Provar Manager Test Coverage
- How to Integrate Provar Manager
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Provar Manager Plugins
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Provar Grid
- DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version Control
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes