We have created a tool to set the Order of Go randomly (but with rules). Check it out!
Go to: Classes > the wheel > Set Order of Go:
- Select the Date/Ring/Group.
- Select the Point Horse for Riders with multiple entries. If there are no riders with multiple entries, then skip this step.
- Select the trips in between riders and click Order Trips.
- Click Save to apply the Order.
This tool sets a random order based on the following rules about riders:
- Riders with multiple entries are color coded, i.e., each rider is assigned a different color.
- If the available trips in-between are less than 8, then the tool will fit in as many as possible with even distribution.
- The Order will be set with riders having more multiple trips scheduled first. That way it will be easier to distribute in-between trips. The riders with the same number of trips will be picked randomly. Ideally, re-ordering trips should yield a different Order of Go each time.
Please note: You can drag/drop to change the order. For classes that have web signups, there is a confirmation dialogue set up before an admin user can randomize a pre-set Order. We are also working to make an addiitional feature that will allow the tool to randomize the Order of Go by trainer groups.
New reports:
Order of Go by class group report
This report gives our same functionality as before but now is based on Class Groups. Previous versions of this report did not a allow for orders for grouped classes.
Payment type and show report
We have developed a new report that provides a summary of payments based on payment distributions. This report summarizes payments by the Payment type and the show they were applied to. It’s ideal for keeping your accounting software in line with ShowGrounds with regard to open balances on each show.
We created a pull-down box so users can select the date with more ease when printing out the Rider, Owner, Trainer schedule.
USEF updates
On September 18, USEF updated its website, causing issues connecting with their web services for membership verifications. It has now been resolved.