...
| Column Name | Data Type | Description |
|---|---|---|
| strategy_id | integer | |
| strategy_name | text | name of the strategy .. (in auto generated strategy definitions, the ticker is appended to the end of the name for single security strategies to distinguish amongst multiple bonds issued by the same issuer) |
| strategy_type | text | user defined field intended to group similar strategies into one e.g. 'by_user_asset_class' or 'by_custodian' or 'by_security_for_Equities' etc. |
| username | text | this is the username (e.g. parent or rm) to whom the strategy belongs |
| user_type | text | e.g. parent, rm |
| strategy_definition | jsonb | defines how the transactions inside this strategy will be selected. Further information is here |
| latest_record_date | date | this stores the latest date to which this strategy has been calculated (i.e. date to which results are available in table strategy_records) |
| success_achieved | boolean | whether strategy calculation was successful or not (null if never run, false if there was an error, true if all went well) |
| run_results | jsonb | meta data of the strategy calculation e.g. how many tickets etc |
| system_generated_strategy | boolean | true if the strategy definition was generated automatically by Canopy |
| last_run_at | date | |
| created_at | date | |
| updated_at | date |
...