top of page

How to handle subscription and contract terminations

Updated: Dec 1, 2023

Github Link : https://github.com/AourLegacy/AourFactory/tree/TerminatedContract

Creating a Salesforce CPQ solution to handle subscription and contract terminations involves several steps.:


1. Trigger: The process starts when a subscription's termination date is changed and is not null.


2. Check Contract Status:

- Retrieve the contract linked to this subscription.

- Check if the contract is not already terminated. If the contract is terminated, the process ends here.


3. Retrieve Linked Subscriptions:

- Get all subscriptions linked to the contract.


4. Check Termination Dates of All Subscriptions:

- For each subscription linked to the contract, check if their termination date is not null.

- If any subscription's termination date is null, the flow ends here.


5. Terminate Contract:

- If all linked subscriptions have a non-null termination date, proceed to terminate the main contract.


To implement this in Salesforce CPQ, you can use a Flow. Here's an outline of how you might structure this:













It's important to handle bulk operations correctly and consider the governor limits in Salesforce. Also, thorough testing in a sandbox environment is recommended before deploying this solution to production.



2 views0 comments

Recent Posts

See All

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page