Available translations

Process Definition

foundations.png
process-definition.png
The process definition node groups all definitions required for a process to function. The Multi-Time-Frame-Market Process deals with time frames of one hour and above. The Multi-Time-Frame-Daily Process deals with time frames of 45 minutes and below.
Content
As hinted above, most bots—in particular indicators—have two different processes. The reason is that different data structures need to be handled in different manners. The Multi-Time-Frame-Daily process handles daily files, while the Multi-Time-Frame-Market process handles market files.
The Multi-Time-Frame-Market process deals with time frames of one hour and above. Because these time frames produce relatively small numbers of records, the process builds one single file per time frame spanning the whole market history—hence the name Multi-Time-Frame-Market.
On the other hand, the Multi-Time-Frame-Daily process deals with time frames below one hour. These time frames produce huge numbers of records, therefore, the corresponding data must be fragmented in multiple files. The Multi-Time-Frame-Daily process builds one file per day for each time frame—hence the name Multi-Time-Frame-Daily.
Properties
  • codeName is the name of the process as used within the code of the system.
Initial Values
These are the Initial Values for Process Definition configuration:
 {
    "codeName": "Multi-Time-Frame-Market|Multi-Time-Frame-Market|From-One-Min-To-Multi-Time-Frame-Daily|From-One-Min-To-Multi-Time-Frame-Market",
    "normalWaitTime": 0,
    "retryWaitTime": 10000,
    "framework": {
        "name": "Multi-Time-Frame-Market|Multi-Time-Frame-Market|From-One-Min-To-Multi-Time-Frame-Daily|From-One-Min-To-Multi-Time-Frame-Market"
    }
}
Examples
This is a list of properties featured by the Process Definition configuration. Expanding a property shows sample values for the property extracted from the current Workspace.
Process Definition Menu
The Process Definition node has the following Node Menu items:
The Configure menu item has the following properties:
  • action: Configure
  • label: Configure
  • iconPathOn: configuration
  • iconPathOff: configuration
  • dontShowAtFullscreen: true
  • actionFunction: uiObject.configEditor.activate
The Add Missing Items menu item has the following properties:
  • action: Add Missing Children
  • label: Add Missing Items
  • actionFunction: payload.executeAction
  • actionProject: Visual-Scripting
  • relatedUiObjectProject: Foundations
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
Process Definition Children
The Process Definition node has the following childrenNodesProperties:
The Process Output node property features the following properties:
  • name: processOutput
  • type: node
  • autoAdd: true
The Process Dependencies node property features the following properties:
  • name: processDependencies
  • type: node
  • autoAdd: true
The Status Report node property features the following properties:
  • name: statusReport
  • type: node
  • autoAdd: true
The Execution Started Event node property features the following properties:
  • name: executionStartedEvent
  • type: node
  • autoAdd: true
The Execution Finished Event node property features the following properties:
  • name: executionFinishedEvent
  • type: node
  • autoAdd: true
Process Definition Attaching Rules
The following are the Node Attaching Rules that govern the attachment of Process Definition with other nodes:
Compatible Types: