Skip to content

Datastore Brazilian Regulations

The Datastore Brazilian Regulations calculates the rules that govern the application of resources, the maintenance and management of a portfolio in accordance with Brazilian regulations, creating a new datastore with the result of the calculations.

Parameters

The Datastore Brazilian Regulations worker must receive specific parameters in order to execute properly. When parameters are not set correctly it may cause the worker to not work as expected. This worker's parameters are separated in the following tabs: Input and Output.

Input

The Input tab contains parameters which are consumed by the worker, in order to execute its calculations.

Portfolio

Set the target portfolio using Fixed Portfolio, Get Latest or Upstream Data variants.

Workspace

Set the research workspace of the portfolio using Fixed Workspace variant. The default is using the current workspace.

CMN 4444

Select the results that are defined in the CMN 4444 regulation using Boolean variant.

CMN 555

Select the results that are defined in the CMN 555 regulation using Boolean variant.

CMN 558

Select the results that are defined in the CMN 558 regulation using Boolean variant.

Output

The Output tab contains parameters that defines the worker execution results, and how it will be provided to downstream workers.

Name

Set the output datastore name using Template Text or Upstream Data variants. Default setting is the name of the input portfolio.

Date

Set the output datastore date using Fixed Date or Upstream Data variants. Default setting is the date of the input portfolio.

Workspace

Set the workspace in which the output datastore will be saved on the platform using Fixed Workspace. Default setting is the workspace of the input portfolio.

Tags

Set the output datastore tags using Fixed Tags or Upstream Data variants. Default setting is the tags of the input portfolio.

Persist

Select if the output datastore will be saved on the platform or be a transient one (temporary during workflow execution), through the following options: Transient or Create. The default is a transient datastore.

Result

Once the worker finishes its executions successfully, it will return a result object containing the datastore to the workflow, which can be used by downstream workers. Below you can see an example of the datastore result object hierarchy.

  • Datastore (datastore)
  • ID (string)
  • Name (string)
  • Date (date)
  • Tags (list of strings)
  • Data (list of lists)

The Data component is composed of the columns common to all datastores, attributes and aggregations, including the selected properties columns. The possible columns added to the datastore are listed below.

  • "sec_gross_exposure"
  • "sec_net_exposure"
  • "port_br_regulations_avgterm_pmr_cmn_4444"
  • "port_br_regulations_avgterm_prc_cmn_4444"
  • "port_br_regulations_cvm_558_var"
  • "port_br_regulations_cvm_q11_total"
  • "port_br_regulations_cvm_q11_coupon"
  • "port_br_regulations_cvm_q11_coupon_scen"
  • "port_br_regulations_cvm_q11_dol"
  • "port_br_regulations_cvm_q11_dol_scen"
  • "port_br_regulations_cvm_q11_ibov"
  • "port_br_regulations_cvm_q11_ibov_scen"
  • "port_br_regulations_cvm_q11_ipca"
  • "port_br_regulations_cvm_q11_ipca_scen"
  • "port_br_regulations_cvm_q11_pre"
  • "port_br_regulations_cvm_q11_pre_scen"
  • "port_br_regulations_cvm_q12"
  • "port_br_regulations_cvm_q13"
  • "port_br_regulations_cvm_q14"
  • "port_br_regulations_cvm_q15"
  • "port_br_regulations_cvm_q16"
  • "port_br_regulations_cvm_q5"
  • "port_br_regulations_cvm_q7"
  • "sec_br_regulations_avgterm_pmr_cmn_4444"
  • "sec_br_regulations_avgterm_prc_cmn_4444"
  • "sec_br_regulations_cvm_558_dol"
  • "sec_br_regulations_cvm_558_ipca"
  • "sec_br_regulations_cvm_558_pre"
  • "sec_br_regulations_cvm_558_worst_total"
  • "sec_br_regulations_cvm_q12"
  • "sec_br_regulations_cvm_q13"
  • "sec_br_regulations_cvm_q14"
  • "sec_br_regulations_cvm_q15"