Configurable activity rollups and task processing

I led the TaskTrigger upgrade at 6sense, building configurable activity processing around Apex and Custom Metadata. The implementation separates the rules used to qualify and aggregate activities from the code that coordinates the processing.

It handles Task inserts, updates and deletes, and recalculates affected parent records, including both the old and the new parent when a relationship changes. Configured rules are evaluated over completed activities, with aggregations such as counts and latest dates over configured windows. Processing runs through Queueable and Batch paths, with persisted activity-window state.

It is a useful example of my focus on maintainable platform engineering: making business rules configurable while keeping transaction handling, parent updates and asynchronous execution in one reusable implementation.

• Built configurable activity processing around Apex and Custom Metadata.
• Handled Task inserts, updates and deletes, recalculating affected parent records.

• Led the TaskTrigger upgrade.

• Apex
• Custom Metadata
• Queueable Apex
• Batch Apex

Client and internal names, payloads and configuration values are deliberately left out of this write-up.