The following table lists the new features, bug fixes and known faults for Version 3.80 of Konect.
New Features | New Features | ||
Brief description | Details | ||
KO-179 | Text annotation for photographs on iOS devices | Konect provides text annotation on photographs taken on iOS devices. | KO-179 |
KO-202 | Example solutions – KPK demo datasets | Konect Manager provides access to example solutions such as Tree Management. The example solutions can be downloaded from a web link to Konect Manager. | KO-202 |
Bug Fixes | Bug Fixes |
| |
KO-180 | DEVICE: Child list rules generated dynamically | When a child list was associated with a parent list, a set of rules relating each parent item to its child items was created. However, when either the parent or child list was updated, the rules were not. Now the rules are created dynamically as needed and lists are kept up to date. This is particularly relevant to the situation where a child list is parented by a ‘Copy value’ field where the value is copied from a List field. | KO-180 |
KO-182 | DEVICE: Visibility rule fails on default value for Integer field | The following error has been fixed:
| KO-182 |
KO-205 | KM: Solution for KS-34, HTTP network error 407 | The Http client has been given a longer timeout period in order to thwart 407 errors. | KO-205 |
KO-206 | KM: Stacked map objects not rendering in the correct order | The map features of child records were not displaying in the correct z-order. Records created at later times must sit on top of records created before them and this was not happening. | KO-206 |
KO-209 | KM: Forms can be saved with invalid field constraints | A form could be saved with invalid field constraints. For example, if a Text field has a maximum length limit of 7 and the default value is ‘AUSTRALIA’, then the form could be saved. This release disables the 'Save' button until field constraints are valid and consistent. | 209 |
KO-220 | Yes/No fields in selection lists rendered with ticks and crosses | When a map is zoomed out, many features may be sitting on top of each other. If the user clicks on this mass of features, a selection list is presented which contains all the features under the click point so that the user may select the required record. If the one of the selection fields is a Yes/No field, then the values for that field will presented as green ticks and red crosses. As an example, let there be a form called 'House Renovation' that has two selection fields called 'Room' and 'Renovated' and let 'Renovated' be a Yes/No field. If there are six records under the click point then the following image shows the values of 'Renovated' with ticks and crosses.
| KO-220 |
KO-221 | KM: Visibility rule depending on List field does not honour ‘not equal to’ operator | Version 3.70 of Konect did not honour the ‘not equal to’ operator for field visibility based on values of List fields. For example, assume there is a List field called ‘Animal Type’ that has three values ‘Dog’, ‘Mouse’ and ‘Rat’. Let there be a Text field called ‘Action Required’ that has a visibility rule: VISIBLE if ‘Animal Type’ not equal to ‘Dog’. The visibility rule was not honoured in Release 3.70 when operators for visibility rule were enhanced. Release 3.80 honours the ‘not equal to’ operator for visibility rules based on List fields. | KO-221 |
KO-223 | DEVICE: Deleting photo in offline project causes konect to freeze | This release fixes the following problem: 1. Create an offline project that has a form that has a photo field. 2. Create a record with no photos and save it. 3. Open the record again. 4. Take a photo for the photo field but don't save the record. 5. Delete the photo from the photo field. 6. Press the 'Save changes' button'. konect permanently displays the message 'Saving your changes now'. | KO-223 |
KO-226 | KM: Missing .CSV file extension is used as a folder during export of data | When a dataset was exported to a CSV file and the extension ‘.CSV’ was missing, a folder rather than a file was created. | KO-226 |
KO-227 | KM: Select 'Primary Form' tab when new form created | When a new form is created the 'Primary Form' tab is now always selected. | KO-227 |
KO-234 | DEVICE: Unable to move map feature in query in offline project | If an offline project had a query and the query’s dataset allowed for features to be edited, a map feature could not be moved on the map. | KO-234 |
KO-235 | KM: Exported geojson files have extension of '.geojson.json' | When a dataset was exported to a GeoJSON file, the filename had an extension of ‘.geojson.json' instead of '.geojson'. | KO-235 |
KO-236 | KM: Cannot revert to 'Match Pattern' = 'None' for Text fields | If the 'Match Pattern' for a Text field was changed from ‘None’ to something else, it could not be changed back to ‘None’. | KO-236 |
| Known Faults | Known Faults | ||
| KO-157 | KM: Map labels based on List fields use code value, not display value | KO-157 | |
| KO-177 | KM: Datepicker control shows a default time of 10 am | KO-177 | |
| KO-178 | KM: Zoom setting does not apply until 'Save location and visibility' button pressed | KO-178 | |
| KO-191 | KM/DEVICE: Field visibility rules based on Time, Date and Datetime fields do not work | KO-191 | |
| KO-194 | DEVICE: Able to save record with out-of-limit numerical field | Assume that an upper and lower limit has been set for the value of a numerical field in a form. Even though limits have been set, a number can still entered on the client device that is outside the limits. The problem is that when the record is saved there is no error message that the field's value is outside the set limits and the entered value is replaced by its closest limit. For example, if the limits are 0 to 100 and the user enters 1000 on the client device, the value stored in the field when the record is saved will be 100, the closest limit to 1000. | KO-194 |
| KO-225 | KM: Cannot directly enter negative numbers for default values | This problem applies to numerical fields. When setting the default value or upper or lower limit in the Konect Manager's form editor, a negative number cannot be directly entered into the textbox. To circumvent this fault, enter the positive number, place the cursor at the front of the number and then type the minus sign. | KO-225 |
| KO-231 | KM: Mouse does not detach from scrollbar when editing a record | This fault occurs when editing a record in Konect Manager where there are many fields and the scrollbar must be used to get to the fields at the bottom of the form. The mouse does not detach from the scrollbar properly when moved off the scrollbar and the form continues to move up or down. | KO-231 |
