Apply a WEIGHT, ORDER BY, or SELECT query to a Pull from List activity in your process flow.
Transcript
00:03
When using a List in your process flow, you can apply a Query in the Pull from List activity.
00:10
The Query can be set up to pull discrete entries from your List, based on specific criteria,
00:15
or to pull quantities of a specific label from entries on your List.
00:20
Applying a Query allows you to set up more complex, responsive, and flexible decision-making processes within your model.
00:29
In this case, three example process flows are already set up to demonstrate the WHERE, ORDER BY, and SELECT Queries.
00:39
When the Pull from List Quick Properties is opened,
00:42
and the drop-down under Query / Object / Array expanded,
00:47
you can see the selections available for the Query field, including WHERE, ORDER BY, and SELECT.
00:55
The first example is set up to demonstrate the WHERE Query.
00:60
Here, open the Assign Labels Quick Properties,
01:03
where you see that a weight label is assigned to each token with a uniform distribution between 200 and 600.
01:12
Next, to create a label field on the list, in the List Quick Properties, click Advanced.
01:21
In the List Properties dialog, Fields tab, click Add > Label.
01:28
Type “weight” in the Label Field.
01:32
Click Apply, and then OK.
01:38
Select View Entries to open the List entries dialog, where the weight column is now included in the List.
01:45
Then, on the right, in the Source Quick Properties, deselect Enabled to disable the Source.
01:55
When the simulation is Reset and Run at an accelerated speed,
01:59
you can see that the weight field is populated for all values in the List.
02:05
Next, apply your Query.
02:09
Open the Pull from List Quick Properties, and in the Query drop-down, select WHERE (Filter) > weight.
02:21
In the Query field, you can now set the values you wish to look for in the form of an SQL statement.
02:28
For example, you could look for an exact weight by typing “= 200”,
02:34
or you can look for a weight greater than, less than, or greater than and equal to a value.
02:42
In this case, you want to find entries with a weight between two values.
02:48
Type “> 300”, then expand the Query field and select WHERE (Filter) > weight again to add an AND statement to the query.
02:60
Then, type “< 500”.
03:04
The query is now set to find and pull values from the List that are between 300 and 500.
03:12
With the Source enabled and View Entries opened, the simulation is Reset, Run, and Paused.
03:21
Tokens pulled from the list move to the Delay activity on the left.
03:26
Click each of these tokens to see in Properties that the weight of each pulled token is within the specified range.
03:34
As the simulation is continued, you can see within the List Entries that all values remaining on the List are not in the specified weight range.
03:44
The next example demonstrates the ORDER BY Query.
03:48
Open the Pull from List Quick Properties, and in the Query drop-down, select ORDER BY (Sort) > weight.
03:60
This allows you to sort or pull entries in ascending or descending order according to their weight.
04:07
To apply ascending, type “ASC”, or to apply descending, type “DESC”, as shown here.
04:17
The simulation is Reset, Run at an accelerated speed, and then Paused.
04:24
Keep in mind that the tokens are not sorted at the Push to List activity, but at the Pull activity.
04:31
When you click the token in the Delay activity on the left,
04:35
in Properties, you can see that the weight is one of the larger values—in this case, 528.39.
04:43
This is because the Pull from list activity has sorted the pushed values and is now pulling the entries in descending order.
04:52
If you open the List Entries dialog, you see that the list is not actually sorted—again, because that happens at the Pull activity.
05:02
Next, review an example of the SELECT Query,
05:06
which allows you to reference and pull a specified quantity from a field based on the Request and Require Numbers.
05:13
In this case, open the Pull from List Quick Properties to see that the SELECT Query is set to pull from the Weight field,
05:21
with the Request and Require fields set to 100.
05:25
With the View Entries dialog open, the simulation is Reset and Run.
05:32
Instead of pulling discrete tokens or entries from the list,
05:36
the Pull from List activity pulls the specified quantity—in this case, a weight of 100—off of the label, or field, on the List.
05:46
In this example, entries are released from the List when they reach a weight of 0.
05:52
Now you can use the WEIGHT, ORDER BY, and SELECT Queries in your Pull from List activity
05:58
to set up complex, responsive, and flexible decision-making processes within your model.
00:03
When using a List in your process flow, you can apply a Query in the Pull from List activity.
00:10
The Query can be set up to pull discrete entries from your List, based on specific criteria,
00:15
or to pull quantities of a specific label from entries on your List.
00:20
Applying a Query allows you to set up more complex, responsive, and flexible decision-making processes within your model.
00:29
In this case, three example process flows are already set up to demonstrate the WHERE, ORDER BY, and SELECT Queries.
00:39
When the Pull from List Quick Properties is opened,
00:42
and the drop-down under Query / Object / Array expanded,
00:47
you can see the selections available for the Query field, including WHERE, ORDER BY, and SELECT.
00:55
The first example is set up to demonstrate the WHERE Query.
00:60
Here, open the Assign Labels Quick Properties,
01:03
where you see that a weight label is assigned to each token with a uniform distribution between 200 and 600.
01:12
Next, to create a label field on the list, in the List Quick Properties, click Advanced.
01:21
In the List Properties dialog, Fields tab, click Add > Label.
01:28
Type “weight” in the Label Field.
01:32
Click Apply, and then OK.
01:38
Select View Entries to open the List entries dialog, where the weight column is now included in the List.
01:45
Then, on the right, in the Source Quick Properties, deselect Enabled to disable the Source.
01:55
When the simulation is Reset and Run at an accelerated speed,
01:59
you can see that the weight field is populated for all values in the List.
02:05
Next, apply your Query.
02:09
Open the Pull from List Quick Properties, and in the Query drop-down, select WHERE (Filter) > weight.
02:21
In the Query field, you can now set the values you wish to look for in the form of an SQL statement.
02:28
For example, you could look for an exact weight by typing “= 200”,
02:34
or you can look for a weight greater than, less than, or greater than and equal to a value.
02:42
In this case, you want to find entries with a weight between two values.
02:48
Type “> 300”, then expand the Query field and select WHERE (Filter) > weight again to add an AND statement to the query.
02:60
Then, type “< 500”.
03:04
The query is now set to find and pull values from the List that are between 300 and 500.
03:12
With the Source enabled and View Entries opened, the simulation is Reset, Run, and Paused.
03:21
Tokens pulled from the list move to the Delay activity on the left.
03:26
Click each of these tokens to see in Properties that the weight of each pulled token is within the specified range.
03:34
As the simulation is continued, you can see within the List Entries that all values remaining on the List are not in the specified weight range.
03:44
The next example demonstrates the ORDER BY Query.
03:48
Open the Pull from List Quick Properties, and in the Query drop-down, select ORDER BY (Sort) > weight.
03:60
This allows you to sort or pull entries in ascending or descending order according to their weight.
04:07
To apply ascending, type “ASC”, or to apply descending, type “DESC”, as shown here.
04:17
The simulation is Reset, Run at an accelerated speed, and then Paused.
04:24
Keep in mind that the tokens are not sorted at the Push to List activity, but at the Pull activity.
04:31
When you click the token in the Delay activity on the left,
04:35
in Properties, you can see that the weight is one of the larger values—in this case, 528.39.
04:43
This is because the Pull from list activity has sorted the pushed values and is now pulling the entries in descending order.
04:52
If you open the List Entries dialog, you see that the list is not actually sorted—again, because that happens at the Pull activity.
05:02
Next, review an example of the SELECT Query,
05:06
which allows you to reference and pull a specified quantity from a field based on the Request and Require Numbers.
05:13
In this case, open the Pull from List Quick Properties to see that the SELECT Query is set to pull from the Weight field,
05:21
with the Request and Require fields set to 100.
05:25
With the View Entries dialog open, the simulation is Reset and Run.
05:32
Instead of pulling discrete tokens or entries from the list,
05:36
the Pull from List activity pulls the specified quantity—in this case, a weight of 100—off of the label, or field, on the List.
05:46
In this example, entries are released from the List when they reach a weight of 0.
05:52
Now you can use the WEIGHT, ORDER BY, and SELECT Queries in your Pull from List activity
05:58
to set up complex, responsive, and flexible decision-making processes within your model.
