Bloc List
The Bloc List component allows you to retrieve lists of Blocs in various ways, some include ways of getting data from these blocs.
This tool is useful for building dynamic navigation around your system. Perhaps you may want to load certain blocs based on a specific criteria like the value of data in those blocs. This tool is also used for other features in the Bloc Settings, for example "Can Assign Users to Other Blocs"
Another popular use for this tool is to get a quick overview of data in other blocs based on certain values you may want to check.
Parameter | Description |
Type Module name | If you want to load a list of Blocs outside of the existing module |
Select How the blocs get displayed | Allows you to choose how the blocs get displayed on the screen (More info on each option is below) |
As an autocomplete field
As a dropdown field
As Buttons/Links to Click on
Links with Latest Data
A normal input field will appear, however when you begin typing it will search/autocomplete all the blocs available to you for clicking (useful if there are a large number)
A dropdown select field will appear with the available blocs.
Buttons will appear, in a similar style to a list of blocs in any module.
Lists links with the latest values in the bloc (can be filtered based on a look up, see below for information). It also includes the number of entries.
It is possible to use another bloc entirely to filter the blocs you see based on values you would like to match.
For example, even though a module might have 4 Blocs, let's call them Bloc 1, Bloc 2, Bloc 3, Bloc 4, it is possible that you may only want to see Bloc 1 and Bloc 3 for one reason, and Bloc 2 and 4 for another.
Using this feature, you can create those rules using a bloc of your choosing.
This feature was originally built to allow customers to filter Test Types. So for instance, for 1 unit they wanted to load all of the tests for that Unit Type, and then load a series of different tests for a different unit.
Parameter | Description |
Type Module Name | Used for deciding what module to look up. |
Select the local field to watch | Select a local field whose data is used to compare against the filtering bloc. |
Select the bloc to use as the filter | Having chosen the module, you can now select the bloc that will be used. |
Select remote field from the bloc to compare with local field data | The filtering bloc will need a field that contains the data you will be comparing against. |
Select remote field from the bloc that contains the bloc names. | With this parameter you set the field that will contain the bloc names, these names will be how the filtering is determined. |
Caution: This feature relies on Bloc names not changing. The titles are used as the means of joining/filtering what to load. We hope to improve this in the feature to allow for Bloc name changes after the field is created.
If your list of blocs are appearing as "buttons" or "links with latest data" it is possible to attach data to that url. This means when you load the url the fields with that data will get populated:
https://url....?urlFieldSlugData={"part_number":"PART1"} would populate a field with the field slug part_number with the value PART1.
This option becomes particular powerful in combination with the Data Filtering Field parameter set on the bloc that is being linked to. Using this you could load a list of blocs, click on one and instantly just see the data you are concerned with without seeing anything else.
Parameter | Description |
Choose Local Field to get data from | Choose the local field whose data will feed into the URL. For example the local field might "Persons Name", the persons name will then get added to the url |
Type Field Slug to Update | You must type the field slug of the field in the other bloc that you intend on populating. Note: The reason for having to manually type the field slug is because it is not possible to choose this field using selections because of the dynamic nature of how the blocs load. We will never know what blocs are loading until the user starts using the front end. |
This option allows us to choose the fields that will appear in the list of blocs. In the example below there is just one field chosen: "Test Result". Note: We are forced to type field slugs because it is not possible to know what blocs will be loading on the front end.
To see data for that bloc, the field slug must exist in the bloc, otherwise it will just appear as if there is no data. In the example above for instance, it could be said Bloc 3 either has no data added or has no field called "Test Result".
For the "Links with Latest Data" option, this feature allows you to filter data based on values in your bloc. This means it will not necessarily just get the latest value, but it will get the latest data that contain values from fields you are using to look up data.
Caution: For similar reasons as the options above, field slugs must be identical across any blocs you would like to filter data by.
Last modified 1yr ago