Q-points usage
Q-points are points that are used when flows are executed. These points are later used to control the usage of Qflow Cloud licenses. All flow steps have an assigned number of Q-points that are used when the step is executed. Qflow offers two types of licensing: one based on consumption and the other based on users, which affects the number of points each step consumes.
There are steps (service task and script task) that require an extra effort for the tool to execute them. These steps, aside from the initial usage, also have an assigned number of Q-points per second that will be used while the step is being executed.
User-based licensing
In this type of licensing, only interactions performed by external users and those steps that involve code execution consume points. The remaining steps have an assigned amount of 0 Q-points.
Step |
Starting Q-points |
Q-points per second of execution |
|---|---|---|
Start event (by an external or anonymous user) |
20 |
0 |
User task (by an external user) |
20 * |
0 |
Service task (Integration) |
1 |
0.1 |
Service task (Connector) |
10 |
0 |
Script task |
1 |
0.1 |
* User task point consumption: Each task response performed by an external user consumes 20 points.
Consumption-based licensing
Step |
Starting Q-points |
Q-points per second of execution |
|---|---|---|
Start event |
10 |
0 |
Start event (by an external or anonymous user) |
20 |
0 |
User task |
3 + 2 ** |
0 |
User task (by an external user) |
3 + 20 ** |
0 |
User notification task |
4 |
0 |
Async service task |
2 |
0 |
Formula task |
2 |
0 |
Call activity |
5 |
0 |
Gateways |
2 |
0 |
Subprocess |
2 |
0 |
Timer event |
2 |
0 |
Service task (Integration) |
1 |
0.1 |
Service task (Connector) |
10 |
0 |
Script task |
1 |
0.1 |
- ** User task point usage
The execution of user task has the following consumptions:
Task instantiation: 3 points.
Task response by system user: 2 points.
Task response by external user: 20 points.
Any steps that are not in this list have an assigned Q-points number of 0.