Relation Flowchart
Show record relation in flowchart
Last updated
Show record relation in flowchart
Last updated
Labii ELN & LIMS provides a widget called the Relation Flowchart, which enables the establishment of record relationships using ForeignKey or ForeignKeys. This functionality is particularly useful for visualizing connections between different entities within the system. For example, you can illustrate how a box is stored in a refrigerator, which, in turn, is located in a laboratory. The Relation Flowchart offers a clear overview of such relationships.
One of the primary applications of the Relation Flowchart is in sample management. For instance, you can track the journey of a blood sample, from its use in DNA extraction to the creation of a library for deep sequencing.
Before using the Relation Flowchart, ensure that the following requirements are met:
The table contains ForeignKey or ForeignKeys columns.
Multiple records refer to each other using the same column.
To utilize the Relation Flowchart, follow these steps:
Add a section containing the Relation Flowchart widget to your interface.
Click on the "Edit" button to access the configuration settings.
Choose the specific column you wish to track within the flowchart.
Select a Text Column that will display the text between two boxes, providing additional context for the relationship. If you want to use the column name itself, please choose 'Self.' Alternatively, if you wish to exclude any text, please select 'None.'
Determine the flowchart direction based on your preference.
Check "Should reverse arrow" to reverse the arrow direction.
Click "Submit" to save your configuration.
It's important to note that when building a relation flowchart using ForeignKeys, multiple paths can be created. However, when using a single ForeignKey, the flowchart will have only one path.
Additionally, you can click on the individual boxes within the flowchart to view more detailed information about the associated records. Please be aware that the loading speed of the widget might be slightly slower due to real-time searching of upstream and downstream connections.
