<< Back to Public Website

Britest Facilitator Support Tool

Please follow the instructions below to download and install the Facilitator Support Tool software. 

Installation Guide

1. The Facilitator Support Tool requires the extended .NET 4.0 Framework to operate. This can be downloaded and installed from the Microsoft website: http://www.microsoft.com/en-us/download/details.aspx?id=17851

2. Download the *.zip file from the link at the bottom of this page.

3. Extract all of the contents to a folder on your computer, including all of the *.dll files. 


Windows Vista, 7 and 8 has an extraction facility built in. For Windows XP, you can use software such as:


Facilitator Support Tool Poster
Printable Poster Download
4. Run the 'Facilitator Support Tool.exe' file. 

5. The software interface should open as shown below: 



Troubleshooting

If the ribbon menu is missing when you open the software (like the image below):



This most likely means that the extended.NET 4.0 framework has not installed correctly.

Please revisit and download the software using this link:
http://www.microsoft.com/en-us/download/details.aspx?id=17851
Once this is complete, try running the Facilitator Support Tool software again.

 

Other Issues

Although the Facilitator Support Tool has been tested extensively during its development, there is always a possiblility of a bug occuring in the software. If whilst using the software you are presented with a "BUG FOUND" screen, please click on the screen and press Ctrl + C on your keyboard. Please paste this into an email and send to jeremy.double@britest.co.uk

Please describe what you were trying to do at the time of the error. We will attempt to fix the problem and get back to you as soon as possible.

Tips for using the tool

The following suggestions will help you to avoid problems when using the tool:

  • For each new study, create a separate folder to contain the files from the study.  This folder will contain the main file for the study (which will have a .fst file extension), plus folders generated by FST to contain the other files such as the Transformation Maps, PDDs etc.
  • When you need to move or copy the study, make sure you move or copy the whole folder containing the study.
  • Make sure all the folders and files used by the study are available for both read and write access.
  • Make sure that all graphic files (Rich Pictures, Transformation Maps etc.) have the correct file extension (.jpg .bmp .png etc.) Using plain filenames without a file extension can cause an error when generating a report.
  • Prefer .jpg and .png image file formats over .bmp.  
  • It’s probably best to work from a local disk (e.g. C: ), and afterwards, if needed, copy the study to a shared drive.  If you need to edit a study stored on a shared drive, first copy it to your local drive, then work on the local copy, and when finished copy the updated version back to the shared drive.
  • There is no auto-save feature, so please save your study regularly.
  • In version 1 of the FST, there was an issue where the use of unusual date formats (e.g. 2015-04-01) would cause an error when creating a report.  We believe that this bug has been fixed in version 2, but if you do experience difficulties then a workaround is to change the system data format to dd/mm/yyyy (using the Region and Language control panel in Windows) before using FST.

Download

The current version of the FST is version 2016.

Version 2016 is similar to version 2.3, with an expiry date of 31-Mar-2017.

Version 2.3 corrects an error where the action prioritisation results were not displaying correctly.

Version 2.2 corrects an error where the Facilitator Prompts buttons were not displaying correctly.

Version 2.1 corrects a bug where, if a stage in a PrISM had more outputs than inputs, then there could be an error when generating a report.

Version 2 corrected a number of bugs that arose in version 1.  The main difference that a user will see is in the editing of actions: each action is now edited in a separate dialogue box (select the action and use the pencil button to start the editing process). This approach corrects several bugs that were experienced when working with actions in version 1.

I agree to the terms of the End-User Licence Agreement (EULA).

Page last updated 1st April 2016