Salesforce Developer in Toronto, ON, Canada

A custom object and custom metadata-driven queueing system for managing the execution of Apex-based asynchronous processes (Queueable, Batch Apex, Future).

Features:
• Every async process is logged in a custom object and any exceptions are captured
• Exception messages are checked for certain keywords that indicate a *temporary* error has occurred (record locking, API timeout, and so on) and are automatically retried with an increasing delay between each retry
• The system automatically chooses which async process is most appropriate based on the number of jobs to process: Batch Apex when there are many jobs, self-chaining Queueables for fewer jobs, Future for web callouts, and for jobs that are safe to run in parallel
• Each user has their own "queue" and jobs are executed "in order," to maintain the proper order of operations
• Custom metadata is used to control the settings that govern the behavior of the queuing system
• Jobs can be "bulkified" where multiple jobs of the same type can be run together in a bulk-safe manner to speed up processing and minimize governor limits

A metadata-driven custom solution for performing child-to-parent rollup summaries on any field using Master-Detail, Lookup, or custom relationships.

Features:
• The relationship between child and parent can be a Master-Detail, Lookup, or any custom field
• The rollup rules are stored in custom metadata
• Rollups are processed asynchronously using Queueable or Batch Apex
• Exceptions/errors such as UNABLE_TO_LOCK_ROW are automatically retried
• Rollups can be batched into smaller batch sizes to minimize governor limit exceptions
• Rollups use aggregation queries when possible or query-driven calculations when not possible (such as when aggregating formula fields)
• Rollups only recalculate when fields that are part of the calculation are changed to minimize recalculations

I created an "interaction log" for Lightning to customize and speed up activity logging.

Features:
• Type-ahead suggestions for the subject based on a list of suggestions that are profile-specific and controlled by custom metadata
• A dropdown of type values that are profile-specific and controlled by custom metadata
• Custom permission is assigned via a permission set that grants the ability to assign activities to other owners
• After logging an activity, the user is presented with a list of "Next Actions" that might want to take, including 1) Log a future open activity, 2) Set a "Call Me Back" date, 3) Send an email, 4) Reassign lead to a queue/other users
• Uses the "Unsaved Changes" component to prompt the user to finish logging their call if they attempt to close the tab without saving
• Set appropriate default field values to speed up data entry

I created a Lightning web component that schedules Zoom meetings and logs activities when the meeting is completed successfully.

Features:
• LWC for creating a scheduled Zoom meeting with the running user's Zoom account
• Associates the meeting with a lead/contact
• Monitors completed Zoom meetings to log an activity associated with the lead/contact along with the duration of the meeting, for inclusion in daily "talk time" reports

I created a Pardot API integration library in Apex for performing API callouts to Pardot from Salesforce for business processes that were not supported by the Pardot Sync Connector.

Features:
• Performs opt-ins based on data input from a flow in Salesforce
• Updates lead/contact records with list-based membership information
• Nulls values in Pardot when nulled in Salesforce

Special notes:
• Authenticates to Pardot using OAuth/SSO
• Refreshes access token when expired
• Settings are stored in custom metadata

Custom logic that executes a round-robin lead/contact assignment when particular business rules are met.

Special Requirements:
• Users who are "full" (have the maximum number of leads allowed already) are excluded
• Sales managers and administrators need to be able to manage the addition, pausing, and removal of users from round robins through clicks, not code

Implementation:
• Custom Apex trigger code was written to implement the complex business logic that triggers the assignment
• Custom Apex code was written to identify which round-robin group applies (based on team and region), find the next user in the round-robin, validate they are not "full," assign the record to the new owner, and log an activity for auditing purposes
• Custom objects were created to store the list of assignment groups and manage the users that belong to each group, as well as store the user's current and maximum number of leads/contacts
• Custom Apex trigger code was written to recalculate a user's current number of leads/contacts whenever an ownership transfer occurs. This recalculation is done asynchronously so as to not slow down the ownership transfer transaction and to manage governor limits

Lightning Records Pages were customized using Enhanced Lightning Grid to separate activity data into separated related lists with filters pre-applied to the data, and shown in separate labeled tabs.

Tabs:
• Activity Highlights: only the most important activities are visible (based on type)
• Activity History: all activities
• My Activities: the running user's activities
• Open Activities: upcoming activities
• Marketing Activities: email opens and clicks from Pardot marketing emails

Special notes:
• Improvements were made to the standard apex code that comes with Enhanced Lightning Grid to make it easier to deploy new ELGs
• Reusable static methods were created to build the SOQL queries that support the user-provided sorting and filtering