Working with Segmentations

Base Segmentation

Base segmentations like currency, country, asset class are typically delivered by the source systems (e.g. a portfolio management system) and are described by a source API segmentations delivering

• the native order of the segments

• the structure of a multi-level segmentation (tree)

Derived Segmentations

In reporting we typically don’t want to list all currencies invested but a rather more optimised break down to populate a table or chart., e.g. CHF, USD + next 3 largest currencies + a rest segment (aggregating all other currencies).

Derived segmentations allow features like grouping, ordering, selection of segments on top of base segmentations or even other derived segmentations.

• mostly stored, reuse them by name

• create ad-hoc by modifiers (segmentationId<6)

Listing of segmentations

The list of segmentations allows to

• search for segmentations

• upload a segmentation from a json file

• create a new segmentation

• filter for drafts or published segmentations

• on a segmentation (icons appear when hovering):

  • duplicate/export/delete a published segmentation

  • publish/export/revert a draft segmentation

Header and Settings

• label for translation will always be segmentation_segmentationId

Segments (Grouping)

• create and define segments

• label for translation will always be segment_segmentId$

rule language

• “in”

• use normal javascript logic (!, &&, || )

Rest Segment

• define a rest segment

Ordeing

• define the order (sorting) of segments

Selection

• define segments to be mandatory