​

Task

​

Key Concepts

​

Default Integration Behavior

• No Default Integration: WeGive does not sync Tasks to Salesforce Tasks by default
• Configurable: While not default, integration is possible to:
  • Default Tasks object
  • Any other Salesforce object
• Alternative Approach: Recommended implementation via Lightning Web Component

​

Integration Philosophy

​

Strategic Decision

1. Data Architecture
   • Separates tasks from contact owner UI
   • Maintains clean Salesforce interface
   • Preserves task management flexibility
2. Cost Management
   • Reduces Salesforce data storage costs
   • Avoids unnecessary data accumulation
   • Optimizes system performance
3. User Experience
   • Provides better task visibility
   • Maintains task context
   • Improves task management workflow

​

Alternative Approach

1. Lightning Web Component
   • Provides access to WeGive tasks
   • Avoids Salesforce data storage costs
   • Maintains clean user interface
   • Preserves task context and visibility
2. Task Management Strategy
   • Keep tasks in WeGive system
   • Access via Lightning Web Component
   • Maintain separate task workflows
   • Preserve task management flexibility

​

Important Notes

​

Current Limitations

• No default Task synchronization
• Tasks remain in WeGive system
• No direct Task object mapping

​

Future Possibilities

• Integration possible through custom configuration
• Can map to any Salesforce object
• Requires explicit setup in WeGive settings

​

Best Practices

1. Task Management
   • Use WeGive for task tracking
   • Access tasks via Lightning Web Component
   • Maintain task context
   • Preserve task workflow
2. Integration Planning
   • Understand current limitations
   • Consider Lightning Web Component approach
   • Plan for future integration if needed
   • Evaluate cost implications
3. User Experience
   • Keep task interface clean
   • Maintain task visibility
   • Preserve task management workflow
   • Consider user adoption

​

Common Scenarios

​

Task Management

1. Tasks created in WeGive
2. Accessible via Lightning Web Component
3. No direct sync to Salesforce
4. Maintains task context and workflow

​

Future Integration Planning

1. Assess integration needs
2. Consider Lightning Web Component
3. Evaluate cost implications
4. Plan for potential custom configuration

​

Task Visibility

1. Tasks visible in WeGive
2. Accessible in Salesforce via component
3. Maintains task context
4. Preserves user experience