Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EU/feature1 #15

Open
wants to merge 1 commit into
base: Int
Choose a base branch
from
Open

EU/feature1 #15

wants to merge 1 commit into from

Conversation

toby-gearset
Copy link
Collaborator

Pull Request Description

This pull request introduces new functionality to handle case management in Salesforce by adding an Apex class and a flow. Below is a detailed breakdown of the changes made in each file:


1. CaseHoldingEmailHandler.cls

Type: New Apex Class
Change:

  • A new global class CaseHoldingEmailHandler has been created.
  • This class includes an @InvocableMethod named sendHoldingEmail that takes a list of case IDs as input.
  • The method retrieves the corresponding cases and sends a holding email to the contact associated with each case if an email address is available.

Impact:

  • This class allows for automated email notifications to be sent when a case is opened, improving communication with customers.
  • Reviewers should ensure that the email content and logic align with business requirements and that the method handles cases without email addresses gracefully.

2. CaseHoldingEmailHandler.cls-meta.xml

Type: New Metadata File
Change:

  • The metadata file for the CaseHoldingEmailHandler class has been created, specifying the API version as 62.0 and setting the status to Active.

Impact:

  • This file is necessary for the deployment of the Apex class. Ensure that the API version is compatible with the rest of the Salesforce org.

3. Update_Cases_To_Closed.flow-meta.xml

Type: New Flow
Change:

  • A new flow named Update_Cases_To_Closed has been created.
  • This flow includes several action calls, including:
    • Notify DevOps Team: Sends an email notification to the DevOps team.
    • Send Holding Email: Calls the CaseHoldingEmailHandler to send a holding email when a case is opened.
  • The flow also includes decision elements to check case status and escalate cases for high-priority customers.
  • It has record updates to change the status of cases and set comments for archiving.

Impact:

  • This flow automates the process of updating case statuses and notifying relevant parties, which can significantly enhance operational efficiency.
  • Reviewers should pay attention to the flow's logic, especially the decision criteria and the email notifications, to ensure they meet the intended business processes.

Summary

This PR introduces:

  • A new Apex class for sending holding emails when cases are opened.
  • A new flow that automates case closure and notifications.

Testing Recommendations:

  1. Apex Class: Test the sendHoldingEmail method with various scenarios, including cases with and without email addresses.
  2. Flow: Validate the flow by creating test cases and ensuring that the correct emails are sent and statuses are updated as expected.
  3. Integration: Ensure that the flow integrates well with existing processes and does not disrupt current case management workflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant