Version 3.05.31.15
Dear maestro* clients,
We proudly present the main developments that were added to maestro* and maestro*MOBILE in this update.
Happy reading,
The Maestro Technical Writing team
To all maestro*MOBILE users: the barcode reader licence has expired. The maestro* update kit dated October 9, 2025, contains the update for this licence: by installing the maestro* update kit 3.05.31.15 | 6.0079, the licence will be automatically updated. Click HERE to download the update.
|
|||
|---|---|---|---|
|
|
maestro* > Accounting > Financial Management > Bank Reconciliation > Modify Cheque Status |
|
Modification made in order to keep the new status assigned to the cheque when saving. |
|
|
maestro* > Projects > Work Orders > Processing > Enter Work Orders |
|
maestro* > Projects > Project Costing > Dispatch > Project Dispatch |
|
Modification made to display the values of the contact’s variables when sending the schedule to the contact. |
|
|
maestro* > Time Management > Maintenance > Payroll > Government Tables |
|
Modification made to display, in the Safety Board section, the new maximums entered via the CNESST button without having to leave the option and return to it. |
|
|
maestro* > Purchasing > Purchasing > Procurement > Procurement Management (MRP 1) |
|
Modification made to eliminate the error 5 obtained. |
|
maestro* > Purchasing > Purchasing > Purchase Order > Stock Order From Catalogue |
|
Modification made to create an order with extension from an existing order and thus be able to immediately complete the fields of the Default Values section (Project, Activity, Group, Call No.). |
|
maestro* > Purchasing > Purchasing > Purchase Order > Purchase Order Management |
|
Modification made so that a regular user, who only has access to their own orders, cannot save a transaction entered by another user. |
|
|
maestro* > Tickets > Quarry Tickets > Ticket Entry - Invoicing |
|
Improvement made to ticket entry when the No internal use box is checked, in order to validate the combination of “Supplier, ticket number, and date” for a period of 6 months prior to the date of the new ticket entered and display a warning message if an identical combination is found within the previous 6 months. Previously, if a ticket number was entered for a date and supplier, the system would validate whether that ticket number had already been entered. However, validation was only performed for the same date. If a ticket was entered later with the same number and supplier, the system did not display a validation message. Some of our clients wanted validation to be performed not only for the same date, but rather over a longer period. |
|
Interfaces |
|
Modification made to the CreateOrder function so that the order number specified in the XML file is saved as is in the stock orders from catalogue and regular purchase orders created, without being modified. Modification made to read the value present in the XML file for tax codes and apply them to the orders created. If no value is present in the XML file, the values assigned to the transactions created will be the default values of the supplier or item code, as applicable. Otherwise, no value will be assigned. |
|
Mailing
|
Modification made to move the mass mailing settings from the Miscellaneous section to Communication. Modification made to configure mailing and mass mailings for the Office 365 - Modern Authentication mailing mode. For more information on the improvements made in maestro*, please refer to the following documentation:
|
|
Modification made to reset Outlook when an error occurs and thus enable pay stubs to be sent to employees. |