Available translations
loading results
Phase
The management of take profit and stop loss targets is done in phases, each with their own formula that determines the target.
Content
Phase 1 sets the initial targets, either for the Managed Stop Loss or the Managed Take Profit, and becomes active as soon as the Take Position Event validates
true. Subsequent phases allows switching to different formulas given certain market situations. The default management of phases is sequential, meaning that phase 2 comes after phase 1, phase 3 comes after phase 2, and so on.
To switch from one phase to the next phase in the sequence, the Next Phase event is used. When the Situation described in the next phase event validates
true, the switch occurs and the next phase becomes the active phase. However, management does not need to happen sequentially. By using the Move To Phase Event instead of the Next Phase Event, the system may activate any other phase and not just the one next in the sequence.
Both events may be used at the same time, and whichever event is triggered first takes precedence.
Note: Notice that stop loss and take profit phases are independent and defined separately from each other, each below the corresponding managed stop loss and managed take profit nodes.
Note: The value of the target set for a phase is expressed by a formula. Learn more about formulas and how to write them.
Tip: This explanation about phase 1 may be extended to any other phase, as they all work similarly, and it applies both for managed stop loss phases and managed take profit phases.
Configuring
Serial Number Configuration
Properties
-
initialValueallows resetting the initial state of the node to an arbitrary value.
Phase Menu
The Phase node has the following Node Menu items:
The Add Formula menu item has the following properties:
- action: Add UI Object
- disableIfPropertyIsDefined: true
- propertyToCheckFor: formula
- label: Add Formula
- relatedUiObject: Formula
- actionFunction:
payload.executeAction
- actionProject: Visual-Scripting
- relatedUiObjectProject: Foundations
The Add Next Phase Event menu item has the following properties:
- action: Add UI Object
- disableIfPropertyIsDefined: true
- propertyToCheckFor:
nextPhaseEvent
- label: Add Next Phase Event
- relatedUiObject: Next Phase Event
- actionFunction:
payload.executeAction
- actionProject: Visual-Scripting
- relatedUiObjectProject: Foundations
The Add Move To Phase Event menu item has the following properties:
- action: Add UI Object
- label: Add Move To Phase Event
- relatedUiObject: Move To Phase Event
- actionFunction:
payload.executeAction
- relatedUiObjectProject: Foundations
- actionProject: Visual-Scripting
The Add Outgoing Signals menu item has the following properties:
- action: Add UI Object
- actionProject: Visual-Scripting
- disableIfPropertyIsDefined: true
- propertyToCheckFor:
outgoingSignals
- actionFunction:
payload.executeAction
- label: Add Outgoing Signals
- relatedUiObject: Outgoing Signals
- relatedUiObjectProject: Trading-Signals
The Add Incoming Signals menu item has the following properties:
- action: Add UI Object
- actionProject: Visual-Scripting
- disableIfPropertyIsDefined: true
- propertyToCheckFor:
incomingSignals
- actionFunction:
payload.executeAction
- label: Add Incoming Signals
- relatedUiObject: Incoming Signals
- relatedUiObjectProject: Trading-Signals
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 Phase already has the required child type that the menu item may add, and only that child is allowed for that case.
Phase Children
The Phase node has the following childrenNodesProperties:
The Formula node property features the following properties:
- name: formula
- type: node
- childType: Formula
- autoAdd: true
The Outgoing Signals node property features the following properties:
- name:
outgoingSignals
- type: node
- childType: Outgoing Signals
- project: Trading-Signals
The Incoming Signals node property features the following properties:
- name:
incomingSignals
- type: node
- childType: Incoming Signals
- project: Trading-Signals
The Next Phase Event node property features the following properties:
- name:
nextPhaseEvent
- type: node
- childType: Next Phase Event
The Move To Phase Events node property features the following properties:
- name:
moveToPhaseEvents
- type: array
- childType: Move To Phase Event
The Announcements node property features the following properties:
- name: announcements
- type: array
- childType: Announcement
- project: Social-Bots
Phase Attaching Rules
The following are the Node Attaching Rules that govern the attachment of Phase with other nodes:
Compatible Types: