Campaign Builder Setup for:
Tabs and Columns
The block below shows a short example of a possible tab and column setup value. The names define the tab names and the columns contain the field names to the relevant fields you would like to show. Please make sure to add the "fieldpath" in front of every field you would like to add and take also note that the API name needs to be added for the fields. To add our targeting component to the setup you can simply enter the name “targeting” behind the fieldpath. To add our Price Rule component to the setup you can simply enter the name “price_rules” behind the fieldpath.
[
{
"name":"Tab 1",
"columns":[
{
"fieldpath":"ADvendio__from_Date__c"
},
{
"fieldpath":"ADvendio__until_Date__c"
},
{
"fieldpath":"ADvendio__Quantity__c"
}
]
},
{
"name":"Tab 2",
"columns":[
{
"fieldpath":"targeting"
}
]
}
]
Static Columns
These define which static columns you would like to show as a part of every tab in the beginning.
The block below shows a short example of a possible static column value. You can add more fields by adding a comma after the last field and setting the API name framed in quotes.
["Name","ADvendio__Billing_Category__c"]
Actions
The actions are relevant to offer your user some quick options while working with Campaign items. Currently we support actions to copy items, to delete items and to copy values.
Please find an example setup in the block below. You can change the boolean values (true or false) if you want to hide certain action on row level or if you want to show certain actions on Package component level.
[
{
"value":"copy",
"label":"Copy",
"isSubitemAction":false,
"isItemAction":true
},
{
"value":"delete",
"label":"Delete",
"isSubitemAction":false,
"isItemAction":true
},
{
"value":"copyValue",
"label":"Copy Value",
"isSubitemAction":false,
"isItemAction":true
}
]
Page Size
Defines the amount of records to be shown on a page. Package Items are considered as one record regardless the amount of components. Please enter a number depending on your needs.
Tab Rules
The Tab Rules define if certain fields should be hidden under conditions or if certain fields should be shown as read only or required under certain conditions.
The conditions will be connected with the logical Connector AND or OR.
A Tab Rule contains the following information:
nameconditionsreadonlyFieldshiddenFieldsrequiredFieldslogicalConnectorallFieldsReadonlyapplyRuleInChildItem
Where:
Field | Required | Description | Example |
|---|---|---|---|
| Yes | Field to evaluate | If it is a field from Campaign Item
If it is a field from current User, add the user. prefix
|
| Yes | By now, it only accepts equal operator “==” |
|
| Yes | Value to match |
|
| No | Reserved or internal use |
|
Currently the Campaign Builder manages some Tab Rules fixed in background, not available to be edited by the user to cover logic for linear packages.
Tab Rules Example
In the following example we have one rule:
Hide Sales Price
with logicalConnector AND:
when the condition is met:
user.isactive == true
hide the following field:
advendio__sales_price__c
[
{
"name": "Hide Sales Price",
"logicalConnector": "AND",
"conditions": [
{
"fieldpath": "user.isactive",
"operator": "==",
"value": "true"
}
],
"hiddenFields": [
"advendio__sales_price__c"
]
}
]
You can start the field path for the conditions either from the user object as in the example above or from the campaign item with the first relevant field, e.g. "advendio__ad_price__r.advendio__ad_spec__r.advendio__distribution__c" .
Other settings
Please take note that 2 new checkboxes were added to change settings for Price Rules.
The checkbox “Hide Apply Price Rules modal“ can be set to hide the modal which will be shown as a reminder that Price Rules will be applied while saving.
The checkbox “Display Apply Price Rules button“ is needed to be set to enable the Apply Price Rules button to be shown in the Campaign Builder.
Error Handling in Item Configuration Setting
When there is an error in one of the field values due to a wrong JSON you will get an error while saving. Errors are shown with the message: “Please check the json structure.”. If this is happening please check if the values you entered are valid following an online JSON formatter as mentioned above.
