Today, I realized that I’ve not done a custom lines section article! A travesty of justice! Or just an oversight. Either way, here it is! This includes a controller APEX class, a VisualForce page and a Template Content that is of type Custom. Have at it below!<\/p>\n\n\n\n
This example is a lines section that groups lines by Product Family. It also rolls up lines by Product! So there will be a section of Hardware, and a rollup of hardware by product within that section (combining quantities of same products).<\/p>\n\n\n\n
APEX Class (Controller)<\/strong><\/p>\n\n\n\n
\/\/ make sure to put \/apex\/c__CustomLinesSection in the Custom Source of the Template Content\npublic class CustomLinesSectionController {\n public Map<String, Map<String, SBQQ__QuoteLine__c>> linesByByProductCodeByProductFamily {get;set;}\n public Map<String, Decimal> netTotalByProductCode {get;set;}\n public Map<String, Decimal> netTotalByFamily {get;set;}\n public CustomLinesSectionController() {\n Id quoteId = (Id)ApexPages.currentPage().getParameters().get('qid');\n linesByByProductCodeByProductFamily = new Map<String, Map<String, SBQQ__QuoteLine__c>>();\n netTotalByProductCode = new Map<String, Decimal>();\n netTotalByFamily = new Map<String, Decimal>();\n for (SBQQ__QuoteLine__c ql : [SELECT Id, SBQQ__Number__c, SBQQ__ListPrice__c, SBQQ__Quantity__c, SBQQ__ProductName__c, SBQQ__ProductCode__c, SBQQ__NetTotal__c, SBQQ__ProductFamily__c FROM SBQQ__QuoteLine__c WHERE SBQQ__Quote__c = :quoteId AND SBQQ__Hidden__c = false ORDER BY SBQQ__Number__c]) {\n \/\/ by product group.\n String family = ql.SBQQ__ProductFamily__c == null ? 'General' : ql.SBQQ__ProductFamily__c;\n if (!linesByByProductCodeByProductFamily.containsKey(family)) {\n linesByByProductCodeByProductFamily.put(family, new Map<String, SBQQ__QuoteLine__c>());\n }\n \n \/\/ by product code.\n String key = (ql.SBQQ__ProductCode__c == null || ql.SBQQ__ProductCode__c == '' ? 'null' : ql.SBQQ__ProductCode__c) + ql.SBQQ__ProductName__c;\n if (!linesByByProductCodeByProductFamily.get(family).containsKey(key)) {\n linesByByProductCodeByProductFamily.get(family).put(key, ql);\n } else {\n linesByByProductCodeByProductFamily.get(family).get(key).SBQQ__Quantity__c += ql.SBQQ__Quantity__c;\n }\n \n \/\/ net total.\n if (!netTotalByProductCode.containsKey(key)) {\n netTotalByProductCode.put(key, 0);\n }\n if (ql.SBQQ__NetTotal__c > 0) {\n netTotalByProductCode.put(key, netTotalByProductCode.get(key) + ql.SBQQ__NetTotal__c);\n }\n \n \/\/ net total by group.\n if (!netTotalByFamily.containsKey(family)) {\n netTotalByFamily.put(family, ql.SBQQ__NetTotal__c);\n } else {\n netTotalByFamily.put(family, netTotalByFamily.get(family) + ql.SBQQ__NetTotal__c);\n }\n }\n }\n}<\/code><\/pre>\n\n\n\n
APEX Unit Test Class<\/strong><\/p>\n\n\n\n
@isTest\npublic class CustomLinesSectionControllerTester {\n static testMethod void QuoteByLocation_PostInstall() {\n Product2 p = new Product2(Name='test', IsActive=True);\n insert p;\n \n Id pbid = Test.getStandardPricebookId();\n PricebookEntry pbe = new PricebookEntry(Pricebook2Id=pbid, Product2Id=p.id, UnitPrice=1, IsActive=True);\n insert pbe;\n \n SBQQ__Quote__c q = new SBQQ__Quote__c(SBQQ__Pricebook__c=pbid);\n insert q;\n \n SBQQ__QuoteLine__c ql1 = new SBQQ__QuoteLine__c(SBQQ__Quote__c=q.id, SBQQ__Product__c=p.id, SBQQ__Quantity__c=1);\n SBQQ__QuoteLine__c ql2 = new SBQQ__QuoteLine__c(SBQQ__Quote__c=q.id, SBQQ__Product__c=p.id, SBQQ__Quantity__c=1);\n insert new List<SBQQ__QuoteLine__c> {ql1, ql2};\n \n PageReference pageRef = Page.CustomLinesSection;\n Test.setCurrentPage(pageRef);\n ApexPages.currentPage().getParameters().put('qid', q.id);\n \n CustomLinesSectionController clsc = new CustomLinesSectionController();\n }\n}<\/code><\/pre>\n\n\n\n
VisualForce Page<\/strong> This is the VisualForce Page that renders the custom lines section. Notice! It doesn’t look like HTML! That is correct. The CPQ document generator requires custom content to be in a form of XML called XSL:FO. Here’s<\/a> some documentation on it!<\/p>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/morecpq.com\/wp-content\/uploads\/2021\/06\/image.png?resize=713%2C220\")
<\/figure>\n\n\n\n