At uLearnIT, we love solving your problems. Here is the latest one solved for a client using our mentoring services.
In an existing FileMaker solution, we would like to know if certain scripts and layouts are being used. Over the years, the solution has been added to and updated in a haphazard manner and we would like to clean it up. How can we find out which scripts and layouts are in use?
It is unreliable and unwieldy for users to manually log their usage. Often, they do not know which scripts and which layouts they use. If they report the use of buttons, then they also have to report which screen and then the developer has to decipher the use.
The key to this solution is to automatically log the use of scripts and layouts. This can be done by triggering a script. The script will need to record the name of the layout or script used and then create a log record. The log record will be created in a special table for the purpose. The log record will have fields for:
- item (type) – layout or script
- name – of the layout or script
- account – name of the account currently in use
- creation – timestamp when created
The item will be set by the script; name will come from the script parameter; account and creation will be auto-entered.
The script to log layout use will be triggered OnLayoutEnter – after a layout is loaded. It will pass the layout name as a script parameter that will be entered into a log record. To set this trigger for any layout:
- Navigate to the layout and enter Layout mode.
- Select Layouts > Layout Setup… and then Script Triggers.
- Select the OnLayoutEnter event and select the required script.
- Set the Optional script parameter to Get ( LayoutName ).
The script used to Log Layout Use is as follows:
New Window [ Style: Card; Using layout: “uselog” (uselog); Height: 100; Width: 100; Top: 0; Left: -1000; Dim parent window: No ]
Set Field [ uselog::name; Get ( ScriptParameter ) ]
Set Field [ uselog::item; "layout" ]
Close Window [ Current Window ]
In the script above, the operation is performed in a card window off the user screen. This ensures that it does not interfere with the user’s normal actions or that of any running script. Since the parent screen does not dim, the user should not notice the script run.
The script creates a new card window and goes to a layout to create a new log record. It uses Set Field script steps to set the name field with the script parameter (in this case the layout name), and the item field with the text string layout.
Repeat the layout script trigger for every layout for which you want to log use. Over time as the solution is used, the log records build an account of layout use. This can then be analysed to see which layouts are most commonly used and which layouts are rarely or not used.
See Part 2 for scripts…
In Part 2 of this post, we will look at how to log the use of scripts in a solution. It is a simple extension of the above method for layouts.
Do you need uLearnIT to solve a problem?
We can do the same for you. Just let us know what you are struggling with and we will provide a cost effective solution. We have saved our customers hours of Googling answers and frustration trying things that never worked for them.
We can do the same for you.
Contact us now before you waste any more time!