Version 6.0.41, Released February 17, 2023 Requires EchoVantage Version 3.44+
Bug Fixes
Ticket Number |
Case Number |
Description |
---|---|---|
EV-6150 |
19192 |
An issue was reported where some custom forms failed to load due to a Null Pointer Exception. The cause was due to an unfocusable component, i.e., a button, in the first position (Tab Order = 0). This issue was addressed, and now forms with a button or other unfocusable component in the first position load without error in the Live Preview. |
Version 6.0.40, Released February 7, 2023 Requires EchoVantage Version 3.44+
Bug Fixes
Ticket Number |
Case Number |
Description |
---|---|---|
EV-1673 |
3311, 15079, 16132 |
An issue was reported where selecting the date picker calendar and clicking rapidly through the navigtation buttons to find a specific date presented a Required Field [date] cannot be blank error. After the error displayed, the calendar would scroll rapidly with no way to stop it. This issue was addressed. Clicking rapidly no longer causes the calendar to scroll, and the missing date error only presents if you navigate away from a required date field without populating it. |
EV-4820 |
15599 |
An issue was reported where a default value appeared to be set (it was not) for a radio button field after the form was saved when the Allow No Selection property was set. However, if the form was reopened and the radio button field was selected, the designer did add a default value in error. Both issues were addressed, and now when radio buttons have the Allow No Selection property set, the radio buttons do not have a selection in the preview or designer pane. In addition, the radio button field can be selected and no default value is set. ![]() |
EV-5729 |
17638 |
An issue was reported where the Select Popup Form Properties screen was not allowing additional rows to be viewed. This issue was addressed, and now if the number of added rows exceeds the viewable area, a scroll bar appears allowing all additional rows to be viewed. ![]() |
EV-5804 |
TEAMCARE |
An issue was reported where clicking on any field of a custom form threw a save error when adding a new record. The issue was caused by an incorrect initial parent container when the form was initialized. This issue was addressed, and now the save error no longer appears when fields are selected. |