+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-2596

Access to contingent/OCO orders via TradeManager interface before the initial order is filled

action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

I'm using the TradeManager interface to keep track of my orders and positions to monitor risk. I've found that at least with PaperTrader, I can see new orders but if there's an attached Profit / Stop order then these only appear after the initial entry order has been filled. Further, while OCOGroupId exists so I can see which orders are part of the same group, I am not able to see which order triggered the OCO order.

This prevents me from assessing risk at the point orders are placed. It is really essential for me if there was a way that for any sent/submitted order to check what any attached exit orders are before the initial order is filled.

I suggest that maybe:

The TradeManager.Order structure be enhanced to include a list of any contingent orders and that a mechanism exists to query/obtain details about these orders.

When an OCO order finally appears via the TradeManager order events API, it includes a reference to the OrderID that triggered the submission.

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates