How to create a dependency

Avatar
Bobby Beauregard
Follow

In LogCheck, you have the option to suspend or activate certain logs depending on the state of another log within the same Location. We call this relationship a dependency.

An example of a when to use a dependency is illustrated in the example below:

Example:

Lets say that you routinely record the hot water supply temperature and hot water return temperature on a boiler, but ONLY when that boiler is running. In this situation we can make three Logs in LogCheck to capture this data.

  1. "Boiler Status" (parent log)
  2. "HW Supply Temperature" (dependent log)
  3. "HW Return Temperature" (dependent log)

Since you only record the temperature logs when the boiler is running, you should make each of the temperature logs depend on the boiler status log. If the boiler status is marked as OFF, then the temperature logs will be suspended, but if the boiler status is marked as RUNNING then the HW Supply Temperature and HW Return Temperature logs become activated and will become due to be checked.

In order to set up a dependency, you must first create the “parent log” and the “dependent log(s)” on the LogCheck mobile app. The “parent log” must always be a toggle log, while the “dependent log(s)” can be any type of log. For help creating new logs please visit our articles on creating toggle logs and creating numeric logs.

Once your new logs are created on the mobile application, hop over to the LogCheck website and navigate to the Location in which these logs exist.

Step 1: Click "Edit" to the far right of the first "dependent" log

SC11.jpg

Step 2: Click the "Suspend Unless" dropdown menu

SC12.jpg

Step 3: Select the "parent" log from the list

SC13.jpg

Step 4: Select the toggle option that activates the "dependent" log

SC14.jpg

Step 5: Click "Save Changes" at the bottom of the page

SC15.jpg

Step 6: Repeat for any other "dependent" logs

Step 7: Review the Location page and "parent log" page

SC16.jpg

SC17.jpg

 

 

 

Comments

0 comments
Article is closed for comments.
Powered by Zendesk