Feature Updates
Added Custom Section Header in Report Builder.
You will now be able to add a custom header to any Report Section in a Report. You can add variable fields like Race Name, Race Location, Race Date, Timer name/URL as well as any text you like.
We also support custom HTML in the field if you have some specific formatting or colors that you prefer.
In the future we will make this available to use in Report Templates if you want to have a standard custom header for all reports you create.
Added Built-in Predicted Time/Pace Reports
You can now mark a Scored Event as a Prediction Run. This will allow you to select a Custom Question/Field that is tracking the predicted time or pace for each participant. After doing this, you will have the ability to create a new report that includes a Prediction Time/Pace Section, which will rank participants based on how close they were to their predicted time or pace.
You also have the ability to say that all Predicted Time/Pace sections created for this Scored Event should be broken out by gender. This will make it so that when you add this kind of Report Section for this Scored Event, it will generate a section that is automatically filtered to only show the genders that you have selected. So if you select Male and Female, when you add a Predicted Time/Pace Report Section, two will drop into the Report (one filtered to only show males, and another filtered to only show females).
Added Time Formatting when using Filters.
Added time formatting to filtering when a time field is selected. Now you will be more easily able to create a filter that is something like “All participants who ran faster than 19:30.000”. Prior to this change you would have to figure out how many milliseconds are in the time you are filtering on.
Added more default dates.
Now whenever a date field shows up in the app it will default to the default race date.
Added Pace (Not Rounded) field to Report Builder.
The default Pace values are rounded up to the nearest second. We use the not rounded version when calculating predicted pace reports, so we have made this field generally available if you prefer to show Paces that are more precise.
Added RFID Direct Stream Support
We have added an RFID Direct Stream option, which will allow you to create a Stream that will connect directly to a single RFID reader by using it’s IP Address and Port.
Added a way to define Aggregate Team “Must Have Gender/Age” settings so that you can require some amount of members per Gender AND some number of those must be over some age.
This will allow you to do a scoring setup such as:
Score through 8 total members. 4 must be male, 1 of those 4 males must be over 40 years old, 4 must be female, and 1 of those 4 females must be over 40 years old.
Bug Fixes
Fixed a bug causing City/State to not automatically populate when entering in a zipcode.
Fixed a bug causing Relay Summary Reports for Races with multiple Segments to not sort non-finishers properly.
Fixed a bug when exporting Reports that include the Team & Members column to CSV, TXT, and PDF that would cause HTML formatting to show in the export.
Fixed user interface issue where the cloud backup/restore buttons could be hidden if the Race name was very long.
Better handling of network errors that occur when connectivity is insufficient.
Corrected issue with IPICO Gunshot Marker processing.
Fixed a bug causing a crash when saving “Must Have X” per Gender settings at the Team Type level under certain situations.
You must log in to post a comment.