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.43.590

  • IMPORTANT A new module is available for aGora, aGora.MailChimp, for those users that purchase it. This module allows you to link your MailChimp® account with your aGora database, allowing you to populate MailChimp's lists with the information you store in aGora of your students, customers, staff and enquiries. It will also allow you to download and process the results of your MailChimp's campaigns in aGora.
  • NEW FEATURE Added a new trigger that, when the "Include payment period in the description item of bills" in the Bills submenu in aGora's Control Panel is activated, the payment period will also be added to the bill's concept text, so it can be copied when creating an invoice with the bill.
  • NEW FEATURE Added a new field to "Enquiries" which allows to specify wether the enquirer wishes to receive mailing from our centre or not.
  • NEW FEATURE Added a new function to the aGora.Moodle module that allows, when a new user is created in Moodle® via aGora, the first time said user enters Moodle® he/she will have to change the default password for one of his/her choice instead.
  • NEW FEATURE Added a new option in aGora's Control panel, in the "Default values" submenu, which allows us to specify a default "means of incoming payment"
  • NEW FEATURE Added a new option for taught classes' weekly registers that allows the user to choose if they want to show the group option's name.
  • FIXING SOURCE Solved a bug on the "Teacher by qualification" statistic on SQL SERVER-based aGora editions
  • FIXING SOURCE Solved a bug on the "Totals by dates" statistic found in the Accounts tab on SQL SERVER-based aGora editions
  • FIXING SOURCE Solved a bug on the "Cancel (incoming) payments" batch process, which caused it to fail for incoming payments related to enrollment fees
  • FIXING SOURCE Solved a bug that impeded the cancellation of a direct debit remit if it had two different billing dates and the earlier billing date was selected as the cancellation date.
  • FIXING SOURCE Solved a bug when cancelling an incoming payment and choosing to add the cancelling expenses to the related bill: If the bill had only one bill concept associated, the "Before tax" quantity was not updated, even thought the "Total" quantity was.
  • FIXING SOURCE Solved a bug on the "Automatic generation of invoices" process which, when choosing a specific emission date for the invoices, would cause the date to be ignored when the user chose not to group all of each customers' bills in a single invoice.
  • FIXING SOURCE Solved a bug that caused aGora to detect overlaps in the timetables of group options when there were none, for cases when the teacher, day and classroom are the same, even if the hours aren't. Only on SQL Server-based aGora editions.
  • FIXING SOURCE Solved a bug which caused the "Hide inactive parameters" in aGora's Control Panel not to show on editions of aGora lower than Gold edition.
  • FIXING SOURCE Solved a bug which caused the retention quantity associated to a cancelled invoce not to reflect correctly in its related rectifying invoice.
  • FIXING SOURCE Solved a bug which would not allow the user to deselect a specific parameter in many edit mode windows if the user lacked permission to create parameters.
  • FIXING SOURCE Solved a bug that allowed us to reactived a course group without first having reactivated its associated course
  • FIXING SOURCE Solved a bug exporting accounting information to ECO5 Pro due to bad naming of the resulting file
  • FIXING SOURCE Solved an error when deleting a sale that had one or more benficiaries: when deleting the sale, the beneficiary-sale relation was not being deleted, which caused the next created sale to automatically associate itself to said beneficiaries.