Improvements | Addresses - It is now possible to select the number of address lines you want to display.
- Addition of the columns "Address for the documents" and "Address for the receipts" in the address grid of the client file and in the grid of the "Client/Address" tab of the client management.
- The "Address types" have been renamed to "Address categories".
- Under the "Main info" tab of the client file, there is now a button allowing you to access the default address. Before, you had to go through the "Addresses" tab. Addition of the checkbox, "Add automatically to the new addresses" in the configuration of an address category. If this checkbox is checked for a category, it is automatically checked when adding a new address.
- It is now possible to adjust the width of the address fields (city, province, country, postal code and cedex) in the client file, the address modification file and the client selection window when adding a transaction.
Characteristics - It is now possible to modify a "List of options" characteristic type to "Predefined option list" and vice-versa, even if it is used in a Web form.
- In a characteristic, a new button allows you to add a value to the list of options at the current position.
- The function allowing you to delete all the values of a characteristic has been moved from the "Advanced functions" menu of the modification file of the characteristic, to the characteristic management.
- In a characteristic, if you choose type "List of options" or "Predefined list of options", the active tab is automatically changed to the one of the list of values.
Client importations - When a client is modified in the Importation module, the same client is modified in all the lines where he or she appears. To know if the client is the same, the client No. and the reference (unique in the preferences) are checked or if the clients are duplicates with one another.
- When importing relations, the duplicate detection is now done on any type of relation. Before, in order for the duplicate to be detected, the relation type to import had to be the same as the one of the relation in ProDon.
Clients - A confirmation window is now displayed when the option "Display 2 tab groups" is deactivated in the client file (option available from the "Display" menu).
- In a client file, the fields of the "Add. info." tab are now arranged differently.
- In the client management, in the exportation for Sollitel, it is now permitted to export a characteristic or a customized field as prioritization code.
- In a client file, the "Categories/Lists" tab has been split in two different tabs.
- In a client file, the grids summaries and beneficiary summaries have been merged.
- Under the "Add. info." of the client of a company, the social security number and the job title disappeared and left an empty space. From now on, the other fields have been changed to fill the space.
- Under the "Relations" tab of the client file, columns have been added to display the name of the contact of the client 1 of the relation.
- In a client file, under the "Add. info" tab, options "Deceased" and "Excluded form mass mailing" have been inverted to respect the logical order. Because by checking the "Deceased" option, the "Exclude from mass mailing" option is checked automatically, it is only natural to find them in this order visually.
- In the assignment of new client values, it is now possible to perform an assignment on the following fileds "This client no longer wants to be called", "This client does not want an amount suggested" and "This client is a beneficiary".
Commitments - In the frequency of a commitment, the label "Every ... week(s)" has been changed to "... week(s)" and the label "Every ... month(s)" has been modified to "... month(s)".
Cross-analyses - Since it was not used anywhere else in ProDon, the "Code" field has been removed from the configuration window of the cross-analyses.
Customized lists - It is now possible to divide the transaction criteria screen in static or dynamic lists.
Duplicate merge - When merging duplicates, the active relations are now before the inactive relations.
- When merging duplicates, a confirmation message is now displayed by clicking on a column header.
E-mail Blast - It is now possible to send an E-mail Blast right after sending the test email. Before, you had to close the mailing and to open it again.
Filters and views - In the filter tool, the ascending order is now the default sort order.
General - The "Deceased" column has been renamed to "Deceased/Closed?", "Birth date" has been renamed to "Birth date/Founded on" and "Date of death" has been renamed to "Date of death/Closed on".
Gift brackets - It is no longer possible to create a gift bracket with the same minimums and maximums as an existing gift bracket.
Groups of characteristics - It is now possible to choose the display order of the groups of characteristics. Before, they were inevitably in alphabetical order.
Importations - It is no longer possible to perform the importation of the data, if the filter of the data to import contains unanalyzed lines.
- It is possible to configure an importation so it can automatically be run from a planned task.
- It is now possible to enter instant payment information from an importation line.
- In the loaded importation data window, a resizing bar has been added between the labels and the entry boxes.
Instant Payments - In the recipient information validation window, in a bank transfer of a corporate file, the "First name" and "Last name" fields are now empty and the name of the company is placed in the "Company" field, whicht has been added.
Mailings - In a client file, in the mailing grid,the column "Org. code" has been added.
Mass mailing - In the modification window of a master document, all the merge fields are now categorized in differnet sections. Some sections have been renamed and certain flleds have been moved to new sections.
- In a company file, it is now possible to document the founding ("Founded on" field) and the closing dates (Closed on" field) of the company, which are equivalent to the dates of birth and death of an individual file. In the management grid, the columns are named "Birth date/Founded on" and "Date of death/Closed on".
- An option has been added in the E-mail Blast, to indicate that you do not wish to take the default address of a client, in the event the desired address type is not found.
- In the relation type E-mail Blast, it is now possible to apply a grouping per relation.
Master documents - In a master document, when you clicked on the duplicate button, a message stated that the Word files would be overwritten even if no file existed for that document.
Means of communication - A resizing bar has been added between the phone numbers and the extension numbers in a client file.
- It is now possible to enter an extension number for toll free phone numbers.
- It is no longer possible to modify the category of a means of communication once this type is used in one or more client file(s) (except for categories "Telephone" and "Telephone and extension", that can be interchanged).
- When the means of communication are displayed in "Quick edition" mode and that the section is shrunk at its minimum in a client file, the means of communication are now displayed in a single column.
Organizations - It is now possible to translate the address of the organization in order to have a French address on JeDonneEnLigne and an English address on IMakeAnOnlineDonation. The right address will also be displayed on the receipt, based on the language in which has been generated.
- It is possible to display the URL address of the French website of the organization in the French organization directory of IMakeAnOnlineDonation and the URL address of the English website in the English directory.
Payment methods - It is no longer possible to configure a Pivotal type payment method.
Preferences - In the system preferences, under the "Performances" tab, when the maximum number of records is modified, a message informs the user that he or she must shut down the software so the modifications can be made.
- In the system preferences, under the "Performances" tab, it is now possible to indicate a maximum number of records displayed in the management grid, for all the managements that are not part of the list.
- An option has been added in the system preferences, under the "Others" tab, so the same alert is not displayed more than once in the given time range.
Receipts - In the configuration of the organization, under the "Receipt (pos.)", it is now possible to preview the 4 types of receipts (receipt without thank-you, receipt with thank-you, duplicata without thank-you and duplicata with thank-you). However, it is not possible to preview Word receipts.
- When emailing a receipt duplicata, the email address of the donor was not selected automatically.
- In the Web forms, the "Annual receipt" checkbox was checked automatically by checking the "Use the Web receipts when making an instant payment" checkbox, it is no longer checked.
Also, for transactions with a Web receipt, the "Annual receipt" checkbox is no longer checked.
Relations - In the modfication file of a relation for a company, the "Birth" and "Deceased on" fields have been replaced with "Founded on" and "Closed on".
- When a relation ends, a question now asks if you wish to have the same end date for the addresses and means of communication coming from this relation.
- In a client file, after adding or modifying a relation, the cursor is now in the grid in order to make sure to be positioned on this relation.
- In a relation involving companies, a button has been added to delete the contacts.
- Under the "Relations" tab of the client management, we can now see all the clients without relation, in addition to seeing all the relations.
Reports - In the "List of prospections" report, the width of certain columns has been increased because it was not sufficient.
Search bar - In the search bar, search functions that were only available with a filter have been added. To know the new possibilities, see the legend. Search function">" now performs the search "is greater than" instead of "greater or equal to". From now on, to perform a "greater or equal to" search, you must use search function ">=". Search function "<" now performs a "smaller than" search instead of "smaller or equal to". From now on, to perform a "smaller or equal to" search, you must now use function "<=". For the columns that display images (e.g. status or priority of the tasks), it is possible to select the value(s) to filter in an option list.
Tasks - Elements "Task types" and " Tasks and history" are now in the "Tasks" menu, instead of the "Analysis" menu.
- When duplicating tasks, the task documents are now duplicated in the new tasks.
- Under the "Availability" tab, the tasks and the resizing bars have been removed. The given space is now automatically divided between the three grids.
Text templates - It is now possible to identify the language in which each text template is written.
When using text templates, if ProDon is in French, only the French text templates are visible by default, but it will still be possible to use English text templates. For each text template, it is now possible to identify the users who can modify or see them.
Titles - In the configuration window of the titles, the option "Favourites" has been added. The titles identified as the favourites appear first in the option lists.
Transaction importations - When importing a transaction with an activity by quantity, if no quantity is indicated and the imported amount is not a multiple of the unit price of the activity, an error message signals it.
- When importing a transaction with an activity by quantity, if the entered quantity and amount do not correspond with the unit price of the activity, an error message signals it.
Transactions - It is now possible to perform a mass assignment of donation occasions and activities on pending or accepted transactions with an instant payment method, if the amount of the transaction is not modified. (72 671)
- If instant transactions of the "To send" tab do not have any payment token, they are now moved to the"Denied" tab when they are sent. Before, when they were sent, they stayed under the "To send" tab.
- When assigning new transaction values, the payment grouping is now separated from the payment.
- In the instant transactions, the field "Instant pay. tr. No." has been renamed to "Merchant tr. No.".
- When assigning new transaction values, the accounting projects, in-kind and transaction forms sections are no longer displayed if they had not previously been activated in the systeme preferences.
Web Forms - The text for the consent for bank transfers has been removed from the summary of the Web form.
This text can be brought back by creating a note attached to the bank transfer payment method that will only be displayed in the summary.
Here is the text that has been removed:
Consent to disclosure of information I hereby consent to the disclosure of the information contained in my pre-authorized debit enrolment agreement to the financial institution, provided such information is directly related to and required for the smooth application of the rules governing preauthorized debits. I recognize that I have read and understand the Change or cancellation conditions and the Reimbursement conditions on this form.
Change or cancellation I shall inform the Payee, in a timely manner, of any changes to this Agreement. I retain the right to revoke my authorization at any time, with a pre-notification of 30 calendar days. To obtain a sample of the cancellation form or for more information on my right to cancel a PAD Agreement, I may contact my financial institution or visit the Canadian Payments Association Web site at http://www.cdnpay.ca. I agree to release the financial institution of any liability if the revocation is not respected, except in the case of gross negligence on its part. I agree that the financial institution at which I maintain the account is not required to verify that the payment is debited in accordance with this authorization. I also certify that every person whose signature is required for the operation of the aforementioned account has agreed this authorization. I acknowledge that the delivery of this authorization to the Payee constitutes delivery by me to the aforementioned financial institution.
Reimbursement I have certain rights of recourse if a debit does not comply with the terms of this Agreement. For example, I have the right to receive reimbursement for any PAD that is not authorized or that is not compatible with the terms of this PAD Agreement. For more information on my rights of recourse, I may contact my financial institution or visit http://www.cdnpay.ca. The financial institution shall reimburse me, on behalf of the organization, for any amounts withdrawn in error, within 90 calendar days of the withdrawal for a Personal PAD and within 10 business days for a Business PAD, provided that the reimbursement is claimed for a valid reason. I understand that a claim to this effect must be made to my financial institution following the procedure it will provide for that purpose. Finally, I acknowledge that a claim for reimbursement filed after the aforementioned time limits must be settled between me and Payee, without any liability or commitment on the part of my financial institution. You accept that the levy will be taken within 3-30 days of receipt of your confirmation email. - In the Web forms, the dimension of the images must now be specified in pixels rather than in points.
- In the configuration window of the website, the option "Add a comma between the street number and the street" has been moved from the "Import" tab to the "Options" tab of the "Configuration" tab.
|
Corrections | Accounting projects - The accounting project management was not hidden, even if it had been deactivated in the system preferences.
Activities - In an activity, it was not possible to specify the start date without the end date. There was an error message stating "The start date is earlier than the end date".
- It was possible to check the "Always issue an invoice" option in an activity even if a commitment used that activity.
Address importations - When importing addresses, the existing addresses were not updated correctly. The fields containing lines 1 to 5 of the address, as well as the fields containing the different parts of the address (street No, road type, street name, etc.) were not modified.
- When importing addresses, if a client had an "Address for receipts" or an "Address for documents" that was checked in his or her file and when a new address with the same identification was imported, the option was not deactivated for the old address.
- In the importation of addresses, if the file contained the same address twice for the same client and the column for the address category contained the same category code, an error occurred.
- In an "Address" type importation, the postal code is now formatted automatically when it is modified.
- In the Importation module, a message stated it was not possible to import two default addresses for the same client, even if only one of the two addresses had the default value.
Addresses - When an address is changed from a client file, a question asks if you want to archive the old address. If you answered yes to the question, an error message appeared.
- In a address file, when the address was modified and you clicked on the "Edit address" button right after, without saving or leaving the edition box; the window opened with the old address.
Analysis and history - In the Analysis and history of the transactions, the summary per Date/Week did not always group the transactions correctly if you selected a grouping per batch date.
Characteristics - It is no longer possible to assign a start date later than the end date when assigning charcateristics in mass.
- In a "List of options" or "Predefined list of options" type characteristic, it was possible to add the same value twice.
- In a characteristic, if the quick entry mode was activated, the date/time display format was not applied.
- A conversion error was displayed by modifying the type of characteristic of any type to the "Date and time" type, when that characteristic contained a default value.
- If a record was changed in the grid of characteristics, an empty column was added.
Client categories - We now make sure there is no other existing category with the same code, when adding a client category.
- When adding client categories, and the code or the description was missing, there was a message stating "The key fields are blank". Now, the message indicates the code or the description is missing.
Client importations - During the importation, an error message was displayed if the importation file contained the columns "CliComments" and "CliComments ".
- In relation importations, an error message was displayed when columns "RelCompany" or "RelService" were present.
- In the Importation module, if a client was a duplicate with the client of another line and if fields CliFirstName, CliLastName, CliCompany and CliService were used, the first name/last name/company/service were not visible in the duplicate section on the right.
- In the importation of clients, if columns "CliNoClient", "RelNoClient" and "RelTypeRelation" were documented and the relation already existed in the database, the value of the "RelOperation" was not modified.
- When the name of a client was modified by the Importation module, the modification was not made in his or her client file.
- In the edit/view loaded data window of the Importation module, the duplicate section did not display any information if the duplicate was an internal contact.
Clients - In the default values of a client file, tabs "Summaries", "Instant payments" and "Recognition program" were visible, even if it was not possible to document default values for those tabs. Now, only the tabs for which it is possible to document default values are visible.
- Improvement of the data display performance of the "Clients/Tasks" tab of the client management.
- It was not possible to use the Internet utilities when a filter on a customized list of duplicates was active.
- In the client management, as well as in a client file, it was possible to select an archived email by clicking on the button to send emails to clients.
- In the assignment of new client values, when the "Deceased" option is checked, the client becomes inactive and is excluded from the E-mail Blast.
- Under the "Relations" tab of a client file, when you click on the button to open the file of the client in the relation, rather than opening a second file, the record in the opened file is changed.
- Under the "Relations" tab of the client management, if you double-click on a client who has no relation, there is now a message stating there is no relation to open.
- The scrollbar of the "Main info." tab was not displayed correctly in the client file.
- When a client and his or her clients were duplicated, the greeting of the relations was not duplicated. When you tried to modify that relation, there was an error.
- If a relation was added, modified or removed from a client file, the floppy to save the modifications was lit when it should not have been.
- Under the "Transactions" tab of the client file, if third-party transactions were displayed and sorted by donation dates, the sorting was not respected because it was first performed on the donor's number.
- In the assignment of new values for clients, when you tried to remove a title (check Edit and not write anything for the new title), by clicking on "Apply the changes", an error occurred. The same error also occurred in the assignment of new values for the relations.
- When a last name or a first name was modified by using the "Search and replace" special function, the greetings were not updated.
- When a client file was suffuciently reduced, the message "Excluded from E-mail Blast" was displayed in the toolbar, over the buttons.
- Either from a relation file or from the "Relations" tab, it is no longer possible for a user to view a client file to which he or she does not have access (visibility level).
- When the "Deceased" option was checked in the file of an individual, the greetings of the companies in relation with him or her were not modified. It was therefore possible to address the deceased person.
- When a client was modified, merged or if you assigned new values that affected him or her, the greetings were updated in the relations, but the greetings of the clients in the relation were not modified.
- In the configuration window of the default values of a client file, there was an error message when opening the "Employee" tab.
- An "In Memoriam gift" quick filter has been added under the "Mailings" tab of the client file.
- It is no longer possible to delete a client if he or she has advanced analysis characteristics.
Commitments - When assigning new commitment values, it is now possible to mass assign only the nature and the form of the donation.
- In a commitment, it is no longer possible to select an activity for which the "Always issue an invoice" option is checked.
Cross-analyses - In the analysis section at the bottom of a management, if the "Refresh automatically" option was selected, the summary displayed all the existing lines in the management even if the "Forced search" mode had been activated.
- Before, it was possible to add the same field twice on the Y axis; it is no longer possible.
Custom reports - The custom reports were no longer generated in the transaction batch transfer.
Customized lists - The "Go to" function of the customized lists was not configured correctly. The names of the columns were wrong.
- If a predefined option of a customized field was moved with the "Other moves" button right after adding it, the option disappeared, then if the option was moved right after modifying it, the modification was not saved.
Donation occasions - Under the "Client 1" and "Client 2" tabs of a donation occasion configuration, the "New" button to add a category or a relation type did not work.
- By duplicating a donation occasion and its activities, the transaction and commitment characteristics checked in the activities were not copied in the new activities.
- In the reorganization of donation occasions and activities, the window did not close when the reorganization was completed.
- It is no longer possible to delete a donation occasion if it is used in an advanced analysis characteristic.
Duplicate merge - In a duplicate merge, the value of the "Gender" field was never displayed.
- When merging duplicates, it was possible to select a title in the result column and to select a language or a gender that does not correspond to the title.
- In the duplicate merge, when you archive or delete an address or a means of communication, options "By default" and "Preferred" are unchecked.
- When merging clients, the order of the merged relations was wrong.
- When merging duplicates, an error message was displayed if the clients to merge were part of the same distribution list.
E-mail Blast - It is no longer possible to register an internal contact to a client type distribution list.
- In a distribution list for the E-mail Blast, if a client had the same email address registered twice to the same list, sometimes it occurred that he or she was registered in double.
- When sending a relation type E-mail Blast, the "Subscriptions of the list" tab displayed the relations between 2 individuals or 2 companies. Now, only the relations between a company and an individual are displayed. Moreover, when there are duplicates for an email address; from now on, the relations to clients are prioritized.
- In the E-mail Blast, if a contact had the same email address twice, we tried to send the email twice to this address. From now on, we eliminate email duplicates within the same contact.
- In a distribution list for the E-mail Blast, the number of people registered to the list was not always the same in the distribution list management as in the modification file of the list.
- If the distribution list was changed in the E-mail Blast mailings, the list of registered people was not refreshed.
- In the update of subscriptions to distribution lists, if the reason for unsubscription is changed, it is only changed for the lists from which the client unsubscribed.
Before, it was changed for all the visible lists.
Expenditures - The "Go to" function was not configured correctly in the expenditure management.
- If a GL account was created from an expenditure activity, the GL code was not displayed when the addition was confirmed.
Export and merge - From any management, if you clicked on the "Export and merge" button, chose a merge with Word and immediately proceeded with an export to Excel without closing the window, an error message appeared.
Filters and views - The keyboard shortcut to paste text (Ctrl V) was no longer functional in the filter when operation "Is in the list" was used for a "Numeric without decimal" or "Date and time" field type.
- In the filters, for the numeric type fields, it is no longer possible to enter something other than numbers.
- In the list of views or in the list of filters of a grid, there was display problem when using the scrollbar.
- In a filter, if you went to the "Fields" tab, got positioned on a long text field and returned to the "Special" tab, the "Add the condition" button remained grey.
General - Buttons "Date", "Date and time", "Text template", "Print" and "Edit the text in an independent window" are now available in all the windows that contain a note or a comment.
- In a predefined list of options type characteristic, when the value of one of the options was modified and the customized order was selected, the order was not respected.
- When the width of the main page was reduced, it was possible to hide the buttons of the toolbar. From now on, the scroll buttons allow you to display the hidden buttons.
Groups of characteristics - Under the "Groups of characteristics" tab of the characteristic management, the button allowing you to display the detailed grid did not work.
Importations - In the Importation module, the client categories sorted as importation constants were not imported.
- When creating a transaction per importation, if the date of the transaction was 1900-01-01, it was replaced by the current date.
- In the loaded data management, the widths of the columns and their positions were the same from one importation to the other. It is now possible to configure and save a different view per importation.
- In the loaded data management, the assignment of new values generated an error if the loaded data window had not been previously opened. Also, even when the window had been opened before performing the assignment, the data was not refreshed.
- In an importation, if there was a procedure that was performed prior to loading the data, if the procedure had already been performed and the file has not been changed since the last execution, it became impossible to load the data.
- In the analysis of relations of the Importation module, the nonexistent "Client No." were deleted even if the option "Accept the nonexistent "Client No." (new clients)" was checked. Also, when modifying a line to import, there was no verification made on the existentce of the "Client No." and the client was always considered a D duplicate.
- When importing relations, it is possible to create a static list with the imported relations. However, the list did not contain the right relations.
- In a relation type importation, if the client of the relation (Rel prefix) was a duplicate (P or D) with a client (Cli prefix), it was possible to have an error like "Invalid column name" by selecting that line in the grid.
- In the importation of addresses and means of communication, the client number was not recovered from the address or the means of communication that was imported and it was therefore not possible to modify any other information of the client at the same time.
- In the loaded data modification window of an importation, it was possible to reduce the window enough so the "Confirm" and "Cancel" buttons would go over the entry boxes.
- There was an error message in the final importation of characteristics and groups of characteristics.
- An error message appeared when importing a characteristic and its group of characteristics if the name of the characteristic contained an apostrophe.
- When importing relations, there was no error if the type of relation was specified, but the first name, the last name, the company and the service were empty for a new client or a new internal contact.
In Memoriam gifts - In the In Memoriam gift management, the "Status" field was truncated to 9 characters.
Instant Payments - When sending instant transactions from the "To send" tab to the "Awaiting response" tab, if the transferred batch contained commitment transactions from IMakeanOnlineDonation and from ProDon and if the shop ID used for credit cards on IMakeanOnlineDonation was different from the one used for credit cards in ProDon, some transactions were in error, because the shop ID did not correspond to the right account number of the payment.
- It is no longer possible to add a transaction or a commitment with a Perceptech credit card type payment method.
- An error occurred when adding an instant transaction, after generating the transactions for automatic commitments with an instant payment method.
Invoices - If you opened a billed transaction, then opened the invoice of that transaction and attempted to modify the quantity or the amount, a message indicated the transaction was locked.
Items - Correction of the cost price calculation of the items. Before, the calculation was made from the lifetime expenditures. From now on, for each item sold, the calculation is made on the cost price of the expenditures made before the sale date.
Mailings - If a user did not have the rights (security) to perform mass mailing assignment, in the advanced functions of the client management, when clicking on "Add mailings", nothing happened. A message now indicates the access is denied.
Management grids - The "Shift TAB" shortcut is now used to scroll down the search bar to the left.
Mass mailing - Fields "Nbr_IMG_to_process", "IMG_Amt_to_process", "Total_Nbr_IMG_to_process" and " Total_Amt_IMG" were always empty when merging.
- When an In Memoriam gift type mass mailing was performed on a deceased person with no family member to notify and the Word file of the master document was nonexistent, an error occurred when you clicked on the "Generate" button.
- An error message was displayed if relation 1 was active in the master document when generating a relation type mass mailing.
- The [Prefix]_Subscription_Date merge field has been renamed to [Prefix]_Entry_Date.
- The Comm_Des_Gift merge field has been added to the commitment type mass mailing.
- Correction of the display format of the dates and amounts in the commitment type mass mailing.
- In an In Memorian gift type mass mailing, it is now possible to insert the "Img_Donor" field and to configure the display of that field. If in the display template of the "Img_Donor" field, fields starting with "Cli_Contact" fields were used, the merge was not made.
Master documents - An error message was displayed when using a text type calculated field, if one of the conditions did not give any result.
- An error message occurred when a master document was duplicated twice.
Means of communication - In the grid mode of a client file, it was possible to reduce the means of communication section enough so the buttons overlaped each other.
- The "Go to" function was not configured correctly in the means of communication management.
Organizations - It is now possible to document a Cedex in the organization configurations. (Europe)
Under the "Addresses" tab of the system preferences, it is possible to identify the disposition of the address in the client file. This disposition is now also used in the organization configurations. - The Cedex specified in the organization configurations is now entered in the address of the organization on the Web receipts. (Europe)
Payment methods - Correction of an error when adding a new payment method.
Periods - In the period management, the name of the column "Description abbr." has been changed to "Code". In the period modification window, "Label" has been renamed for "Description" and "Abbreviated" has been changed to "Code".
Receipts - Once the receipt issuance is complete, the lock is sometimes removed. This kept other users from accessing the receipt management.
- An error message was displayed when generating several receipt duplicates.
- The "Advanced functions" menu and the "Cancel the issuance of the receipts" function are now available in the "Processing of receipts to be issued".
- In the "List of Issued Receipts" report (available from the Analysis and history and from the Management of issued receipts), the "Receipt date" column displayed the "Receipt issuance date" field.
- Addition of the "Issued receipts cumulative" field, which displays the total of the receipts issued by the client from many grids.
Addition of the "Eli. receipts cumulative" field, which displays the total of eligible receipts of the client in many grids. Addition of the possibility to make a summary per cumulative on the issued receipts. Addition of the possibility to make a summary per cumulative on the eligible receipts. Addition of the possibility to make a static or dynamic list on the cumulative of the eligible receipts.
Relations - In a relation window, the asterisks are now displayed on the tab of the characteristics if it is not empty.
- In a relation, when a contact was assigned to a company with an internal contact, the contact was not saved.
- It is now possible to convert an internal contact into a client, even if this contact is used as company contact in another relation.
- In a relation, when there is a company on one side and an individual on the other, the means of communication of both clients are now aligned.
- In a relation modification window, certain fields have been troncated in the event the window is reduced to the minimum.
- From now on, when one of the clients of a relation is modified, the same validations as in a client deletion are applied (e.g. It is not possible to delete a relation when it is used in some mailings).
- It is no longer possible to have an end date earlier than a start date in a relation.
- When a client file was opened from a relation and that its name was modified and confirmed; the content of the "Greeting" tab of the relation was not refreshed, so the old name of the client was displayed.
- When a "Spouse" type relation was added, the greeting was calculated correctly in one direction, but not in the other.
Reports - In the "List of transactions" report of the analysis and history, the space available to display the receipt number has been enlarged, since a 6-digit receipt number with a Web prefix was not displayed correctly.
- When generating the "Balance sheet of a donation occasion" report, the options selected the last time the report was generated should always have been brought back. However, the value of the "View the projections of the commitments" checkbox was not brought back.
- In the "Summary per GL account (With taxes)" report, if the separation per GL account was selected, the report was also separated by payment method.
- Correction of an error that occurred when changing the destination of the report generation if there was no report in the list.
- In a custom report, when the report was saved, the characters that are not permitted by Windows were not removed from the file.
- In the "Detailed list of clients" report, the alignment of the different tables in landscape mode has been corrected.
Search bar - The "Ctrl E" keyboard shortcut allows you to empty the search bar again.
- In the search bar, on the date/time fields, if you selected the "Others" option and that you selected a function not requiring a quantity (for example J-X), the box allowing you to specify the quantity was activated anyway.
- When a client is added from the client management, from the "Select a client for a transaction" window, if the search bar contains a filter on the columns "Last name/Company" and "First name/Service", these values are recovered as default values for the new client. However, the following operators, empty (#), not empty (!#), equal (=), different (!=), greater or equal to (>=), smaller or equal to (<=), greater than (>), smaller than (<), as well as asterisks (*) were not removed from the search values.
- In the legend of the search bar, there is no longer an automatic carriage return. Also, the "For logical values (checkboxes)" section has been added.
Shortcuts - During a new software installation, it was not possible to create the shortcut to the support centre if the postal code of the organization had not been documented in the organization parameters. From now on, it is possible to enter the postal code directly in the shortcut creation utility.
Task importation - When importing tasks, if you did not import the "ModifiableTas" field, an error occurred.
- When importing tasks, if the task number was provided, the operation remained at A for Add, rather than at E for Edit; which resulted in adding the task twice with the same number.
- The importation of tasks linked to a client did not work when the reference number of the client was used to make the link.
Task types - The "Go to" function of the task types displayed an error message.
Tasks - The "Open the description in a window" button has been removed from the tasks, because it was no longer useful and could cause problems.
- When a task was duplicated and the type of deadline of the current task was different from the one of the duplicated task, the deadline of the task was not duplicated correctly.
- When duplicating a task, the values "In realisation by", "In realisation on", "Completed by" and "Completed on" are no longer duplicated.
- When a task assigned to a user was saved and the group of this user was in the "Visible by" and the "Modifiable by", a message stated that the creator should be able to view and modify the task.
- It sometimes occurred that the assignment of new values locked some tasks and did not remove the lock after the modification; which made them inaccessible to other users.
- When opening a task undergoing modifications, the focus is now placed on the description field.
- Under the "Accessibility" tab of a task, when selecting a user, the sort order was wrong. The order in now the following: "Author and producer", "All users", "Supervisor", the groups of users and the other users.
- The "Go to" function of the task management was not configured correctly.
Transaction analysis and history - In the Transaction analysis and history, the assignment of new values returned an error message when you tried to assign a GL account.
Transaction importations - It is no longer possible to import instant transactions per quantity with a total amount of zero.
- In a transaction importation, if the "Amount" column was not in the importation, the following error message was displayed "Quantity required". The error message is now "Quantity or amount required".
- It is no longer possible to import a transaction with an empty value in the "Amount" field.
- In the transaction importation module, an error occurred in the analysis when the fields of the linked clients were used.
- In the transaction importation module, linked clients 1 and 2 were not imported.
- When donation occasions were created via the Importation module, if there were fields for the linked clients, they were not activated in the created donation occasions.
Transaction/Commitment importations - When importing transactions with an IBAN payment method, the RUM was not imported. (Europe)
Transactions - Either from a transaction or from the client search of the transaction addition, it is no longer possible to add or modify a client if the user does not have the rights to add of modify clients.
- In the batch processing of receipts, an error occurred when opening after the user had changed.
- Either from a transaction or from the client search of the transaction addition, it is no longer possible to add or modify a client if the user does not have the rights to add or modify clients.
- In a transaction, it is no longer possible to check the "Issue an invoice" option if the transaction is from a commitment.
- From a transaction update file, when a receipt duplicata was generated, it was not possible to perform the generation, because the generation had been locked by us.
- When saving a transaction, the characteristics that did not contain any value were deleted.
- When you saved an In Memoriam gift type transaction for which the person to notify was documented, the name of that person was doubled.
- In the system preferences, if the option to automatically recover the donation occasion and the activity of the last solicitation was checked and the donation occasion of this solicitation was inactive; the donation occasion was not brought back, but its documents were all checked anyhow.
- When adding a transaction, an error message was displayed if the client was modified and the required fields were not filled.
- By clicking on the "OK duplicate" button of the transaction modification window, the information of the participants is now duplicated. (73 925)
- Correction of an error that occurred when opening the new transaction value assignment window.
Users - It was not possible to change the order of access to organizations for users if the user was linked to a group.
- When the toolbar was copied from another user, it was not displayed again when confirming.
- The following securities "Untransferred gifts (Transaction management)", "Importation of online donations" and "Import the donation history of another client" have been renamed to "Untransferred transactions (Transaction management)", "Importation of Web forms" and "Import the transactions of another client".
Web Forms - If modifications were made to the Web receipts, but were not sent in production, the message "Some information was not sent to generate Web receipts. Do you want to send it?" was displayed the next time the software was opened. This message now only appears for the users who are allowed to modify Web forms.
- In the importation window of Web forms, the number of Web forms awaiting loading was not calculated per organization.
|