<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mukesh Pal on Medium]]></title>
        <description><![CDATA[Stories by Mukesh Pal on Medium]]></description>
        <link>https://medium.com/@mukesh.palsftech?source=rss-5b345498fd34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Xs5GhjgVKectc6Epe66hOw.png</url>
            <title>Stories by Mukesh Pal on Medium</title>
            <link>https://medium.com/@mukesh.palsftech?source=rss-5b345498fd34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:52:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mukesh.palsftech/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Null Coalescing Operator in Salesforce Apex]]></title>
            <link>https://medium.com/@mukesh.palsftech/null-coalescing-operator-in-salesforce-apex-024448694b4f?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/024448694b4f</guid>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 08:26:59 GMT</pubDate>
            <atom:updated>2024-09-09T08:26:59.074Z</atom:updated>
            <content:encoded><![CDATA[<p>The Null Coalescing Operator (??) in Apex provides a way to return the first non-null value from a list of expressions. It’s useful for simplifying code when you need to handle null values and provide a default value if necessary.</p><p><strong>Syntax:</strong></p><p>result = expression1 ?? expression2;</p><p>In this example, result will be assigned the value of expression1 if it is not null; otherwise, it will be assigned the value of expression2.</p><p>Examples:</p><p>1. Basic Example:<br>String name = null;<br>String defaultName = ‘Guest’;<br>String finalName = name ?? defaultName;</p><p>2. With Variables:<br>Integer count = null;<br>Integer defaultCount = 10;<br>Integer totalCount = count ?? defaultCount;</p><p><strong>3.</strong> <strong>In Conditional Logic:</strong></p><p>Account acc = [SELECT Name FROM Account LIMIT 1];<br>String accountName = acc.Name ?? ‘Unknown Account’;</p><p><strong>Use Cases:</strong></p><p>1. Providing Default Values: When fetching data from a source that may return null, use the null coalescing operator to provide a fallback value.</p><p>2. Simplifying Code: Reduces the need for lengthy conditional statements to check for null values.</p><p><strong>When It Does Not Work:</strong></p><p>1. Complex Expressions: The null coalescing operator does not work with expressions that involve complex logic or require multiple operations. For example, if you need to evaluate more intricate conditions, you might need a different approach or additional logic.</p><p>2. Custom Logic Handling: If you need to perform specific actions based on the value being null, you might have to use traditional if statements or other conditional structures.</p><p>3. Non-Primitive Data Types: The null coalescing operator is limited in handling non-primitive data types Example custom objects or collections) directly. You may need to use more specific logic for these cases.</p><p><strong>Example of When It Doesn’t Work:</strong></p><p>List&lt;String&gt; names = new List&lt;String&gt;{‘Anil’, null, ‘Pratik’};<br>String firstValidName = names[1] ?? ‘Default Name’;</p><p>// This will not work as expected because ‘names[1]’ is an element in a list.<br>// You need to handle list-specific logic separately.</p><p>In summary, the Null Coalescing Operator is useful for simplifying null-check logic and providing default values, but it has limitations when dealing with complex conditions or non-primitive types.</p><p>For More Info Connect me on : <a href="http://www.linkedin.com/in/mukeshpals">www.linkedin.com/in/mukeshpals</a>f</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=024448694b4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Detailed Functional Explanation of Quote-to-Cash Process in Salesforce CPQ]]></title>
            <link>https://medium.com/@mukesh.palsftech/detailed-functional-explanation-of-quote-to-cash-process-in-salesforce-cpq-0c64c24ba159?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c64c24ba159</guid>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Sun, 08 Sep 2024 05:37:12 GMT</pubDate>
            <atom:updated>2024-09-08T05:37:12.689Z</atom:updated>
            <content:encoded><![CDATA[<p>The Quote-to-Cash (QTC) process in Salesforce CPQ (Configure, Price, Quote) encompasses several critical stages that allow companies to manage and automate their sales processes from lead management through contract generation, order fulfilment, invoicing, and renewals. Below is a comprehensive breakdown of each step, focusing on how contracts are created, fields required, how orders are generated, amendments, and renewals.</p><p><strong>1. Lead Management and Opportunity Creation</strong></p><ul><li><strong>Lead Conversion</strong>: When a lead is qualified, it is converted into an Account, Contact, and Opportunity.</li><li><strong>Fields Involved in Opportunity</strong>:</li><li><strong>Opportunity Name</strong>: Automatically generated but can be edited.</li><li><strong>Close Date</strong>: When the deal is expected to close.</li><li><strong>Stage</strong>: Sales stage Example Prospecting, Proposal, Negotiation).</li><li><strong>Amount</strong>: Estimated deal value.</li><li><strong>Account Name</strong>: Linked Account to which the opportunity belongs.</li><li><strong>Owner</strong>: The sales rep managing the opportunity.</li></ul><p><strong>2. Product Configuration</strong></p><ul><li><strong>Purpose</strong>: To select and configure products according to customer requirements.</li><li><strong>Key Features</strong>:</li><li><strong>Guided Selling</strong>: Helps users select the correct products based on customer needs.</li><li><strong>Rules Engine</strong>: Ensures correct product combinations (validation, configuration, and selection rules).</li><li><strong>Fields Involved</strong>:</li><li><strong>Product Name</strong>: Name of the selected product.</li><li><strong>Quantity</strong>: Number of units.</li><li><strong>Options</strong>: Additional configurable features Example color, size).</li><li><strong>Price Book</strong>: Determines pricing based on predefined price lists.</li></ul><p><strong>3. Pricing and Discounting</strong></p><ul><li><strong>Purpose</strong>: Calculates the total price based on selected products, volume discounts, pricing rules, and special promotions.</li><li><strong>Fields Involved</strong>:</li><li><strong>List Price</strong>: Base price from the price book.</li><li><strong>Discounts</strong>: Applied at product level, quote level, or through special promotions.</li><li><strong>Net Price</strong>: Calculated price after applying discounts.</li></ul><p><strong>4. Quote Generation</strong></p><ul><li><strong>Purpose</strong>: To generate a formal document that outlines the configured products, pricing, terms, and conditions.</li><li><strong>Fields Involved</strong>:</li><li><strong>Quote Name</strong>: Automatically generated or manually entered.</li><li><strong>Quote Number</strong>: System-generated for tracking.</li><li><strong>Expiration Date</strong>: When the quote is valid until.</li><li><strong>Primary Contact</strong>: Person receiving the quote.</li><li><strong>Terms and Conditions</strong>: Legal and financial terms of the sale.</li><li><strong>Quote Line Items</strong>: Detailed list of configured products with pricing.</li></ul><p><strong>5. Quote Approval</strong></p><ul><li><strong>Purpose</strong>: To ensure compliance with pricing, discounting, and other approval thresholds set by the company.</li><li><strong>Approval Process</strong>:</li><li>Triggers are based on defined criteria Example discount percentage, deal size).</li><li>Approval requests are sent to relevant managers or teams.</li><li>Upon approval, the quote can be sent to the customer.</li><li><strong>Fields Involved</strong>:</li><li><strong>Approval Status</strong>: Pending, Approved, Rejected.</li><li><strong>Approver Comments</strong>: Feedback or required changes.</li></ul><p><strong>6. Contract Creation</strong></p><ul><li><strong>Purpose</strong>: To formalize the agreement between the company and the customer based on the approved quote.</li><li><strong>Steps to Create a Contract</strong>:</li></ul><ol><li><strong>Conversion</strong>: Once the quote is accepted by the customer, it is converted into a contract.</li><li><strong>Template Selection</strong>: Select the appropriate contract template (Standard, Custom).</li><li><strong>E-signature Integration</strong>: Obtain signatures via tools like DocuSign.</li></ol><ul><li><strong>Fields Required</strong>:</li><li><strong>Contract Name</strong>: Unique identifier for the contract.</li><li><strong>Start Date</strong>: When the contract becomes effective.</li><li><strong>End Date</strong>: Contract expiration date.</li><li><strong>Contract Term</strong>: Duration of the contract Example 12 months).</li><li><strong>Billing Frequency</strong>: Monthly, quarterly, annually.</li><li><strong>Renewal Term</strong>: Defines if and how the contract can be renewed.</li><li><strong>Payment Terms</strong>: Payment schedules, due dates.</li></ul><p><strong>7. Order Creation and Fulfilment</strong></p><ul><li><strong>Purpose</strong>: To initiate the delivery of products/services outlined in the contract.</li><li><strong>Steps to Create an Order</strong>:</li></ul><ol><li><strong>Convert Contract to Order</strong>: This is often automated once the contract is active.</li><li><strong>Fulfilment Planning</strong>: Details how and when products will be delivered.</li></ol><ul><li><strong>Fields Required</strong>:</li><li><strong>Order Number</strong>: Auto-generated for tracking.</li><li><strong>Order Start Date</strong>: When fulfilment starts.</li><li><strong>Shipping Address</strong>: Destination for physical products.</li><li><strong>Fulfilment Status</strong>: Not started, in progress, completed.</li><li><strong>Fulfilment</strong>:</li><li>For software: License provisioning, account setup.</li><li>For physical products: Shipment, delivery tracking.</li></ul><p><strong>8. Invoicing and Payment</strong></p><ul><li><strong>Purpose</strong>: To generate invoices based on the order and collect payment.</li><li><strong>Steps to Create an Invoice</strong>:</li></ul><ol><li><strong>Generate Invoice</strong>: Based on the order details and terms in the contract.</li><li><strong>Send Invoice</strong>: Emailed or integrated with financial systems for processing.</li></ol><ul><li><strong>Fields Required</strong>:</li><li><strong>Invoice Number</strong>: System-generated.</li><li><strong>Billing Address</strong>: Where the invoice is sent.</li><li><strong>Due Date</strong>: Payment deadline.</li><li><strong>Amount Due</strong>: Total payable amount.</li></ul><p><strong>9. Renewal Management</strong></p><ul><li><strong>Purpose</strong>: Manage contract renewals, ensuring ongoing business and opportunities for upselling.</li><li><strong>Steps</strong>:</li></ul><ol><li><strong>Renewal Notification</strong>: Automatically generated based on contract end date.</li><li><strong>Renewal Quote</strong>: Create a new quote based on existing contract terms, adjusted for any changes (price increases, additional products).</li></ol><ul><li><strong>Fields Involved</strong>:</li><li><strong>Renewal Start Date</strong>: When the renewed contract starts.</li><li><strong>Renewal End Date</strong>: Expiry of the new term.</li><li><strong>Renewal Pricing</strong>: Adjusted pricing based on current rates or negotiated discounts.</li></ul><p><strong>10. Amendments</strong></p><ul><li><strong>Purpose</strong>: To modify existing contracts when terms, products, or pricing need to change before the contract ends.</li><li><strong>Steps to Create an Amendment</strong>:</li></ul><ol><li><strong>Select Contract to Amend</strong>: Choose the active contract.</li><li><strong>Amend Products or Terms</strong>: Add or remove products, adjust quantities, update pricing.</li><li><strong>Generate an Amendment Quote</strong>: Reflects the updated terms.</li><li><strong>Approval and Execution</strong>: Requires approval similar to the original quote.</li></ol><ul><li><strong>Fields Required</strong>:</li><li><strong>Amendment Type</strong>: Product change, pricing change, term adjustment.</li><li><strong>Reason for Amendment</strong>: Document why changes are made.</li><li><strong>Revised End Date</strong>: New expiration if extended.</li></ul><p><strong>For More Information connect with Me on :</strong> <a href="https://medium.com/www.linkedin.com/in/mukeshpalsf">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c64c24ba159" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce CPQ Product Bundle]]></title>
            <link>https://medium.com/@mukesh.palsftech/salesforce-cpq-product-bundle-8a1fc1331fca?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a1fc1331fca</guid>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Sat, 07 Sep 2024 07:36:40 GMT</pubDate>
            <atom:updated>2024-09-07T07:36:40.927Z</atom:updated>
            <content:encoded><![CDATA[<p>In <strong>Salesforce CPQ</strong>, a <strong>bundle</strong> is a group of products sold together, typically as a package. Bundles allow users to manage multiple related products in one selection, making it easier to configure, price, and quote complex offerings. Each bundle consists of a <strong>parent product</strong> (the main product) and <strong>child products</strong> (options or components).</p><p><strong>Types of Bundles in Salesforce CPQ:</strong></p><ol><li><strong>Static Bundle</strong>:</li></ol><ul><li>The components or options in the bundle are fixed and cannot be changed by the user.</li><li>Example: A laptop bundle with a pre-defined hard drive, RAM, and operating system.</li></ul><ol><li><strong>Configurable Bundle</strong>:</li></ol><ul><li>Users can choose or customize options (such as selecting different components) within the bundle based on their requirements.</li><li>Example: A laptop bundle where the user can choose the type of hard drive, RAM, or accessories.</li></ul><ol><li><strong>Nested Bundle</strong>:</li></ol><ul><li>A bundle within a bundle, where each child product can also have its own set of options or components.</li><li>Example: A home theater system bundle that includes a speaker system, which is itself a bundle with different speaker configurations.</li></ul><ol><li><strong>Dynamic Bundle</strong>:</li></ol><ul><li>Products are dynamically added to the bundle based on certain criteria like user selections or business rules.</li><li>Example: A mobile phone plan bundle where available accessories are shown dynamically based on the selected phone model.</li></ul><p><strong>How to Create a Bundle in Salesforce CPQ:</strong></p><p><strong>Method 1: Basic Bundle (Static Bundle)</strong></p><p><strong>Steps:</strong></p><ol><li><strong>Create the Parent Product</strong>:</li></ol><ul><li>Go to <strong>Products</strong> and create the <strong>Parent Product</strong> (Example “Laptop”).</li></ul><ol><li><strong>Add Options to the Parent Product</strong>:</li></ol><ul><li>Under the parent product, create child products as <strong>Options</strong> (Example”16 GB RAM”, “500 GB SSD”).</li></ul><ol><li><strong>Create an Option Group</strong> (Optional):</li></ol><ul><li>Group options together for better organization (Example “Memory Options”, “Storage Options”).</li></ul><ol><li><strong>Set Bundle Configuration</strong>:</li></ol><ul><li>Set the <strong>Bundle</strong> checkbox to <strong>True</strong> for the parent product to designate it as a bundle.</li></ul><ol><li><strong>Add Option Constraints (if needed)</strong>:</li></ol><ul><li>Add logic for incompatible or required options (Example “If 32 GB RAM is selected, SSD must be 1 TB”).</li></ul><p><strong>Use Case</strong>: A predefined set of products like a laptop with specific storage, memory, and software pre-installed.</p><p><strong>Method 2: Configurable Bundle</strong></p><p><strong>Steps:</strong></p><ol><li><strong>Create Parent Product</strong>:</li></ol><ul><li>Create a parent product that can be configured (Example “Custom Laptop”).</li></ul><ol><li><strong>Create Option Products</strong>:</li></ol><ul><li>Define option products (Example different types of RAM, hard drives, accessories).</li></ul><ol><li><strong>Add Option Groups</strong>:</li></ol><ul><li>Group the options for better organization (Example “Memory Options”, “Storage Options”).</li></ul><ol><li><strong>Set Configurable Attributes</strong>:</li></ol><ul><li>Set the <strong>Configurable</strong> checkbox to <strong>True</strong> on the parent product.</li></ul><ol><li><strong>Set Option Constraints and Rules</strong>:</li></ol><ul><li>Use <strong>Product Rules</strong> to set dependencies (Example “If SSD is selected, certain software is included”).</li></ul><ol><li><strong>Add Pricing Rules (Optional)</strong>:</li></ol><ul><li>Use <strong>Price Rules</strong> to adjust prices based on user selections (Example additional fees for upgraded RAM).</li></ul><p><strong>Use Case</strong>: A product with customizable options, like selecting various specs for a laptop.</p><p><strong>Method 3: Nested Bundle</strong></p><p><strong>Steps:</strong></p><ol><li><strong>Create Parent Product</strong>:</li></ol><ul><li>Create a parent product (Example “Home Theatre System”).</li></ul><ol><li><strong>Create Nested Bundles</strong>:</li></ol><ul><li>Define child products (Example “Speaker System”) as their own bundle with their options.</li></ul><ol><li><strong>Add to Parent as Option</strong>:</li></ol><ul><li>Assign the nested bundle as an option to the parent product.</li></ul><ol><li><strong>Set Constraints/Dependencies</strong>:</li></ol><ul><li>Define rules for options between the parent and nested bundle (Example “If Dolby system is selected, add HDMI cable”).</li></ul><p><strong>Use Case</strong>: A complex package with sub-packages (Example a home theatre system where different speakers have their own components).</p><p><strong>Method 4: Dynamic Bundle</strong></p><p><strong>Steps:</strong></p><ol><li><strong>Create the Parent Product</strong>:</li></ol><ul><li>Define a parent product with dynamic options (Example “Mobile Phone Plan”).</li></ul><ol><li><strong>Use Product Rules</strong>:</li></ol><ul><li>Set up <strong>Product Rules</strong> to dynamically display options based on user selections (Example accessories based on the selected phone model).</li></ul><ol><li><strong>Create Option Products</strong>:</li></ol><ul><li>Define options that are only available in certain conditions (Example phone case shown based on phone colour).</li></ul><ol><li><strong>Set Dynamic Constraints</strong>:</li></ol><ul><li>Add dynamic option constraints to adjust the available child products in the bundle.</li></ul><p><strong>Use Case</strong>: A mobile phone bundle where available accessories vary based on the chosen model.</p><p><strong>Benefits of Using Bundles in Salesforce CPQ:</strong></p><ul><li><strong>Simplifies Configuration</strong>: Bundles allow users to select multiple products easily, reducing configuration time.</li><li><strong>Prevents Incompatible Selections</strong>: With option constraints and product rules, users can avoid selecting incompatible products.</li><li><strong>Improves Sales Efficiency</strong>: Bundles streamline the quoting process, especially for complex products with multiple options.</li><li><strong>Flexible Pricing</strong>: Bundles allow for discounting or pricing adjustments based on group selections.</li><li><strong>Boosts Upselling/Cross-Selling</strong>: Bundles can suggest complementary products, increasing the potential sale.</li></ul><p><strong>All Possible Ways to Create Bundles:</strong></p><ol><li><strong>Static Bundles</strong>: Fixed products with no user configuration.</li><li><strong>Configurable Bundles</strong>: Users can choose and configure options.</li><li><strong>Nested Bundles</strong>: Bundles within bundles, allowing more granular control.</li><li><strong>Dynamic Bundles</strong>: Conditional products that appear based on user selections or rules.</li></ol><p><strong>For More Information connect with Me on :</strong> <a href="https://medium.com/www.linkedin.com/in/mukeshpalsf">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a1fc1331fca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dunning Management in Salesforce CPQ Billing]]></title>
            <link>https://medium.com/@mukesh.palsftech/dunning-management-in-salesforce-cpq-billing-7928f7d0794a?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/7928f7d0794a</guid>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 04:38:03 GMT</pubDate>
            <atom:updated>2024-09-03T04:38:03.253Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Dunning management</strong> in Salesforce CPQ Billing refers to the automated process of managing overdue invoices and outstanding payments. The purpose of dunning management is to improve collections by systematically following up with customers who have overdue payments, ensuring that unpaid invoices are addressed promptly and effectively.</p><h3>Purpose of Dunning Management in Salesforce CPQ Billing</h3><ol><li><strong>Automated Follow-Up</strong>: Dunning management automates the process of sending reminders and notifications to customers with overdue payments. This reduces the need for manual intervention and ensures timely communication with customers.</li><li><strong>Improved Cash Flow</strong>: By actively managing overdue accounts, dunning helps in accelerating the collection of outstanding payments, thereby improving the company’s cash flow.</li></ol><p><strong>Reduction of Bad Debt</strong>: Consistent and timely follow-up on overdue payments can reduce the risk of bad debt, as customers are more likely to pay when they receive regular reminders.</p><p><strong>Customer Retention</strong>: Effective dunning management can help maintain a positive relationship with customers by providing clear communication and flexible options for payment plans or settlements, rather than abruptly terminating services.</p><p><strong>Minimized Administrative Effort</strong>: By automating the dunning process, Salesforce CPQ Billing reduces the administrative burden on finance teams, allowing them to focus on more strategic tasks rather than manual collections follow-up.</p><h3>How Dunning Management Improves Collections</h3><ol><li><strong>Tiered Communication Strategy</strong>: Dunning management allows you to set up a series of communications that escalate based on the length of time an invoice is overdue. For example:</li></ol><ul><li><strong>First Reminder</strong>: A gentle reminder sent shortly after the due date.</li><li><strong>Second Reminder</strong>: A more formal reminder sent if the payment is not received after a certain period.</li><li><strong>Final Notice</strong>: A final warning that might include consequences, such as suspension of services.</li></ul><p><strong>Automated Actions</strong>: Salesforce CPQ Billing can automatically trigger specific actions based on dunning rules, such as:</p><ul><li>Applying late fees or penalties.</li><li>Suspending services if payment is not received within a specified timeframe.</li><li>Initiating more aggressive collection efforts if invoices remain unpaid beyond a certain threshold.</li></ul><p><strong>Customizable Dunning Process</strong>: Salesforce CPQ Billing allows for the customization of the dunning process to match the business’s specific policies and customer segments. This flexibility ensures that communications are appropriate and effective for different types of customers.</p><p><strong>Payment Options and Flexibility</strong>: Dunning management can be configured to provide customers with various payment options, such as payment plans or discounts for early settlement, which can encourage quicker payments and improve collections.</p><p><strong>Visibility and Reporting</strong>: Salesforce CPQ Billing provides reporting and analytics on overdue accounts and the effectiveness of the dunning process. This data allows the finance team to identify trends, adjust strategies, and optimize the dunning process for better results.</p><p><strong>Consistency and Professionalism</strong>: Automated dunning ensures that all customers with overdue invoices receive consistent and professional communication, which can help maintain a positive brand image even when dealing with delinquent accounts.</p><p>For More Info Connect me on: <a href="http://www.linkedin.com/in/mukeshpalsf">www.linkedin.com/in/mukeshpalsf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7928f7d0794a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disabling Salesforce CPQ Triggers in Apex !!]]></title>
            <link>https://medium.com/@mukesh.palsftech/disabling-salesforce-cpq-triggers-in-apex-cd949f039dc0?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd949f039dc0</guid>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Sun, 01 Sep 2024 06:19:53 GMT</pubDate>
            <atom:updated>2024-09-01T06:19:53.572Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Disabling Salesforce CPQ Triggers in Apex !!</strong></p><p><strong>1. Explanation</strong></p><p>Salesforce CPQ (Configure, Price, Quote) is a powerful tool that uses triggers extensively to automate business processes such as pricing, discounting, and approvals. However, there are scenarios where you might need to temporarily disable these triggers during certain operations. This can be useful during data migrations, bulk updates, or custom logic implementations where CPQ’s standard triggers might interfere with your processes.</p><p>Disabling CPQ triggers involves leveraging the CPQTriggerHandler class provided by Salesforce. This class allows you to enable or disable specific CPQ triggers selectively. By using this class, you can ensure that your custom Apex code runs without being affected by the CPQ logic, providing more control over your operations.</p><p><strong>2. Use Case</strong></p><p><strong>Scenario:</strong> You are performing a bulk update of Quote Line Items (QLIs) where your custom logic should override the standard CPQ pricing calculations. During this operation, the standard CPQ triggers should be disabled to prevent them from recalculating the prices based on the standard rules.</p><p>Steps:</p><p>1. Identify the CPQ triggers that need to be disabled (e.g., BeforeInsert, BeforeUpdate, AfterInsert, AfterUpdate).</p><p>2. Use the CPQTriggerHandler class to disable these triggers before performing the operation.</p><p>3. Re-enable the triggers after the operation to restore normal CPQ functionality.</p><p><strong>3. Code Example</strong></p><p>public class CustomQuoteUpdate {</p><p>public static void updateQuoteLineItems(List&lt;QuoteLineItem&gt; qlis) {</p><p>try {</p><p>CPQTriggerHandler.disableTrigger(‘BeforeUpdate’);</p><p>CPQTriggerHandler.disableTrigger(‘AfterUpdate’);</p><p>// Step 2: Perform custom logic</p><p>for (QuoteLineItem qli : qlis) {</p><p>qli.Custom_Price__c = calculateCustomPrice(qli);</p><p>}</p><p>update qlis;</p><p>// Step 3: Re-enable CPQ triggers</p><p>CPQTriggerHandler.enableTrigger(‘BeforeUpdate’);</p><p>CPQTriggerHandler.enableTrigger(‘AfterUpdate’</p><p>} catch (Exception ex) {</p><p>// Handle any exceptions</p><p>System.debug(‘Error during QLI update: ‘ + ex.getMessage());</p><p>}</p><p>}</p><p>private static Decimal calculateCustomPrice(QuoteLineItem qli) {</p><p>return qli.Quantity * 100;</p><p>}</p><p>}</p><p><strong>4. Limitations</strong></p><ul><li>Partial Trigger Disabling: CPQ triggers can only be disabled at specific points (BeforeUpdate, AfterUpdate, etc.). You cannot disable all CPQ logic entirely.</li><li>Global Impact: Disabling CPQ triggers affects all operations running concurrently. Ensure no other processes rely on the disabled triggers during the operation.</li><li>Governance Limits: Disabling triggers does not bypass Salesforce’s governor limits. If your operation exceeds these limits, it may still fail.</li><li>Maintenance Risks: Future updates to Salesforce CPQ might change how triggers work or introduce new ones. Regularly review and test your code to ensure compatibility.</li></ul><p><strong>5. Impact</strong></p><ul><li>Performance: Disabling triggers can improve performance for bulk operations by preventing unnecessary recalculations.</li><li>Data Integrity: Disabling triggers may lead to data inconsistencies if not carefully managed, as CPQ triggers often enforce business rules.</li><li>Custom Logic Override: Disabling CPQ triggers allows custom logic to take precedence, but this requires thorough testing to ensure it aligns with overall business requirements.</li></ul><p><strong>6. Precautions</strong></p><ul><li>Enable Triggers Post-Operation: Always re-enable CPQ triggers after your operation to restore standard functionality.</li><li>Thorough Testing: Test the operation in a sandbox environment to identify potential issues before deploying to production.</li><li>Rollback Mechanism: Implement rollback mechanisms in case the operation fails, ensuring data integrity is maintained.</li><li>Collaboration: Coordinate with other teams to ensure that disabling triggers doesn’t affect their processes.</li></ul><p><strong>7. Salesforce Reference Links</strong></p><ul><li><a href="https://developer.salesforce.com/docs/atlas.en-us.cpq_dev.meta/cpq_dev/cpq_dev_intro.htm">Salesforce CPQ Developer Guide</a></li><li><a href="https://developer.salesforce.com/docs/atlas.en-us.cpq_dev.meta/cpq_dev/cpq_dev_custom_triggers.htm">CPQ Apex Trigger Customization</a></li><li><a href="https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm">Apex Triggers in Salesforce</a></li></ul><p>This approach gives you the flexibility to implement custom logic without conflicting with Salesforce CPQ’s standard processes. However, always proceed with caution and thorough testing to ensure data integrity and system stability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd949f039dc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce Topic: Declarative Lookup Rollup Summaries (DLRS)]]></title>
            <link>https://medium.com/@mukesh.palsftech/salesforce-topic-declarative-lookup-rollup-summaries-dlrs-164fbfbe88fa?source=rss-5b345498fd34------2</link>
            <guid isPermaLink="false">https://medium.com/p/164fbfbe88fa</guid>
            <category><![CDATA[salesforce-lightning]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Mukesh Pal]]></dc:creator>
            <pubDate>Fri, 30 Aug 2024 17:57:41 GMT</pubDate>
            <atom:updated>2024-08-30T17:57:41.700Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Declarative Lookup Rollup Summaries (DLRS)</strong> is a powerful tool that allows you to create rollup summaries between objects that do not have a master-detail relationship in Salesforce. It enables rollup summary calculations using declarative tools without needing complex Apex code, making it extremely helpful for developers and administrators alike.</p><p><strong>How to Install DLRS:</strong></p><p>1. <strong>Access the GitHub Repository:</strong></p><p>o The official DLRS tool is available as an unmanaged package on GitHub.</p><p>o <a href="https://github.com/afawcett/declarative-lookup-rollup-summaries">DLRS GitHub Repository</a></p><p>2. <strong>Install the Package:</strong></p><p>o You can install DLRS in your Salesforce org using the following links:</p><p>§ <strong>Production/Developer Org</strong>: <a href="https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4J000000kCIEQA2">Install DLRS for Production/Developer</a></p><p>§ <strong>Sandbox Org</strong>: <a href="https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4J000000kCIEQA2">Install DLRS for Sandbox</a></p><p>3. <strong>Post-Installation Setup:</strong></p><p>o After installation, you need to grant the appropriate permissions:</p><p>. Go to <strong>Setup &gt; Installed Packages</strong>.</p><p>. Locate DLRS and click on <strong>Manage Licenses</strong>.</p><p>§Assign the <strong>DLRS Admin</strong> and <strong>DLRS User</strong> permission sets to the relevant users.</p><p>4. <strong>Enable Remote Site Settings:</strong></p><p>. Navigate to <strong>Setup &gt; Remote Site Settings</strong>.</p><p>. Add a new Remote Site with the URL of your Salesforce instance to allow DLRS to perform its operations.</p><p><strong>How DLRS Helps Developers:</strong></p><ul><li><strong>Eliminates Need for Apex Code:</strong></li><li>DLRS allows developers to create complex rollup summaries without writing a single line of Apex code, which simplifies maintenance and reduces technical debt.</li><li><strong>Cross-Object Rollups:</strong></li><li>It supports rollup summaries for objects without a master-detail relationship, which is not possible using standard Salesforce rollup summary fields.</li><li><strong>Support for Complex Use Cases:</strong></li><li>DLRS supports different operations like COUNT, SUM, MIN, and MAX on child records and can be triggered in real-time, scheduled, or manually.</li><li><strong>Automation and Flexibility:</strong></li><li>Developers can use DLRS to automate business processes and create flexible solutions that require aggregating data from related records.</li></ul><p><strong>Use Cases for DLRS:</strong></p><ul><li><strong>Aggregating Opportunity Amounts to a Custom Object:</strong></li><li>Roll up the total value of related Opportunities to a custom object where no master-detail relationship exists.</li><li><strong>Summing Related Object Fields:</strong></li><li>Automatically calculate the sum of related records, like summing up the quantity of items from child records to a parent record.</li><li><strong>Creating Custom Rollups for CPQ or Billing Objects:</strong></li><li>Roll up the total of invoice line items to the invoice object in a custom Salesforce CPQ or Billing implementation.</li><li><strong>Dynamic Rollups for Complex Relationships:</strong></li><li>Handle dynamic parent-child relationships where the standard rollup summary fields are not available due to a lack of a direct relationship.</li></ul><p><strong>Official Salesforce Links and Documentation:</strong></p><ul><li><strong>Salesforce GitHub Repository for DLRS:</strong></li><li><a href="https://github.com/afawcett/declarative-lookup-rollup-summaries">DLRS GitHub Repository</a></li><li><strong>Salesforce Trailhead on DLRS:</strong></li><li><a href="https://trailhead.salesforce.com/content/learn/modules/dlrs">Trailhead: Using Declarative Lookup Rollup Summaries</a></li><li><strong>Salesforce Documentation on Rollup Summaries:</strong></li><li><a href="https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&amp;type=5">Salesforce Roll-Up Summary Fields</a></li><li><strong>Salesforce AppExchange Link:</strong></li><li>DLRS on Salesforce AppExchange</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=164fbfbe88fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>