How it works

Data is transformed by doing HTTP requests to RPS Engine API.

All HTTP requests must be authenticated using Identity API.

One HTTP request can contain one or more transformations requests as explained in the Transform API documentation.

Transformation process

  1. RPS Engine API receives an HTTP request of transformations from a client
  2. request contains
  3. RPS Engine API retrieves, from RPS CoreConfiguration, the rights context which correspond to the sent evidences
    1. If rights context is Not defined then a null value is returned as transformed value
    2. if rights context is Can Read then requested data instances' value is returned as transformed value
    3. if rights context is Can Transform then
      1. RPS Engine API retrieves from RPS CoreConfiguration the processing context which corresponds to the pushed evidences
      2. If the processing context is valid then
        1. The corresponding transformer sequence for the given processing context and for the requested data instances is retrieved from RPS CoreConfiguration
        2. The list of transformers belonging to the retrieved transformers sequence is applied to the input data instances in order to transform it
        3. The transformers sequence's result is returned as transformed value
      3. If the processing context is not valid then anull value is returned as transformed value

Examples of data entities before transformation:

{customer, name}Laura, John, ...
{transaction, amount}12'450 CHF, 230 EUR, ...
{address, city}Rome, Paris, ...
{account, IBAN}ES7921000813610123456789, ...

Examples of data entities transformed using the RPS Engine API :

{customer, name}: Maurizio, Maurizio, ...
{transaction, amount}: @__asds33df23qaasdasd, @__asdaseE2_wwwd, ...
{address, city}: 3fa85f64-5717-4562-b3fc-2c963f66afa6, ...
{account, IBAN}: AA0034534058930459304593, ...