Skip to main content
Version: 2

Considerations for Plinqx in Salesforce

Introduction​

While Plinqx leverages the robust capabilities of Salesforce, it is important to be aware of various Salesforce-specific limits and operational considerations. These factors play a significant role in developing and configuring integrations within Plinqx. This page outlines key considerations to keep in mind.

1. API Limits in Salesforce​

Salesforce imposes limits on the number of API calls that can be made within a given time frame. When designing APIs in Plinqx:

  • Be aware of your Salesforce org's API request limits.

  • Plan your integration architecture to optimize API usage and avoid exceeding these limits.

  • More details can be found in the Salesforce API Request Limits and Allocations documentation.

2. Event Limits in Salesforce​

For applications using Platform Events or other Salesforce event-driven features:

  • Understand the event delivery and volume limits applicable in your Salesforce edition.

  • Design your Plinqx integrations to efficiently manage event throughput within these limits.

  • Refer to Platform Event Limits and Allocations for comprehensive information.

3. Governor Limits in Salesforce​

Salesforce Governor Limits restrict the amount of resources consumed during code execution. When developing custom Apex or Flows for Plinqx:

  • Ensure your code adheres to Salesforce’s Governor Limits, such as limits on SOQL queries, DML operations, and CPU time.

  • Use best practices in Apex and Flow design to optimize resource usage and prevent limit exceptions.

  • The Apex Governor Limits documentation provides detailed insights.

4. Order of Execution in Salesforce​

Understanding Salesforce's order of execution is crucial:

  • Be mindful of how triggers, workflows, and processes execute in Salesforce.

  • Ensure your Plinqx configurations align with this order to achieve the desired outcomes and maintain data integrity.

  • Visit Triggers and Order of Execution for more details.

5. Data and File Storage Management in Salesforce​

Managing data and file storage is vital, especially for Transaction and Log files in Plinqx:

  • Monitor your Salesforce org's data and file storage limits.

  • Regularly review and clean up Transaction and Log records in Plinqx to manage storage usage efficiently.

  • Consider archiving strategies for historical data while ensuring compliance with data retention policies.

  • Salesforce’s documentation on Data and File Storage Limits offers valuable guidelines.

Conclusion:

Plinqx, while built on Salesforce, is subject to the platform's limits and operational behaviors. Understanding and accommodating these considerations in your Plinqx development and configuration is crucial for creating efficient, reliable, and scalable solutions. Always plan and test your Plinqx integrations with these Salesforce-specific aspects in mind to ensure optimal performance and compliance with the platform's standards.