Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section contains the Bug fix description of Aptify 6.4 release as given below:

Additional diagnostics when view SQL fail in services, cap on query results

Aptify 6.4 has been enhanced to include improved diagnostics in case of a view failure and handle out of memory warnings while returning large query results. To improve the diagnostics in case a SQL view fails, an exception will be logged in the Event Viewer stating that the provided SQL failed, and a base view has been returned instead; to avoid out of memory error, web.config files has been modified to enforce the TopRecord setting. By doing so the service will not consume all memory while getting result sets for a large query.

(Issue 4769

Kendo-Contact log > Load from Template popup UI load problem

...

The Records ID of Persons, Orders, Company, and Product were displaying as undefined in the record tab heading. This issue has been resolved in release 6.4.

(Issue 5373)

Hitting Cancel for Messaging Wizard Confirmation Dialog Loses Entire Message

In Aptify, the Messaging Wizard dialogue– “Do you really want to send this message?”–was not working as expected. When the user clicked cancel button to go back to the message, the entire message was getting wiped out. This issue has been fixed, now when the user clicks cancel button, they will be taken back to the original message and the wizard will persist it’s previous state.

(Issue 5656)

ProductCache: Unable to Locate Product information with an ID of 0

In Aptify, while processing an order creation from the app server for Product ID 0, the application was logging exception– “Unable to locate Product Information with an ID of  0” in Error Log table.  This issue has been resolved.

(Issue 5663)

Event Viewer is spammed with message about DefaultScheme not being set

...

In Aptify release 6.2 and release 6.3, while processing credit card reference payments with Bluepay, an error message “Credit card verification failed” was being encountered. This issue has been resolved by adding following new attribute to the configuration files through setup.  Attribute information:

shell.config

<add key="Aptiy.Framework.Payment.ClientInformationProvider" value="Aptify.Applications.OrderEntry.Payments.ClientValuesDesktop.DesktopClientInformationProvider, ClientValuesDesktop, Version=6.0.1.0, Culture=neutral, PublicKeyToken=f3fa0ecabf9514d9"/>       —added to shell.config for desktop application.

web.config 

<add key="Aptiy.Framework.Payment.ClientInformationProvider" value="Aptify.Applications.OrderEntry.Payments.ClientValuesServices.ServicesClientInformationProvider, ClientValuesServices, Version=6.0.1.0, Culture=neutral, PublicKeyToken=f3fa0ecabf9514d9"/>       —added to web.config for web application.(Issue 6040

(Issue 6040)

Save for Later function saving credit card information in database

In Aptify, while processing credit card reference transaction payment for an order, if the option "Save for Future use" is selected, the credit card number was being stored in an incorrect format in the database. This has been rectified.

 (Issue 6071)

Company Persons Entity List View (ELV)Hangs After Sort

In Aptify, there was an issue found in the sort operation on Persons view in Company records. When a user performed sort operation on ELV headers, Aptify would become unresponsive with a message–"You can wait for it to become responsive or exit the page”. This issue has been resolved, now the ELV sorting is working as expected.

(Issue 6072)

Order line description coming up as Booth: undefined

In Aptify, there was an issue while overriding the product description of an order through Edit Order Line button; the content of the description was being displayed as “Booth: undefined”. This issue has been resolved.

(Issue 6085)

Some Advanced SQL Views Do Not Display Paging or Record Count

In Aptify, some of the views with advanced SQL did not display the pagination correctly at the bottom of an Entity List View (ELV). This issue has been resolved.

(Issue 6092)