99 posts tagged with "legacy"

8.3.6.6 (2021.06.14)

June 14, 2021RunScore Team

Added the ability to create a PDF output from listing files using the Destination, Output To, OR Output Format Commands
Added the ability to send a PDF to a Race Roster race

May 3, 2021RunScore Team

Fixed an issue that caused JSON output to fail if participants did not complete the same amount of laps in a lap race.

April 19, 2021RunScore Team

March 17, 2021RunScore Team

This release changes the cumulative time in output of laps race to default format (no fractional seconds). A timer requested requested that the time format used for cumulative times be the same as for split times, i.e. H:MM:SS.
This release updates the functionality of the “le number of laps” and “ge number of laps” commands to fix a bug that caused the laps not to be filtered correctly or display appropriate Time and Laps data as expected.

January 13, 2021RunScore Team

This release implements a breaking change to how emails are sent to SendGrid due to a change in the SendGrid authentication protocol. RunScore timers who previously used a username and password to send emails through SendGrid will need to contact Support at support@runscore.com to be issued a new username and password with instructions for generating the required api_key that is now used to authenticate email requests to SendGrid through RunScore.

December 2, 2020RunScore Team

This release includes a fix that prevents a deadlock situation from happening when a timer deletes results on the RunSignUp dashboard, but the result set will still be defined in the timer’s race folder.

November 3, 2020RunScore Team

Adds new integration with the BlueBox external timing system
RunScore now supports the upload of custom fields to RunSignup. Prior to this change, when a timer did a native upload, only fields that RunSignUp knew about, e.g. “First Name” could be uploaded. By supporting custom fields, now any field can be handled.

October 27, 2020RunScore Team

Timers reported that they were experiencing greater RunScore instability and crashes especially during live races. The cause was traced back to a minor update to the screen refresh rate. This update strictly removes that earlier change.

October 21, 2020RunScore Team

Adds support for RunSignUp custom fields
Fixes minor issue that could cause RunScore to hang when initializing a timer
Fixes a minor issue that could cause incomplete downloading of participants from when parsing empty or bad input data
Removes extraneous RunScore Results login

October 5, 2020RunScore Team

Resolves an issue where a timer received a null error message when uploading results to the TFRRS system. This was caused by a TFRRS ID of one runner that had an extra character (hex ‘A0’) at the end of the id.
Minor update to the RunScore logos on server and client
Downloading registrations from RunSignUp with an exceptionally long questions caused the question not to be mapped correctly. This has been fixed.
Removes the extraneous RunScore Results login protocol (no longer needed)