The Security Remapping remaps symbology of securities inside a Everysk portfolio. It can be used to correct securities with symbology not in line with Everysk's standard, based on a datastore containing the correct symbology for each security. After a successful execution, the worker will return a remapped portfolio as result.
The Security Remapping 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 parameters is separated in the following tabs: Input and Output.
The Input tab contains parameters which are consumed by the worker, in order to execute it's calculations or actions.
Set the research workspace of the portfolio using Fixed Workspace variant.
1.3 Remap Datastore
Set the research workspace of the datastore using Fixed Workspace variant.
The Output tab contains parameters that defines the worker execution results, and how it will be provided to downstream workers.
Set the workspace in which the remapped portfolio will be saved on the platform using Fixed Workspace.
2.4 Storage Mode
Select if the result portfolio will be saved on the platform, update an existing portfolio or be a transient one through the following options: Transient, Create or Update.
Once the worker finishes it's executions succesfully, it will return a result object containing the remapped portfolio to the workflow, which can be used by upstream workers. Below you can see an example of the Security Remapping's result object hierarchy. You can check the Output Types article to learn more about result objects types.
- Portfolio (portfolio)
- ID (string)
- Name (string)
- Tags (list of strings)
- Date (date)
- Base Currency (number)
- NLV (number)
- Securities (list)
- ID (string)
- Status (string)
- Instrument Class (string)
- Symbol (string)
- Label (string)
- Quantity (number)