Using the Tachyon Explorer, questions can be asked of the Tachyon client devices by users with the questioner or actioner roles . The responses can be viewed by viewers, questioners and actioners.
Details on asking questions can be found in Explorer Home page, questions and responses.
Tachyon works in real-time, so not all of the devices may be connected at the time a question is asked. Tachyon questions have a configurable duration that they will gather data for - allowing devices that connect later, within the gather data for duration, to respond.
Questions also have a configurable keep answers for duration - given that the answers from a live network can potentially get stale quickly and Tachyon questions are fast enough that you can simply ask the question again rather than relying on old answers.
Coverage and filters
You can use coverage and filters to reduce the amount of network traffic caused by asking a question. They are also useful in reducing the amount of data that is presented to the Tachyon users. Tachyon provides coverage, question filters and view filters.
- Coverage is applied before a question is asked and reduces how many Tachyon client devices get asked the question. Coverage uses the device properties that are sent by a Tachyon client when it connects to Tachyon.
- Question filters are applied at the Tachyon client after the question has been asked and use the attributes from the question responses to determine whether the Tachyon client should send the response.
- View filters are applied in the Tachyon Explorer after the responses have been sent and reduce the responses that are displayed.
For more information see Coverage, question filters and view filters.
Normally, before an action is performed a question is asked. This identifies the set of devices the action will be performed on, after the coverage, question and view filters have been applied.
Using the Tachyon Explorer, actions can be performed on the Tachyon client devices by users with the actioner role on a product pack subject to the following:
- they will need to enter their password
- if the action has been configured to use two-factor authentication, they will need to enter the authentication code
- they will need the approval of someone other than themselves with an approver role.
Details on performing actions and the approval workflow can be found in The action approval workflow.