Configuring Admin Settings

Admin Settings are system properties that have different values and you can use them for different purposes. You must configure admin settings to meet the business objectives of your implementation along with Custom Settings.

 To create admin settings

1. Click and click Admin. All the standard Admin Settings are displayed on the Admin home page. Based on your organizations' requirements, you can add or create new Admin settings.
2. To create a new Admin Setting, click New.
3. Enter Name, Value, and Code for the Admin Setting and click Save. Your new Admin Setting is saved and added.

Admin Settings in CPQ

The following content provides information about various admin Settings available in CPQ along with their values and purposes.

APTS_AsyncMergeCall

You can use this setting to enable asynchronous document generation for large templates. A notice is displayed when the Sales rep performs the document generation after a number of seconds/milliseconds determined by the property APTS_MergeCallTimeOut or Merge Time Callout Millis Comply System Property , and permits the Sales rep to perform other operations while the document generates in the background.

APTS_AsyncMergeEmail

You can use this setting to send a notification email to the Sales rep initiating the asynchronous document generation after generation is complete. 

Conga recommends to enable both APTS_AsyncMergeCall and APTS_AsyncMergeEmail.

APTS_DefaultEmailContactName

You can use this setting to define the default email contact name.

APTS_DisableCartActivityHistory

You can use this setting to disable the generation of activity history product configuration. When enabled, CPQ does not add entries to the Activity History related list, when you create, finalize, or reconfigure a product configuration.

APTS_DisableCartAsyncNotification

You can use the Admin Setting APTS_DisableCartAsyncNotification to turn off the email notifications you receive after completion of any async operation such as cart finalization and pricing in every type of quote or agreement. In the Split quote or agreement, the notification for cart splitting is also disabled along with finalization and pricing. If you enabled the Progress Tracker on the quote or agreement page to monitor the progress of all the async operations, email notifications are redundant and you can use this feature to avoid them.

APTS_DisableConstraintRulesOnFinalize

You can use this setting to disable the execution of server-side constraint rules to optimize performance upon cart finalization.

This feature is not supported with the Replacement type Constraint Rule.

APTS_DisableCumulativeQuantityAcrossCart

You can use this setting to disable CPQ from applying the cumulative range matrix on multiple line items of the same product.

APTS_DisablePLITimeZoneAdj

You can disable the time zone adjustment on the Effective Date and  Expiration Date fields in the Price List Item. By default, the time on the Effective Date and Expiration Date fields is adjusted based on the Time Zone of the Locale in the org. If you disable the adjustment, CPQ does not change the time you manually configured in the Effective Date and  Expiration Date fields. Refer to Adding Additional Details to a Price List Item for information about the Price List Item fields.

APTS_DisableRolldownOptimization

You can use this setting to optimize the system behavior while using custom logic in the methods invoked in the Roll Down mode.

APTS_EnableBlockingCallsOnServiceCatalog

Use this admin setting to display a spinner on the Service Catalog upon the click of the Add to Cart or Update buttons. When this admin setting is set to true, CPQ displays the spinner to ensure that the creation of related line items is completed for standalone products before you navigate away to a different page or click another button.

When this admin setting is set to false, if you quickly navigate away from the Service Catalog after clicking Add to Cart, CPQ does not create related line items for standalone products.

APTS_EnableInstallBaseFilteringAcrossAccounts

You can use this setting along with Asset Line Item Callback to display assets from multiple accounts, which are related to an opportunity, on the Installed Products page. For more information to configure the callback, see Displaying Assets from Multiple Accounts on the Installed Products Page.

APTS_EnableMultiBenefitItems

You can use this setting to control the ability of the Sales rep to apply promotions to multiple line items of the benefit product (Y). By default, this setting is disabled and CPQ applies the promotion only to the first line item of the benefit product (Y). When you enable this setting, CPQ applies the promotion to all line items of the benefit product (Y).

APTS_ExcludeOptionalProducts

You can use this setting to exclude options, bundle, and sub-bundle that are marked optional from the min/max criteria of the option group. When the Sales rep marks options or bundles as optional using the Is Optional checkbox, they are not considered in the Min Options, Max Options, Min Total Quantity, and Max Total Quantity criteria.

APTS_IncentivePricingBatchSize

You can use this setting to process the promotions in batches for a cart with a large number of line items. The batch processing is only supported for Buy X Get X and Buy X Get Y promotions with Auto Apply? enabled. You can use this feature for both regular and async pricing.

Name	APTS_IncentivePricingBatchSize
Value	Enter the number of line items to be processed in a batch. You must define the batch size based on the complexity of the cart and the number of incentives applied on the line items.
Code	Leave the field blank

APTS_LargeDocSObjects

You can use this setting to define objects as Large Objects for document generation. You can also define a batch size for each of these objects. By default, CPQ considers Proposal Line Item and Agreement Line Item as Large Objects for document generation.

APTS_LoadProductRelatedAttributesOnly

You can use this setting to enable the optimized retrieval of attributes on the cart page. When this setting is enabled, CPQ only retrieves the attributes in the cart that are associated with the product added to the cart. By default, all the attributes from Product Attribute Value, Product Attribute Value Ext, Product Attribute Value Ext 2, Product Attribute Value Ext 3, and custom Product Attribute Value Ext objects are loaded on the Cart page.

APTS_MergeCallTimeout

You can use this setting to display a timeout message whenever document generation exceeds 60 seconds.

APTS_MS_EnableNameSort

You can use this setting to specify whether the related list should be sorted by the name field in the generated document. When enabled the related lists will be printed in the merge documents in the order of the name field of the related list. 

APTS_NoISOCurrencyFieldObjects

You can use this setting to add support for custom object generation for objects that do not have a CurrencyIsoCode field (e.g., "EventRelation," "Task," "TaskRelation"). Separate Object names using a comma or new line. The setting is only applicable to templates in multi-currency org. 

APTS_NoNameFieldObjects

You can use this setting to add support for custom object generation for Objects that do not have a Name field. (e.g., "EventRelation," "Task," "TaskRelation") Separate Object names using a comma or new line. 

APTS_Password

You can use this setting to create a password for protecting Microsoft Word agreements that are generated by the application. It also allows the application to password protect generated Microsoft Word documents. 

APTS_PricingServiceUrl

You must use this setting to set the Turbo Engines URLs. For more information, see Setting Up the TurboPricing Endpoint URLs.

APTS_PriceListItemCustomFields

You use this setting to auto-retrieve the custom fields in the onPriceItemSet() method in the Pricing Callback Class. For more information on Pricing Callback methods, see Pricing Callback Class.

APTS_ProposalConfig

You can use this setting to enable pdf security on the generated Quote/ Proposal document. Before defining this setting you must configure Enable PDF Security and PDF Owner Password.

<ProposalConfig>
<PDFSecurityDefault>
<CanPrint>true</CanPrint>
<CanCopy>true</CanCopy>
<CanChange>false</CanChange>
<CanAddNotes>true</CanAddNotes>
<CanFillFields>true</CanFillFields>
<CanAssemble>false</CanAssemble>
</PDFSecurityDefault>
</ProposalConfig>

You can also use this setting to define the line and option sequence.

<ProposalConfig>
<SortSpec>
<SortObjects>
<SortObject>
<Name>Apttus_Proposal__Proposal_Line_Item__c</Name>
<SortFields>
<SortField>
<Name>SequenceLine__c</Name>
</SortField>
<SortField>
<Name>SequenceOption__c</Name>
</SortField>
</SortFields>
</SortObject>
</SortObjects>
</SortSpec>
</ProposalConfig>

APTS_RollUpOptionNetAdjustment

You can use this setting to display the adjustments on options at the bundle and summary totals level.

APTS_SortDocumentsDesc

You can use this admin setting to sort the documents generated on the Doc Gen page, in descending order of the creation date by defining it as true. If this setting is not configured or set to false, the documents are sorted in ascending order of creation date, by default.

APTS_UpdateViewProductClasses

You can use this setting to execute the Category Maintenance batch job for the changes you make modifications to existing records instead of executing the batch job on the entire category definition.

Name	APTS_UpdateViewProductClasses
Value	Leave the field blank
Code	Enter the Product Classification records of the newly added products.  These records are created after you associate products to the category.  In case, you want to execute a maintenance batch job for the entire definition, clear the Code field, and then execute the Category Maintenance batch Job.

APTS_UpdateViewApiBatchSize

You can use this setting to specify the batch size for the Category Maintenance batch job when the job is executed using the exposed global Apex method CPQWebService.updateHierarchyViews(). You must specify a batch size value only when you notice limit exceptions in batch jobs because of complex categories with a lot of hierarchy levels. In such cases, you must decrease the batch size to execute the batch jobs successfully.