Price List Type (PLTT)
- Štěpán Vacek
Since version 14.0
Fields
Field | Availability | Description |
|---|---|---|
| Release 10.0 | JSON array with list of actions (Context Links). See more in the description below. |
| Release 8.0 | Name of the matrix logic which will supply values for the second dimension (i.e. key2 field) for each item. |
| Â | Name of the logic which will be used to calculate the header of the Price List. |
| Release 8.0 | Name of the element of the matrix logic which returns the values for the second dimension. |
| Release 9.0 | List of Custom Mass Action logic names which can be used on the LPG detail page. |
| Release 8.0 | Name of the price list logic. This logic will define the custom input fields and then calculate every line of the Price List. |
Contextual Actions
Contextual Actions are actions, which could be performed from the price list/grid detail page. They will be represented by special buttons at the top of the Price List detail page. For example of usage, see Price List Impact Simulation - Usage.
Sample of contextualActions content (with placeholders instead of some values)
[
{
"targetPage": "newModelPage",
"targetPageEntityType": "MODEL_CLASS_NAME",
"targetPageTarget": "drawer",
"targetPageInputs": {
"FIRST_STEP_NAME": {
"FIRST_TAB_NAME": {
"INPUT_FIELD_NAME_1": "VALUE_1",
"INPUT_FIELD_NAME_2": "VALUE_2"
}
}
}
}
]The contextual actions are configured as context linking. The general meaning of the context linking parameters is described on page Context Linking. This article describes only the special differences used by contextual actions.
targetPage - name of the page, which should be called. The value newModelPage is one of the constant’s value available in AppPages. Note, that the value newModelPage is supported only here in Contextual Actions, but in the future it may be also supported in Context Linking generally.
targetPageEntityType - The name of the Model Class used to calculate the price list simulation.
targetPageTarget - Defines, how the link is opened. The value drawer means, that the content of first Tab (expected to have some input fields) of the first Step of the model will be displayed on the right side of the Price List detail page.
targetPageInputs - values passed to the inputs of the first Tab of the first Step of the Model. To pass dynamically a value from the Price List entity, use the field name in composite brackets - e.g.
{typedId}, to pass in the actual value of typedId field of the price list/grid, from which we’re calling the context action.
Found an issue in documentation? Write to us.
Â