This page is under construction. Topics to be handeled
...
Global profile vs. mapped profile (vs. profile in reportType or fixed profile as parameter)
...
Just a bunch of parameter values
...
Reference = report order parameters + solution invented non-ordering parameters, see also ReportCSAM
...
use draft mechanics
...
full text search
...
A Cinnamon reporting solution is very flexible allowing to introduce new parameters to be used in orders and report types. As most parameters should only be needed in report orders they should have a default value that can depend on the client type, product type or portfolio. To set parameters to meaningful defaults Cinnamon proposes to use profiles.
Types of profiles
A Cinnamon reporting solution can support multiple types of profiles:
Profile type | Description |
---|---|
Global Profile |
|
Product / Client Type Profile |
|
Portfolio Profile |
|
User Interface
The user interface supports
Searching for a profile by id, name or contents
Search & replace parameter values in multiple profiles
Creating, duplicating, deleting profiles
Exporting & uploading of profiles
Publishing draft profiles
Compare profiles
Structure of a profile
The structure of a profile is very simple and contains a parameters object identical to a report order:
Code Block | ||
---|---|---|
| ||
{
"profileId": "sample_fixedIncomeProfile",
"name": "Sample profile for fixed income portfolios",
"parameters": {
"attributionSegmentations": [
"currencies<6",
"ratings<6"
],
"assetBreakdownSegmentations": [
"currencies<6",
"ratings<6",
"durationBuckets",
"sectors<6",
"countries<6"
],
"positionListSegmentation": "currencies<6",
"attributionModel": "Brinson",
"riskModel": "factorModel",
"cashflowFigures": [
"coupon",
"principal"
],
"keyFigures": [
"numberOfCusips",
"effectiveDuration",
"yieldToMaturity",
"averageRating"
]
}
} |