Advanced Configuration Options (Price List)

 

autoGroupCalculationResultsInDetailsView

Groups results by the Result Group in Calculation Details.

See also – How to Group Calculation Results

Type – boolean

availableWorkStatus

Defines your own values to represent work status.

Configured on page – Administration > Configuration > Price Setting > Work Status Options

See also – Work Status Options

Type – text

Sample value – Ready,In Progress,Not touched,Discarded,For grooming

calculableObjectPreferredMapping

Sets mapping between element names and attribute numbers.

Configured on page – Administration > Configuration > Price Setting > Defaults for Price Lists and LPGs

See also – Defaults for Price Lists and LPGs

Type – json object

Sample value – {
    "ListPrice" : "attribute22",
    "ResultPrice" : "attribute23",
    "Label" : "attribute24",
    "Currency" : "attribute25",
    "Comment" : "attribute26"
}

commentHistory

If set to true, history of comments in Price Lists, Manual Price Lists and Live Price Grids is captured and displayed in the product details screen Comment History.

Configured on page – Administration > Configuration > System Configuration > General Settings

See also – General Settings

Type – boolean

Sample value – false

defaultFormula

Name of the Logic. Defines a default generic calculation logic.

Configured on page – Administration > Logics > Calculation Logic > Generic Logic

See also – Generic Logic

Type – text

Sample value – QuoteLogic

defaultGroups

Sets which objects will be assigned the same default user groups as the creator has.

Configured on page – Administration > Configuration > System Configuration > Entitlements

See also – Entitlements

Type – json object

Sample value – {
    "quote" : true, 
    "contract" : true, 
    "rebateAgreement" : true, 
    "compensation" : false,
    "pricelist" : true, 
    "manualPricelist" : true, 
    "priceGrid" : false, 
    "simulation" : false, 
    "lookupTable" : false, 
    "dataChangeRequest" : false
}

defaultPLFormula

Defines a default logic used for Price Lists.

Configured on page – Administration > Configuration > Price Setting > Defaults for Price Lists and LPGs

See also – Defaults for Price Lists and LPGs

Type – text

Sample value – PL_DefaultPriceList

defaultPLPreferenceInfo

Defines which Price List’s view preference for the output columns will be used as a template and applied to all Price Lists without individual settings.

Configured on page – Administration > Configuration > Price Setting > Defaults for Price Lists and LPGs

See also – Defaults for Price Lists and LPGs

Type – text

Sample value – [ 203 ] - Default (2020-12-03)

defaultPLUserNotification

Defines which user is notified when the calculation of a new Price List is completed. Value is one of "NONE" or "EMAIL"

Configured on page – Administration > Configuration > Price Setting > Defaults for Price Lists and LPGs

See also – Defaults for Price Lists and LPGs

Type – text

Sample value – EMAIL

doNotStoreGlobalsForDirtyPass

Disables storing the content of api.global in the transition between passes. Note: This is only applies for cases where the first pass is non-distributed.

Type – boolean

doNotUsePerProductFormulasInLists

When set to true, price list calculations and price grid calculations will use the calculation logic specified in the list configuration only and not the logic that might be defined in the product master (which usually overrides the list-defined logic).

Type – boolean

enableSubmitReasonForTypes

Enable submitter comment. For Quotes, Contracts, Rebate Agreements, Compensation Plans or Price Lists, you can allow users to optionally enter comments when they submit the document.

Configured on page – Administration > Configuration > System Configuration > My Workflows

See also – Workflows Configuration

Type – json array

Sample value – [ "Q", "CT", "RBA", "CO", "PL" ]

extraExportColumnsConfig

When downloading a price list to Excel, this option expands one row matrices into individual columns. Example: {"PLI": {"<PLI_COLUMN_NAME1>": ["<MATRIX_FIELD_LABEL1>","<MATRIX_FIELD_LABEL2>"],"<PLI_COLUMN_NAME2>": […​]}}

Type – json object

See also – Export Tables

Sample value – {
    "XPLI" : {
        "LastTransaction" : [
            "Last Price Paid",
            "Last Price Paid Date",
            "Last Price Paid Order",
            "Last Price OV Flag"
        ]
    }
}

mandatoryPLElements

Makes specified Price List outputs mandatory.

See also – How can I make Price List outputs mandatory

Type – json array

Sample value – [ "ListPrice", "Margin" ]

pricelistLogics

Defines a list of logics (sub selection of all logics) available when creating Price Lists.

Configured on page – Administration > Configuration > Price Setting > Defaults for Price Lists and LPGs

Type – json array

Sample value – [
    {
         "uniqueName" : "Chem-Pricing",
        "resultElementName":"ListPrice"
    }
]

pricelistTargetDateEditable

If set to true, it is possible to edit the target date even after the price list was calculated.

Configured on page – Administration > Configuration > System Configuration > General Settings

Type – boolean

Sample value – true

publishingTemplates_<typeCode>

Specifies Excel or Word templates used for publishing documents to XLSX, PDF or DOC formats. You need to specify the type by adding a suffix: "publishingTemplates_Q" (Q for quotes; others respectively).

Configured on page – Administration > Configuration > Templates > Publishing Templates

See also – Publishing Templates

Type – json object

Sample value – { "templates" : [ ] }

shotgunThreshold

Sets a number describing how many items will be calculated in the distributed mode.

Type – number

Sample value – 5000

startPagePanels

Allows you to define at the partition level the list of portlets that will be displayed on the Home page.

Configured on page – Administration > Configuration > System Configuration > Home Page

See also – Home Page

Type – json array

Sample value – [
    "pricelist", 
    "rebateManager", 
    "promotionManager", 
    "priceShop"
]

Found an issue in documentation? Write to us.

Â