Available translations
loading results
Trigger Stage
The trigger stage deals with monitoring the market in search of trading opportunities with the corresponding strategy.
Content
A trading system may have multiple strategies designed for the same market.
An important aspect of trading systems is that they are allocated a certain amount of capital (see the base asset parameter of the trading session). As a consequence, strategies within a trading system share a certain capital allocation.
The logic behind the concept of the trigger stage assumes that different strategies within a trading system may be specialized for trading in different market situations. The trigger stage in each strategy is, therefore, the mechanism by which any particular strategy within the trading system may be selected to trade, given any particular market situation.
The triggering-on of a strategy effectively blocks the selection of any other strategy in the trading system and reserves the whole capital allocation for the one strategy selected, until the strategy is triggered-off.
Therefore, if certain strategies are meant to trade under the same market situations and open trades concurrently, then those strategies should be deployed in separate trading systems.
Once a strategy is triggered, the strategy may decide—or not—to take a position. If a position is taken, then the rest of the stages eventually become active.
However, the strategy may also be triggered off without taking a position. When a strategy is triggered off, the trading system goes back to monitoring the trigger-on definitions for all strategies, and capital is released to be used by whatever strategy is triggered-on next.
Trigger Stage Menu
The Trigger Stage node has the following Node Menu items:
The Add Missing Events menu item has the following properties:
- action: Add Missing Children
- label: Add Missing Events
- relatedUiObject: Trigger Stage
- actionFunction:
payload.executeAction
- actionProject: Visual-Scripting
- relatedUiObjectProject: Foundations
The Add Announcement menu item has the following properties:
- action: Add UI Object
- label: Add Announcement
- relatedUiObject: Announcement
- actionFunction:
payload.executeAction
- relatedUiObjectProject: Social-Bots
- actionProject: Visual-Scripting
The Delete menu item has the following properties:
- action: Delete UI Object
- actionProject: Visual-Scripting
- askConfirmation: true
- confirmationLabel: Confirm to Delete
- label: Delete
- iconPathOn: delete-entity
- iconPathOff: delete-entity
- actionFunction:
payload.executeAction
Tip: When a menu item is grayed out, it means that Trigger Stage already has the required child type that the menu item may add, and only that child is allowed for that case.
Trigger Stage Children
The Trigger Stage node has the following childrenNodesProperties:
The Trigger On node property features the following properties:
- name:
triggerOn
- type: node
- childType: Trigger On Event
- autoAdd: true
The Trigger Off node property features the following properties:
- name:
triggerOff
- type: node
- childType: Trigger Off Event
- autoAdd: true
The Take Position node property features the following properties:
- name:
takePosition
- type: node
- childType: Take Position Event
- autoAdd: true
The Announcements node property features the following properties:
- name: announcements
- type: array
- childType: Announcement
- project: Social-Bots
The User Defined Code node property features the following properties:
- name:
userDefinedCode
- type: node
- childType: User Defined Code
- autoAdd: false
Trigger Stage Attaching Rules
The following are the Node Attaching Rules that govern the attachment of Trigger Stage with other nodes:
Compatible Types: