Page Comparison

• This interface delivers the current data availabiliy for all portfolios

• The usage is mainly to feed the Scheduler Service to automatically schedule reports when data get's available

• Report scheduling logic (given orders, portfolios availability and existing executions)

The following rules should be adhered to by any response and will eventually be checked when consuming a response:

Consistency Rules

* all portfolios available should be listed
* the list of qualities should not include duplicates

/portfolio/availability

portfolioId (optional)

string

The id of the portfolio (or consolidation) in the data source

/portfolio/availability

• This interface delivers all portfolios of a location

• The usage is mainly to feed the Data Scope Service where the lists are tailored to represent a users data scope

• Data scope calculation

The following rules should be adhered to by any response and will eventually be checked when consuming a response:

Consistency Rules

* Every portfolioId is a valid portfolio (e.g. returns data for /portfolio/masterdata)
* The list of portfolios is a set (no duplicates)

/portfolio/bylocation

location

string

The id of the location

• GLOBAL (this location will deliver all the portfolios)

• CH

• SG

• etc.

/portfolios?location=CH

• This interface delivers all portfolio roles for a given user (e.g. if he is PM or CPM)

• The usage is mainly to feed the Data Scope Service tailor portfolio access

• Data scope calculation

The following rules should be adhered to by any response and will eventually be checked when consuming a response:

Consistency Rules

* Every portfolioId is a valid portfolio (e.g. returns data for /portfolio/masterdata)
* portfolioIds are unique within the response (no duplicates)

/user/portfolioroles

userId

string

The id of the user:

• example bmpi: marcus.braendle

• example CSAM: F883476

/user/portfolioroles?userId=james.bond