Release notes

AGORA RELEASE NOTES

We want to thank all our aGora users that contribute the launch of new versions and program compilations with their inestimable suggestions.

Through the release notes you will view some novelties added to the updates and new versions of the program. These novelties expand aGora constantly, providing it of improved stability, new functionalities, solved errors, etc.

aGora Release Notes

Release notes 4.48.640

  • NEW FEATURE New statistic added: Active contracts (with groups dates) progression. It only considers the group ending dates in the contract.
  • NEW FEATURE New statistic added: Active contracts progression. It considers, not only the groups ending dates as in the one shown before, but also the predefined ending date and the group ending date. It is possible too to create a query for future dates.
  • NEW FEATURE New statistic added Active contracts progression by series (with groups dates). It only considers the group ending dates in the contract.
  • NEW FEATURE New statistic added Active contracts progression by series . It considers, not only the contract ending dates in groups as in the one shown before, but also the predefined ending date. It is possible to create the query for future dates.
  • NEW FEATURE New statistic added: Staff expenses .
  • NEW FEATURE New query added: Terminations and temporary absences by student type
  • NEW FEATURE New query added: Terminations and temporary absences by contract type
  • NEW FEATURE New query added: Incoming payments of bills with starting date between . It shows all the incoming payments of the bills with starting dates between two particular dates.
  • NEW FEATURE New query added: Incoming payments by contract type
  • NEW FEATURE New query added: Incoming payment by sales type
  • NEW FEATURE New query added: Customers by group type (current)
  • NEW FEATURE Added email field in the "Contract-student data" query
  • NEW FEATURE New printouts added in the section "Courses > Taught classes > Timetables control (daily, weekly or monthly)" which indicate the number of hours including start and finish hours that the teacher has taught to be signed by him/her. It only considers the confirmed taught classes.
  • NEW FEATURE New feature added in the process "batch sales". If in the process prefilter "a group customers" has been selected, in the new window, it will be linked to that group automatically.
  • NEW FEATURE Bill generation process changed in the case of having stablished a different concept for the bills in the contract and the generated bill only has one bill concept related, the group name won't be shown after that. It only will appear in case the bill has more than one bill concept linked.
  • NEW FEATURE Added the field "Particular/ company" in the customer list as a hidden one.
  • NEW FEATURE Changed the concept that applies the program by default in the returned incoming payments in the cancelled direct debit payments. Other than RETURN it will show CANCELLATION to distinguish it from the real returned ones.
  • NEW FEATURE Changed the way of sending results reports or any kind of PDF file from the aGora automations. That way, if there is a customized printout, the PDF will be sent attached with the name of the customized printout. For instance, if in the results of assessment report has been created a customized printout called 'Certificate', the PDF file will be generated when we send asessment results report from aGora using an existing automatic process, they will be generated with the name of 'Certificate' instead of 'Assessment report'.
  • FIXING SOURCE Solved bug produced when printing a calendar. When selecting in the printing settings the title "Window title", in the printing preview it appeared correctly, but not in the final printing.
  • FIXING SOURCE Solved bug: the queries "Bills by course" and "Incoming payments by course" produced records with duplicated or triplicated results, depending on the number of the lines of the bill description items.
  • FIXING SOURCE In an already generated contract with finished groups linked, if a discount or surcharge is added globally in the contract, it was distributed between all groups in the contract without distinction if the groups were already finished. Now this distinction is considered.
  • FIXING SOURCE Solved bug when adding a payment to staff from the staff list window. I did not actually linked to the selected staff member in that moment.
  • FIXING SOURCE Solved bug when updating the files of students, customers, enquiries or staff members if they were linked to a MailChimp contact and the email address had been deleted in their corresponding aGora file.
  • FIXING SOURCE Solved bug: the cancelled contracts did not appear in the Contracts by other description item queries in case of having the option See all Contracts. (Contracts by group, Contracts by surcharge, Contracts bu student type, Contracts by customer type, Contracts by course type, Contracts by payment option, Contracts by predefined discount, Contracts by course, Contracts by course category, Contracts by student).
  • FIXING SOURCE Solved bug in the "Totals of student of the group between dates" query in the case the student had data in the alergies field and these data exceeded 128 characters.
  • FIXING SOURCE Solved bug that doesn't allowed to extend the contracted hours to a student if the panel control option "Take into account maximum number of places in course group" was selected and the course group capacity was already complete.
  • FIXING SOURCE Solved bug when printing a teacher's planning. Printing it directly, in the printout appeared the teacher's name and date, but if it was clicked the preliminary view before and the printout was launched from there, some data was lost.
  • FIXING SOURCE The process of changing the amount in group contracts (from inside the group) didn't take into account contracts with no selection of the Some bills option in the contract to SQL Server database engine versions.
  • FIXING SOURCE Solved bug that in JET database based editions made that in the SQL queries created by the user, they couldn't sent emails and niether SMS with combined-fields templates if the SQL query had any parameter.