You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
This custom schema element has been superseded by AQ_JustificationTreeV2, which offers more features. It will be removed in a future version of Blueriq.
This custom schema element represents a justification tree for the configured attribute. When you add this element to your domain schema, it looks like this:
Parameters
The following parameters are available:
| Parameter name | Required | Default value | Description |
|---|---|---|---|
| entityName | yes | n/a | The name of the entity |
| attributeName | yes | n/a | The name of the attribute within the entity for which the justification tree should be created |
| assetFormat | no | 'Text' | The asset format that should be returned for the justification tree justification texts |
Example
A Justification Tree in a response of a BaaRS could look like this:
{
"Costs": 3000.0,
"AQ_JustificationTree": {
"key": "AnnualAmount",
"values": ["3000.0"],
"justification": "A car that is over 60k has a high annual tax.",
"used_values": [
{
"key": "ModelYear",
"values": ["1993"],
"justification": null
},
{
"key": "Value",
"values": ["7000.0"],
"justification": null
}
]
}
}
Justification Tree while mapping
It might be the case that the attribute referenced by the parameters of the AQ_JustificationTree already has an attached value for the justification. This value can be set during mapping, if this was configured properly in the Configuration module.
In this case, the 'assetFormat' property will be ignored.
In the case where the justification was constructed during mapping, that value will have precedence over the value which is being constructed on the fly when the domain schema is composed. For more details on how to set the value of a Justification during mapping, please check Mapping Justification Trees for attribute values
Overview
Content Tools