FennEdge Learn · Programming

DAS Trader Advanced Hotkey Script Course

Understand the code. Inspect the state. Verify the outcome. A detailed path through Advanced Script: language, data structures, order objects, event workflows and complete practice projects.

Plan about 1046 minutes including reading, worked examples, and each lesson exercise; actual time varies.

36Lessons≈1046Est. minutes—Sign in to save progress
15
Lesson 15 of 36 · About 32 min

DAS Order Objects: Construct, Inspect and Submit

Understand NewOrderObj, properties and Send as separate stages.

Three representations of an order

Prerequisite: object state and Load/Send. A Montage ticket, a newly constructed order object and an order returned from a submitted-order search are different things. NewOrderObj() creates an object you configure. GetOrderObj(filter) retrieves a matching order from the platform’s order records; do not assume it finds an unsent draft. The construction pattern below is a code-reading and simulator-preparation exercise.

A fully explicit draft

Replace the account and route with values verified in a training environment. MSFT, quantity 10 and price 25 are hypothetical teaching inputs. Creating and inspecting the draft does not send it; the terminal Send call is commented so the copied example remains a draft.

Working example

$feDraft = NewOrderObj();
$feDraft.Account = "TR_PRACTICE";
$feDraft.Symbol = "MSFT";
$feDraft.Side = "B";
$feDraft.Share = 10;
$feDraft.Type = "L";
$feDraft.Route = "LIMIT";
$feDraft.Price = 25.00;
$feDraft.Tif = "DAY";
$feDraft.ShowObject();
// Simulator execution boundary, after reviewing the complete draft:
// $feDraft.Send();

Field-by-field reasoning

Account selects the account; Symbol identifies the instrument; Side and Share express direction and requested quantity. Type describes order mechanics, Route selects an execution destination, Price has meaning under that type, and Tif describes duration/session policy. LIMIT is a documentation example, not a universal broker route. Updating only Route while leaving Type from another configuration can create an inconsistent draft. Set all dependent fields together.

Inspecting status and lifecycle

The official object screenshot lists Account, Symbol, Price, Share, Open, Side, Tif, Route, RefNum, Status and Type, plus Clear, Send and Cancel methods. It does not enumerate every Status value or fully define Open. Inspect the current build and reconcile with Orders before interpreting Open as a remaining quantity. Clear is not a substitute for cancelling a submitted order. Send is a method and uses parentheses; the source documents a one-order-per-second restriction at that revision, not a current universal throughput promise.

Exercise and worked answer

A draft changes Route from a limit route to a market route but leaves Type="L" and Price=25. What must be reviewed? Answer: the route/type pair, price requirements, TIF and the actual object after edits. Do not infer type conversion from the route name. In a simulator, record the submitted object’s RefNum and platform acknowledgement separately; successful local construction is only the first stage.