Subprocesses
Search Knowledge Base by Keyword
Subprocesses enable quick re-use of Models, by dragging and dropping them to the canvas and incorporating them in a new Model. This is particularly useful for common and recurring functionality, which can be modelled once and then re-used wherever it occurs in a system.
To embed a Model as a subprocess in another model, drag the Subprocess action to the canvas, dropping it where the subprocess will be placed. Next, select the Model to be imported. Models are displayed within their relevant project and release, and are sorted by version:
The Model will be added to the canvas as a collapsed block:
Click the “plus” button to expand the subprocess box. Next, use Arrows to connect the Start and End points of the subprocess into the existing Model.
Actions from the master model can be connected to the Start and End points of the subprocess. The Start and End points of the Subprocess can equally connect to any action in the existing model.
When you connect into a start endpoint to a subprocess, you can expand the subflow and choose a start or endpoint. Alternatively, simply drag from a collapsed subprocess or from any empty space in an expanded subprocess. You must then select the relevant start startpoint in the subprocess to which the edge (arrow) will connect. Likewise you will need to select the relevant endpoint when connecting the subprocess to a subsequent block:
If there is only one startpoint or endpoint in the subflow, this will be selected automatically.
The Start and End points of the subflow are the inputs and outputs of the subprocess, incorporating its logic into the master model. Looping is not possible, meaning that an End point of a Subprocess cannot be connected to the block in the master model from which that same subprocess is connected.
If a model is being used as a subprocess in another model, and its start and end points are removed, this will create a break in the logic of the master flow. The following warning is therefore displayed when a start or end point in an model used as a subprocess elsewhere is removed:
All Subprocesses in a given model can be expanded and collapsed simultaneously, using the “Expand” and “Collapse” option in the Format tab of the Model Editor.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-