 |
|
|
Due in the next release...
The custom bar code report now orders students by surname for easier collating.
You can now size barcodes so that long student or subject names can be accommodated.
Changes to the PC side
There had been an error that was generated when the Cases codes were created.
The two Cases reports were using the wrong reason types when distinguishing between Explained and Unexplained absences.
Reason maintenance now has an extra field called “CasesCode”. This allows you to use your own code for a reason, but still have it associated with a standard Cases code. In fact, a number of internal codes could be associated with a single Cases code.
Another new field, “Show in Web”, has been added to the “Reasons” screen that allows you to limit the reasons that show on the pop-up menu in First Class Web.
Changes to the PDA
The startup has been sped up.
The word “Additional” has been removed from relevant menus.
The previously selected route will be selected next time the route screen is used.
The selected period will be incremented each time the route screen is used and reset to the start each day.
The synchronization has been rewritten to do the following…
 | It compacts the PDA database before and after doing a sync to reduce the possibility of out of memory problems. |
| Speed has been improved for cases where a table does not need to be synchronized, eg no students have been changed. |
| Clash resolution has been implemented. If a roll record is marked on the PDA and the PC (or web) differently, then a clash record is created which can be resolved by going to the A+ > Clashes menu. |
| Synchronization now checks that the PDA is connected to an A+ database (i.e., it will fail if connected to a non-A+ database). |
| Synchronization also checks that it is connected to the same A+ database that the PDA was originally synchronized to. Previously it was possible to sync to one database and then attempt to sync to another, which caused errors. |
| It also checks that the roll data has not been deleted from within First Class. If it has the user will need to empty the database on the PDA and sync again. |
| The PDA now shows the number of records uploaded and downloaded and the number of clashes. |
When emptying the database you are now given a different warning if the PDA contains unsynchronized data (data will be lost) as opposed to when the PDA has been synchronized (no data will be lost).
A battery indicator now shows on the main screen and the Route screen when in all modes, including “Kiosk”.
When initially going into a class that has not been marked all of the students will show as “unmarked”. This gives a clear indication that the class has not been marked. When edit is selected all the students will be changed to present. This does not apply to routes because Edit would have been selected before going into the class.In the Roll Edit screen…
| The icons on the LHS of screen have been improved. |
| The columns now automatically resize to show reasons a little better and to give more room to show student name. |
| You are now only asked to save if data has changed (previously it always asked). |
How do I get a report on Emergency (Relief) Teacher usage?
At this stage there are no reports on Emergency or Relief teacher usage. However, if you follow these steps, you can use the current reports for this.
| 1. | From the MAINTENANCE menu, select TEACHER. |
| 2. | In EDIT mode, change all the EMERGENCY status fields from “Yes” to “No”. |
| 3. | Save the changes |
As First Class will now see those EMERGENCY teachers as if they are normal staff, their details will appear on all reports. Don’t forget to change the teachers back to their original status by following steps 1-3 above again, this time changing the EMERGENCY status back to “Yes”.
Due in the June release of SAS2000
Users of our administration package SAS2000 will be pleased to note that the first stage of our “Working Together” project is complete and will be unveiled in the June release of SAS2000.
This new feature will allow SAS users to view timetable data stored in First Class Web. You simply configure SAS to point to where the First Class data is stored, link the data and then anyone with appropriate permissions in SAS can view and print student or teacher timetables.
To book into a course, you can either click on one of the dates below, or visit the following page on our website:
http://www.humanedge.biz/firstclass/fc2000training.asp
First Class training, which is held at 427 City Road, South Melbourne will be held on the following dates...
Melbourne
| Tuesday, 12 July, 2005 | Advanced First Class Training Day 1 | 7 places left |
| Wednesday, 13 July, 2005 | Advanced First Class Training Day 2 | 7 places left |
| Thursday, 21 July, 2005 | First Class Extras | 9 places left |
| Tuesday, 26 July, 2005 | First Class Blocking | 10 places left |
| Friday, 5 August, 2005 | First Class Timetabling | 10 places left |
Wollongong
This training will be held at Illawarra Sports High School, Gura Street, Berkeley.
| Monday, 18 July, 2005 | Introduction to First Class | 5 places left |
More dates will be scheduled as needed.
For more information please contact:
Robert Bakker
First Class Support, Implementation and Training team
Phone: 1300 301 931
E-mail: firstclass@humanedge.biz
Human Edge adheres to a policy of not sending unsolicited (SPAM) e-mail. You are receiving this e-mail because you are listed as a contact for a product or service that our organisation provides or have requested that this service be activated for you. If you are receiving this message in error or wish to have our records changed please advise us via return e-mail or call us on +61 3 9690 5044